Skip to main content
All systems operationalChangelogv1
Log in
Industry solution

Recurring Commerce

Build recurring payment journeys with explicit consent, reusable credentials, subscription lifecycle management, retries, and reconciliation.

On this page

Recurring Commerce separates the customer-approved setup from later merchant-initiated charges. A safe implementation preserves consent and credential lineage, distinguishes the initial customer interaction from subsequent charges, and gives operations teams a complete subscription and payment history.

Credential setupTokenize a supported credential and retain the customer consent and usage purpose.LifecycleCreate and manage supported plans, subscriptions, renewals, retries, and cancellation.Outcome operationsTrack asynchronous state, refunds, disputes, and reconciliation across every charge.

Separate setup from recurring execution#

Sequence diagram
1Customer2Merchant3DEUNA4ProviderApprove terms and credential useTokenize through a supportedexperienceReturn a reusable referenceCreate the supported recurring chargeSubmit with configured recurringcontextReturn processing stateNotify or expose authoritative outcome
Merchant or customerDEUNAProvider or processor

The exact first-payment, token, network, authentication, merchant-initiated transaction, and retry requirements depend on the provider, market, method, and account configuration.

Operational requirements#

  • Record the customer, terms version, consent time, credential reference, and permitted use.
  • Keep credential status separate from subscription and individual charge status.
  • Apply a unique business reference and supported idempotency behavior to each scheduled charge.
  • Define retry eligibility, spacing, maximum attempts, customer communication, and cancellation rules before production.
  • Reconcile a timeout or unknown state against the original attempt before resubmitting.
  • Support credential expiry, replacement, revocation, customer deletion, plan change, pause, and cancellation.

For account-specific batch optimization of scheduled charges, see Acceptance Agent. It is an agreed file interface, not a public API contract.

Continue with Subscriptions, Payment Vault, and Reconciliations.