Library · Payments · Guide
Auth / capture / settle — claim map
GuideAuth / capture / settle — claim mapBack to article
Void before capture. Refund after. Settle ≠ deposit. Filter the claim. Type this gateway’s windows — we invent none.
| Claim | Reality | Type / ask | Do not |
|---|---|---|---|
| I can void after capture | Usually no. Capture closes the void door; refund / reverse applies | This gateway’s void-after-capture rule | Promise a void on a captured sale |
| Settled means cash in my bank | No. Settlement is acquirer books. Deposit is a later clock | Batch-to-bank days on this schedule | Bid on settled as if it deposited |
| Open auth is spendable / settled | No. Auth is a hold. It can expire. It is not settlement | Auth expiry on this issuer / gateway | Scale media off open auths |
| Refund overlap clock = auth void window | No. Overlap is refund vs dispute timing. Void is pre-capture | Which clock CS is on — void or refund | Mix the two clocks in one CS script |
| This map is sold-vs-settled stages | No. Sold-vs-settled names CRM / statement stages. This map is reverse doors | N/A — open sold-vs-settled for stage labels | Skip typing stages because you named void/refund |
| Universal void window is 7 days | No. We invent no number. Issuer holds and gateway capture rules differ | Written capture / void windows here | Paste a forum day count into policy |
Filter the claim. Open auth → void. After capture → refund. Settle is acquirer books, not your deposit. Type this gateway’s windows — we do not invent them.
Pairing procedure: Know when an auth is still reversible. Topic: Payments.
Work with us — We run this job on your accounts. Services