Skip to main content
Qomon Fundraising is a separate add-on. See pricing or reach out to your account manager to get access.
Financial data in Qomon is organized around transaction bundles. A bundle represents a single payment event and groups together:
  • Transactions — the payment itself (amount, method, payer)
  • Memberships — membership subscriptions attached to the payment
  • Donations — donations attached to the payment
One bundle typically contains one transaction, but the memberships and donations within it can be attributed to different contacts than the payer. For an overview of the transactions feature in the Qomon web app — including provider configuration and dashboard concepts — see the Qomon help center: Overview of the transactions feature.

​
One API key = one space

The bundle is recorded in the space whose API key you use. The contact can belong to a different space — their profile will still show the transaction. This is the correct pattern for multi-space organizations (e.g. a national federation and local chapters).

​
Payer vs. beneficiary

​
Getting required IDs

Before creating a bundle, retrieve the IDs valid for your group: See Reference data for details on each endpoint.

​
Updating and refunds

Bundles are updated via PATCH /v1/transaction_bundles/{id}. Updates are additive: items not included in the request remain unchanged.
Always resend all required fields on an item you are updating. Missing required fields may be cleared.
For a refund: PATCH the transaction with the reimbursed status and reimbursed_amount, and also update the amount on the linked membership or donation, then DELETE or update the products in the bundle so that the sum of the amounts correspond to the amount of the transaction bundle. See Update and refund bundles for step-by-step examples.

​
external_transaction_id

Use this field to link bundles to your own system’s records. Must be a plain integer, string are not supported.
Last modified on June 16, 2026