Charge a Recurring Authorization
Once a RecurringAuthorization is active, merchants can charge Members automatically.
Endpoint
Use Cases
Request Fields
-
recurringAuthorizationId
-
amount
-
currency
-
merchantReference
Response
-
transactionId
-
approved
-
riskScore
-
status
Recurring charges are standard sale transactions but marked as merchant-initiated.
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 ...
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 ...
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 ...
Authorization & Capture Flow
The RMO payment process uses a two-step flow—Authorization and Capture—similar to card networks and major payment processors. Step 1 — Authorization A merchant sends an authorization request to: POST /merchant/v1/transactions/authorize During this ...
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 ...