Void an Authorization | RMO Developer Center

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 shipment

Request Fields

  • authorizationId

Response

  • voided (true/false)

  • reasonCode

Voids cannot be performed after the capture step; use refunds instead.


    • Related Articles

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

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

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

    • Capture a Transaction

      Captures finalize a previously approved authorization. Money begins moving only after a successful capture. Endpoint POST /merchant/v1/transactions/capture Use Cases Completing a hotel stay Charging after verifying funds Adjusting the amount after ...