Library · Payments · Guide
Partial / multi-capture — claim map
GuidePartial / multi-capture — claim mapBack to article
Split ship after one auth. Partial capture ≠ void. Filter the claim. Get this gateway’s multi-capture rule in writing.
| Claim | Reality | Get in writing | Do not |
|---|---|---|---|
| I can always multi-capture any auth | No. Gateway and issuer must allow it. Some force full capture or new auth | Partial / multi-capture enabled on this MID | Assume every auth splits cleanly |
| Partial capture voids the rest for the customer | No. Captured dollars stay. Unused auth release is not a refund | How leftover auth is released here | Tell CS unused auth = customer credit |
| Capture full auth on day one; fix with void later | Usually wrong. Capture what shipped. Full early capture starts the refund clock | When capture is allowed relative to ship | Capture the whole cart before inventory moves |
| Leftover auth waits forever for the second box | No. Auths expire. Second ship may need a new auth | Auth expiry and re-auth rule | Invent a universal hold window |
| Refunds always hit “the order,” not a capture | No. Refunds attach to captures / settlement lines | Which capture a refund reverses here | Guess which line CS credited |
| This map is void vs refund clocks | No. Auth-capture-settle is reverse doors. This map is split-ship capture | N/A — open auth-capture-settle for void/refund | Skip multi-capture writing because you know void rules |
Filter the claim. Split ship needs a capture plan. Partial capture is not a void. Leftover auth can expire. Type this gateway’s multi-capture rule — we invent none.
Pairing procedure: Split ship needs a capture plan. Topic: Payments.
Work with us — We run this job on your accounts. Services