It's late afternoon and an order has just come in from a returning customer. Their card is already saved from last time, but the stock check won't finish until tomorrow, so you don't want to take the money yet and you can't risk losing it either.
If you build checkouts or billing for UK businesses, this is the everyday job of charging a saved card off-session. The customer isn't there, and your code decides when money is reserved, when it's collected and when it's let go. This post walks through auto capture, manual capture and capture before expiry, what happens when a hold expires, where SCA does and doesn't apply, and how idempotency stops a retry from charging someone twice.
Why off-session card charges need care
An off-session charge is a card payment you start when the customer isn't on your site or app.…