Mail Order/Telephone Order (MOTO)

A Mail Order/Telephone Order (MOTO) transaction is a card-not-present transaction where the shopper provides you with their order and payment details by regular mail (not email), fax, or telephone. By passing on these data to you, the cardholder gives you permission to process the transaction. When you do a MOTO transaction, the payment terminal prompts you to enter the shopper's card number and CVC code. The result of checking the CVC code is shown in your Customer Area > Transactions > Payments.

Delayed capture

If you want to accept MOTO transactions, you should configure a capture delay. This gives you time to cancel the authorization before the payment is captured, in case you have second thoughts about the transaction.

Risk management

You can use our risk management system to minimize fraud by applying risk rules before processing a transaction. Based on your risk settings, every transaction gets a risk score ranging from 0 to 100 and is declined when the risk score reaches 100.

Address verification service

To reduce the risk of fraud, you have the option to add an address verification service (AVS) check to the MOTO payment flow. With an AVS check, the payment terminal prompts you to enter the shopper's postal code (zip code) and house number. The card issuer validates the data you entered against the cardholder's billing address, sends us the result, and declines or authorizes the payment.

It is possible that issuers authorize a payment even though the entered data do not fully match. To enable you to verify this and decide whether to go ahead with the transaction, you receive the result of the AVS check in the payment response and in your Customer Area > Transactions > Payments. If you configured a capture delay, you can cancel the authorization if necessary.

AVS is supported by American Express, Discover, Mastercard, and Visa. In the US, UK, and Canada, all other issuers also support it.

AVS on standalone terminals

When you use MOTO with AVS on a standalone terminal, this is what happens:

• The issuer declines or authorizes the payment.
• If the issuer didn't decline the payment, the terminal shows the result of the AVS check and prompts you to Approve or Decline the transaction.

If you have second thoughts about the transaction and select Decline, we'll take care of canceling the authorization or, if the payment has already been captured, refunding the shopper.

Enable MOTO and AVS

1. Contact our Support Team to enable MOTO for the account that you want to use for processing MOTO payments.
   If you want to add an AVS check to the flow, ask our Support Team to enable that too.

2. Configure the maximum transaction amount that the terminal allows for a MOTO transaction:

   1. Log in to your Customer Area.
   2. Go to In-person payments > Terminal settings (or select a specific terminal) and select Payment features.
   3. Enter the MOTO max amount.

   4. Select Save.

3. If you are adding an AVS check to the MOTO flow, make sure that you receive the AVS response:

   1. In your Customer Area go to Developers > Additional data.
   2. Select Acquirer result and Raw acquirer result.

   3. Select Save configuration.

4. Configure a capture delay.

Make a MOTO payment

With a Terminal API integration, proceed as follows to trigger the payment terminal to prompt you to enter the card details:

1. Make a PaymentRequest that contains a SaletoAcquirerData field with the MOTO tender option specified in one of the following formats:

   • Option 1: a JSON object converted to a Base64 encoded string.
     Encode {"tenderOption": "MOTO"} to Base64, and pass the resulting string:
     "SaleToAcquirerData": "eyJ0ZW5kZXJPcHRpb24iOiAiTU9UTyJ9"

   • Option 2: a key-value pair:
     "SaleToAcquirerData": "tenderOption=MOTO"

   The format that you use here, will also be the format of the AdditionalResponse that you receive.

   If there are more tender options or other data elements that you need to pass in the SaleToAcquirerData field, see Add information to a payment.

2. When prompted, enter the shopper's card number and CVC code on the payment terminal.

3. If you enabled AVS, enter the shopper's postal code (zip code) and house number on the payment terminal.

4. Note that the payment response contains:

   • EntryMode: Keyed.
   • AdditionalResponse: depending on the format that you used in the SaleToAcquirerData field, this is either a Base64-encoded string that you need to decode to get a JSON object, or a string of key-value pairs separated by &. This includes posEntryMode=MKE.
     If you enabled AVS, it also includes avsResult and avsResultRaw.

5. If you enabled AVS, check the avsResult and avsResultRaw against our list of AVS responses for point of sale. It is possible the issuer authorized the payment even though the AVS check was inconclusive.

6. When the issuer authorized the payment, decide whether you trust the transaction. If not, cancel the authorization. If you do not cancel the transaction, the payment will be captured.

Testing MOTO payments

To test a MOTO payment with an AVS check:

1. Make a MOTO payment as described above.
2. When prompted to enter card and address details on the payment terminal, use the details for one of the test cards listed under Test Address Verification System (AVS). These test cards can be used for both online and point-of-sale AVS tests.

See also