Repeat collection

Make every renewal explainable

Recurring payments require more than scheduling a charge. Customer authorization, payment state, retries, cancellation, and account access need a shared operating model.

Apply for merchant access

Recurring lifecycle

Design the renewal around state

Availability depends on the approved business, payment method, and commercial arrangement.

  1. 01

    Authorize

    Present the customer terms and collect the authorization required for the approved repeat payment flow.

  2. 02

    Schedule

    Connect the billing date and amount to the customer account or subscription record.

  3. 03

    Attempt

    Receive a verified outcome and keep the account active, pending, or past due as appropriate.

  4. 04

    Recover

    Use a controlled retry or customer update path rather than creating duplicate collection attempts.

  5. 05

    Cancel

    Stop future collection and preserve the record required for support and reconciliation.

Subscription operations

What the integration must decide

The gateway returns payment states. Your product still decides what those states mean for access and service.

When access starts

Activate an account only after the payment result meets your verification rule.

How pending is treated

Keep an account in a clear interim state when the final payment outcome has not arrived.

What a failed renewal changes

Define the retry window, customer notification, grace period, and suspension rule.

How refunds affect service

Connect full or partial refunds to entitlement, accounting, and customer communication.

Map your renewal flow before onboarding

Bring the billing cadence, customer terms, retry policy, and account state model to the merchant review.

Discuss recurring payments