/

Payment capture

GLOSSARY

Payments

Payment capture

Payment capture

Payment capture

THE SHORT VERSION

Payment capture collects an amount that was previously authorised. It is a different event from a payment provider paying funds into your bank account.

Payment capture collects an amount that was previously authorised. It is a different event from a payment provider paying funds into your bank account.

Payment capture is the collection step following a separate authorisation. For example, Stripe’s capture operation applies to an existing uncaptured payment and can specify an amount within its rules. A capture record is distinct from the later payout record. Source: Stripe API: capture a payment Source: Stripe: payout reconciliation

Keep booking and payment evidence separate

In an illustrative travel workflow, a supplier confirms the room and the agency then captures the authorised payment. Record the supplier reference and the payment reference together, while keeping each status visible. This lets a colleague investigate either part without assuming one proves the other.


The sequence must fit your actual supplier agreement, payment provider and integration. Use a test environment to establish the supported behaviour before applying the process to customer bookings.

A useful check

Compare the captured amount and currency with the agreed customer price. Record a reason for any difference, such as an approved partial collection, so it can be explained during reconciliation.


If the result is unclear, retrieve the payment’s current status before attempting another collection. This check establishes what happened to the first attempt before anyone takes further action.


Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.

Sources

The official pages behind this explanation. This is general information, not legal advice, and rules change, so check the latest version.