MOTO

Introduction

A MOTO transaction is a purchase where the customer cannot tap, insert, or swipe their card on the terminal - instead, the merchant enters the customer's card details into the terminal on their behalf. This is typically used when a customer pays over the phone or by mail. It is also known as a card-not-present transaction.

📘

In your POS, the button for initiating a MOTO transaction must be separate from the button for making a standard purchase.

Enabling MOTO

MOTO requires configuration by the merchant's bank or payment provider. The merchant must contact their payment provider to enable this.

When testing with Gecko Bank, open the MXA Settings app and enable the MOTO setting.

Creating a MOTO transaction

POST /v1/transactions

{
  "moto_details": {
    "moto_amount": 1000
  }
}

📘

Tipping and cashout cannot be used with MOTO transactions.

When testing with Gecko Bank, select the type of MOTO transaction — Mail order, Telephone, or Manual — then enter the card details.

Polling

Once created, follow the polling loop described in Transactions overview until the transaction reaches FINALISED.

Finalised response

The MOTO response follows the same structure as any other finalised transaction. Once status reaches FINALISED, read the following fields:

UNKNOWN means the outcome could not be determined - handle this via the override flow in Transaction recovery.