Update an existing transaction_bundle by id
Update an existing transaction bundle. Updates are additive for arrays — items not included in the request remain in the bundle unchanged.
Rules:
- To update an existing transaction/membership/donation: include its
idplus ALL its required fields (not just the changed ones — omitted required fields may be cleared) - To add a new item: omit
id— a new item will be created and added to the bundle - Items not included in the request arrays are left unchanged
- The bundle
idin the path must match theidin the request body
Warning: Always send all required fields when updating an item, not just the fields you want to change. Missing required fields on an updated item may be reset to empty/zero values.
Refund workflow For a partial refund (e.g. 10€ back on a 20€ transaction):
- Get the transaction
idand membership/donationidfromGET /v1/transaction_bundles/{id} - PATCH with the reimbursed status,
reimbursed_amount, and the updated membership/donation amount:
{
"id": "<bundle_id>",
"data": {
"transactions": [
{
"id": "<transaction_id>",
"contact_id": 123456,
"amount": 2000,
"currency": "eur",
"payment_method_kind": "CB",
"date": "2026-03-29T12:59:52+02:00",
"external_transaction_id": 1001,
"status_id": 2,
"reimbursed_amount": 1000
}
],
"memberships": [
{
"id": "<membership_id>",
"contact_id": 123456,
"membership_price_id": 10,
"start_date": "2026-01-01T00:00:00Z",
"end_date": "2026-12-31T00:00:00Z",
"amount": 1000,
"amount_initial": 2000,
"currency": "eur"
}
]
}
}
Use GET /v1/transaction_statuses to find the id of the “Reimbursed” and “Cancelled” statuses for your group.
For a full refund or cancellation, the cleanest approach is:
DELETE /v1/transaction_bundles/{id}to remove the bundlePOST /v1/transaction_bundlesto recreate it with the corrected data
Note: A PATCH does NOT change the bundle’s position in GET /v1/transaction_bundles list — it stays at its original creation date position.
Documentation Index
Fetch the complete documentation index at: https://developer.qomon.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
ID of transaction_bundle to update
Body
A transaction bundle groups together related financial operations (transactions, memberships, donations) that are part of a single payment event.
Structure:
transactions: Array of payment transactions (required - at least one)memberships: Array of membership subscriptions (optional)donations: Array of donation contributions (optional)summary: Automatically calculated counts (read-only, returned in responses only)
When Creating:
- Omit
idfield (auto-generated) - Omit
summary(auto-calculated, returned in responses) - Include at least one transaction with required fields
When Updating:
- Include
idfield matching the bundle ID in the URL - Include
idfor existing items you want to modify - Omit
idfor new items you want to add - Note: Updates are additive - items not included in the request remain in the bundle unchanged (they are not removed)
Response
Successful operation
"success"
A transaction bundle groups together related financial operations (transactions, memberships, donations) that are part of a single payment event.
Structure:
transactions: Array of payment transactions (required - at least one)memberships: Array of membership subscriptions (optional)donations: Array of donation contributions (optional)summary: Automatically calculated counts (read-only, returned in responses only)
When Creating:
- Omit
idfield (auto-generated) - Omit
summary(auto-calculated, returned in responses) - Include at least one transaction with required fields
When Updating:
- Include
idfield matching the bundle ID in the URL - Include
idfor existing items you want to modify - Omit
idfor new items you want to add - Note: Updates are additive - items not included in the request remain in the bundle unchanged (they are not removed)