Introduction to the RMO Merchant API | RMO Developer Center, Merchant Services

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 authorizing, capturing, refunding, voiding, and settling transactions. Merchants can also take advantage of PaymentCodes, a secure PIN-based alternative to stored cards, and RecurringAuthorizations, which allow merchant-initiated transactions in a compliant and member-controlled manner.

What You Can Do

  • Process authorizations (auth-only)

  • Capture funds against an existing authorization

  • Run combined sales (auth + capture)

  • Void authorizations before settlement

  • Process partial or full refunds

  • Accept PaymentCodes for CNP payments

  • Enable, charge, and revoke recurring billing

  • Retrieve transaction history

  • Access settlement batches and statements


API Base URL

https://api.rmous.org/merchant/v1/


Core Domains

  • MerchantServicing – Merchant accounts, PaymentCodes, RecurringAuthorizations, merchant transactions

  • FinancialServicing – Ledger transactions, account balances, statements

  • CardServicing – Card issuance, limits, statuses, card networks


Whether you’re building an e-commerce checkout, a POS integration, or a subscription platform, the RMO Merchant API provides all the core payment capabilities you need.
    • Related Articles

    • Authentication & API Security

      The RMO Merchant API uses API Keys to authenticate and authorize requests. Every request must include a valid key in the Authorization header. Authentication Header Authorization: Bearer <API_KEY> API Key Types Test Keys: For development and QA Live ...
    • 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 ...
    • 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 ...
    • Understanding Transaction Types

      The RMO Merchant API supports multiple types of monetary transactions. Understanding these types ensures proper integration and reduces payment errors. Authorization Checks whether funds are available. No money moves. Capture Transfers funds after a ...
    • 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 ...