Library · Payments · Guide
Auth expiry / re-auth — claim map
GuideAuth expiry / re-auth — claim mapBack to article
Open auth holds die. Late capture may need a new auth. Filter the claim. Type this gateway’s window — we invent none.
| Claim | Reality | Get in writing | Do not |
|---|---|---|---|
| Auths stay open until I capture | No. Issuer / gateway holds expire | This MID’s auth expiry window | Invent a universal day count |
| I can capture after the hold died | Usually no. Re-auth (or restart) first | Capture-after-expiry behavior here | Force capture on a dead auth |
| Expired auth = money stuck in float | No. Float is after capture / settlement | N/A — open payout-delay for deposit clocks | Confuse dead holds with bank float |
| CRM paid means the hold cannot expire | No. CRM paid is often just auth. Holds still die | Whether CRM marks auth vs capture | Bid media on open auths |
| Partial first capture freezes leftover forever | No. Leftover hold can still expire before the next ship | Leftover auth lifetime after partial capture | Assume split ship is unlimited hold time |
| This map is sold-vs-settled stages | No. Sold-vs-settled names cash stages. This map is hold death / re-auth | N/A — open sold-vs-settled for stage labels | Skip writing expiry because you know the stages |
Filter the claim. Open auths expire. Late capture can fail. Re-auth when the hold is dead. Type this gateway’s window — we invent none. Not the same clock as payout float.
Pairing procedure: Ask when an open auth dies before ship. Topic: Payments.
Work with us — We run this job on your accounts. Services