Recurring Billing & Merchant-Initiated Transactions | RMO Developer Center

Recurring Billing with Recurring Authorizations

Recurring Billing with RecurringAuthorizations

Article Body (Secure Version)

RMO supports compliant merchant-initiated recurring billing through RecurringAuthorizations, which represent a verified agreement between a Member and a Merchant for future charges.

How Recurring Billing Works

  1. A Member completes the first transaction (PaymentCode or card).

  2. The Merchant requests recurring permission within their integration.

  3. The Member receives a prompt in the RMO Mobile/Web app to approve or deny.

  4. Upon approval, a RecurringAuthorization is created and linked to the merchant.

  5. The Merchant can then initiate recurring charges using:

POST /merchant/v1/recurring/charge

What a RecurringAuthorization Contains

Each recurring agreement securely stores:

  • Merchant reference

  • Member reference

  • Approved payment method reference

  • Whether recurring billing is currently active

  • Timestamp of the first approved transaction

  • Timestamp of the last successful use

Revoking Recurring Agreements

Both merchants and members may revoke recurring billing at any time.
Revoked authorizations immediately prevent all future merchant-initiated charges.

    • Related Articles

    • Create a Recurring Authorization

      RecurringAuthorizations allow merchants to charge Members on a recurring schedule once the Member has approved the agreement. Endpoint POST /merchant/v1/recurring/authorize Workflow Merchant requests recurring setup Member approves in RMO app ...

    • Charge a Recurring Authorization

      Once a RecurringAuthorization is active, merchants can charge Members automatically. Endpoint POST /merchant/v1/recurring/charge Use Cases Subscriptions Membership billing SaaS monthly fees Merchant-initiated payments Request Fields ...

    • Introduction to the RMO Merchant API

      The RMO Merchant API allows merchants, platforms, and payment partners to securely process transactions across card-present and card-not-present channels using RMO’s unified payments network. This API provides a modern, predictable interface for ...

    • Validate a Payment Code

      Before using a PaymentCode for a sale or recurring billing, merchants can validate the code. Endpoint POST /merchant/v1/paymentcodes/validate Verifies Code format Code activation Member association Expiration or usage limits Whether recurring billing ...

    • Processing Payments with PaymentCodes

      A PaymentCode is a secure 8-character alphanumeric token created by a Member in the RMO app or portal. PaymentCodes provide a safe alternative to storing card details and are ideal for card-not-present payments. Key Features 8-character randomly ...