Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Use a stable idempotency key for one payment intent and let the server enforce deduplication. Treat a timeout as an unknown outcome and reconcile with server state.
Persist the intent identity before sending the request and reuse it when retrying the same operation. The backend must atomically map that identity to the payment outcome and reject incompatible payload reuse. Disabling the button helps usability but cannot protect against process restarts or transport retries. After a timeout, query the authoritative status or retry under the same identity. Create a new identity only for a genuinely new intent and define retention and reconciliation behavior.