Skip to main content
Use this page for state handling in your backend, UI, and operations dashboards.

​
Typical lifecycle

​
Status handling guidance

  • pending: transaction created but not final.
  • three_ds_required: customer interaction is required.
  • authorized: payment network approved the charge.
  • captured: merchant-safe success state for fulfillment.
  • refused: show a retry path or another payment method.

​
Webhook implication

Do not fulfill based only on the first synchronous response if the flow can still require 3DS or move through provider processing. Your webhook consumer should own the final decision.