Guide
3-D Secure 2: what the backend has to do
Authentication is not a capture. Which states your API has to persist, why the shopper return and the webhook will race, and what not to infer from a redirect.
Topic
payments
6articles · all topics
GuideHTTP
Idempotency keys for payment endpoints in .NET
How to make a charge endpoint safe to retry: key scope, hashing the raw body, the 409 on a mismatched payload, and the race a unique index has to close.
Guide
Out-of-order webhooks: what the handler must do
Payment webhooks do not arrive in causal order. How to apply them with a state machine and an event id, instead of trusting which HTTP request landed first.
Guide
Retry and backoff for payment APIs in .NET
Which payment HTTP failures are safe to retry, why a timeout is not one of them, and how backoff without an idempotency key charges the customer twice.
Guide
Reconciling a ledger against a settlement file
A captured payment is not settled money. How to match a settlement file to your ledger on the provider reference, and which mismatches need a person.
Guide
What a payment sandbox will not let you test
A sandbox proves your request is well formed. It does not prove settlement timing, issuer behaviour, or failures that show up only with real cards.