What capture date is
Capture Date refers to the date a payment capture is processed by an acquirer. A capture follows an authorization and requests the movement of authorized funds from the cardholder's account to your business. The authorization reserves funds, while the capture is the later step that charges the card.
A transaction is the broader payment event, which can include authorization, capture, and settlement. Capture Date identifies a date associated with the capture step, not the full transaction timeline. The term does not have one universal field name or format across payment systems.
A Capture Date shows when a capture was processed, not when the money necessarily reached your bank account.
Which payment date you are looking at
Payment records can show several dates for the same capture. In one API format, `timeOfRecord` is when the gateway considers the operation to have occurred, while `transaction.acquirer.date` and `transaction.acquirer.time` indicate when the acquirer processed it. The acquirer date and time are not returned in every record.
`transaction.acquirer.settlementDate` refers to when the acquirer expects funds to move to or from your account. `transaction.funding.date` records the date funds arrive when known, while `transaction.funding.initiatedDate` and `transaction.funding.estimatedDate` describe a transfer in progress or an expected arrival. These dates answer different questions, so a capture date alone does not prove your deposit arrived.
What capture date means for costs and cash flow
Capture Date is a timing and reconciliation detail, not a separate fee by itself. Processing fees can apply to authorization, capture, or refund activity, but the date label does not tell you the fee amount or establish a separate capture-date charge.
Captures are commonly grouped into a batch before settlement, so the date a capture is processed and the date funds move can differ. If you compare daily sales with bank deposits, match the capture record to the batch and settlement details rather than treating the Capture Date as the deposit date. A missed authorization expiry can also cause a later capture request to be rejected, leaving the payment uncollected.
What you can actually change
You do not set the acquirer's processing date, and a Capture Date does not create a cost you can negotiate. You can capture within the authorization's valid period and use consistent records to trace each payment through settlement.
- Match each capture to its original authorization using the order or transaction identifiers.
- Compare the capture processing date with the batch settlement date and the date funds reached your account.
- Review any fee by its fee type and amount, rather than assuming a Capture Date line is a fee.
- Match payment records. Use the order ID and transaction ID to connect each capture with its authorization and settlement record.
- Separate the dates. Reconcile capture processing, settlement, and bank funding dates as separate events in your daily close.
- Inspect fee details. If a statement shows a date-related charge, verify its actual fee name and amount against your processing records.
Frequently asked questions
Does Capture Date mean the date I receive the money?
No. Capture Date refers to when a capture is processed. Settlement and bank funding are separate steps, so compare the capture record with the settlement details and the deposit posted to your account.
Is Capture Date the same as Transaction Date?
No. Transaction Date can refer to a date associated with the broader payment event. Capture Date concerns the capture step, which follows authorization and requests that authorized funds be charged.
Does Capture Date affect my processing fees?
The date itself is not a separate fee. Processing fees can apply to authorization, capture, or refund activity, so identify the fee type and amount on your records instead of treating the date as a charge.