Create a Recurring Authorization
RecurringAuthorizations allow merchants to charge Members on a recurring schedule once the Member has approved the agreement.
Endpoint
Workflow
-
Merchant requests recurring setup
-
Member approves in RMO app
-
Authorization becomes active
-
Merchant may initiate future charges
Request Fields
-
memberId or paymentCode
-
merchantReference
-
description
Response
This endpoint initializes the recurring billing relationship.
Related Articles
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 ...
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 ...
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 ...
Void an Authorization
Voids cancel an authorization before it is captured or settled. No funds are moved. Endpoint POST /merchant/v1/transactions/void When to Use Customer cancels order Duplicate transactions Authorization created in error Adjustments required before ...
Authorize a Transaction
The authorization endpoint checks if a Member has sufficient funds or credit and validates the payment method without moving any money. It is commonly used for: E-commerce pre-auth Hotels Fuel stations Tipping workflows Any flow where final price may ...