MOTO Transactions

Overview

Recurly has added support for the MOTO (Mail Order / Telephone Order) transaction type. This is used in scenarios where you or your agents may be accepting and inputting billing information on behalf of your customers. For example, MOTO will be passed when inputting billing information through the Recurly Admin UI or when specified via the API (such as for transactions processed by you or your agents via a custom-built, internal checkout page) once enabled.

Importance

While this transaction type is optional for most use-cases, it is required for merchants in-scope of the PSD2 mandate as it will indicate to the customer’s issuing bank that the transaction is being processed on their behalf by a third-party. This should prevent a 3DS2 challenge from being presented. If you are not in-scope of PSD2, you do not need to enable this setting.

Please note, MOTO indicators will only be passed for initial merchant initiated transactions using new billing information or for merchant initiated one-time transactions using stored billing information. Recurring transactions will not be affected and will continue to be passed unchanged.

Supported Gateways

Currently, MOTO indicators are supported for the following gateways:

  • Adyen**
  • Braintree
  • Chase Orbital*
  • Cybersource
  • Stripe
  • WorldPay*

*MOTO transaction support must be enabled for your account before you’re able to pass this transaction type.
**MOTO transactions can be processed by your gateway by default, though you will need to complete additional documentation. Please contact your gateway for more information.

Configuration

There are two steps that must be completed in the order listed to enable support for MOTO transactions:

  1. Enable MOTO support on your gateway.
  2. Enable MOTO support in Recurly.

Gateway

Before enabling MOTO support within Recurly, please be sure to contact your gateway to ensure that your account is correctly enabled to support this transaction type. Skipping this step may result in unintentional declines depending on your payment gateway.

Recurly

Once support for MOTO transactions are enabled for your gateway account, you can move forward with enabling this setting in Recurly. This will be done on the configuration page for the gateway where MOTO transactions will be processed. Note, this transaction type will be routed according to Recurly’s standard routing logic, so please be sure to keep that in mind if you have multiple gateways configured.

Enablement will be completed via the following steps:

  1. From the Recurly Admin UI, select Configuration > Payment Gateways from the menu on the left.
  2. Select Options > Edit for the appropriate gateway instance.
  3. Enable the MOTO configuration button and save changes.
1630