PaymentCodes for CNP Payments | RMO Developer Center, Merchant Services

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 generated code

  • Securely hashed on the server immediately after creation

  • Linked to a specific Member and their selected payment account

  • Supports both one-time and recurring billing

  • Member-controlled and revocable at any time

Where PaymentCodes Are Used

  • Online checkout flows

  • Over-the-phone payments

  • Subscription setup

  • Merchant-initiated recurring billing

API Endpoints

POST /merchant/v1/paymentcodes/validate
POST /merchant/v1/paymentcodes/sale
POST /merchant/v1/paymentcodes/recurring-charge

Security Considerations

  • Raw PaymentCodes are never stored

  • Hashing is performed using strong cryptographic functions

  • Codes may be time-limited or usage-limited

  • Only authorized merchants may submit PaymentCodes


    • Related Articles

    • 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 ...

    • 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 ...

    • 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 ...

    • 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 ...

    • Perform a Sale (Auth + Capture)

      A Sale requests authorization and capture in a single step. It is the most common type of transaction. Endpoint POST /merchant/v1/transactions/sale Use Cases Retail E-commerce checkout Food & beverage Subscription initial payments Request Fields ...