Overview

Required plan

This feature or setting is available to all customers on any Recurly subscription plan.

Definition

MOTO (Mail Order / Telephone Order) transactions allow businesses or agents to accept billing information and process payments by request of customers in a card-not-present manner. 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.

Key details

• Improved customer experience: Facilitate smooth transactions for customers who prefer phone or mail orders, enhancing their overall experience.
• Flexible payment options: Diversify your payment channels, catering to a broader segment of customers and enhancing accessibility.
• Enhanced gateway support: MOTO transactions are supported by a plethora of prominent gateways, ensuring versatility and ease of integration.

Key details

MOTO indicators are exclusively reserved for certain use cases. These are one-time customer-initiated transactions using fresh billing details that are entered by the Merchant into a billing system that the customer typically does not have access to, like a back office system or Virtual Terminal.

Recurly's MOTO transactions play a crucial role in expanding merchant offerings and revenue channels. However, it's pivotal to note that MOTO indicators should not be used improperly for merchants in regions where PSD2 and SCA are compliance requirements. Recurring transactions remain untouched, continuing their regular course and are not considered MOTO.

Many gateways support MOTO transactions including Adyen, Braintree, Chase Orbital, Cybersource, Stripe, and WorldPay. However, before enabling MOTO transactions, it's important to enable the support for this specific transaction classification in your account if your use case qualifies.

In cases with gateways like Adyen, while MOTO transactions are supported, they often require the completion of additional documentation. As a precaution, it's always wise to speak with your gateway to clarify any concerns.

Gateway configuration

To begin, follow these steps:

1. Contact your Gateway: Ensure you have MOTO transactions enabled.
2. Documentation (if necessary): Complete any paperwork your gateway requires. Certain gateways require additional documentation – please complete this step to avoid errors in processing.

Recurly Configuration:

Enablement of MOTO on each gateway can 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. Select the MOTO configuration button and save changes.

If you are using Gateway Routing, ensure you are routing to the proper gateways to avoid errors in processing.

Can I use MOTO transactions if my customer is in session on my website?

No. When a customer is in session on your website, this is considered a Customer Initiated transaction and is subject to PSD2 and SCA compliance mandates where applicable. To avoid regulatory fines from the card brands, do not classify these transactions as MOTO.

How can I process a MOTO transaction through Recurly?

If you are integrating to Recurly via API from your back office, ensure you are classifying your transactions through the /purchase endpoint as MOTO and have your gateway settings set to MOTO specifically.

You may also add Billing Information and create Invoices directly within your Recurly control panel.

Transactions processed from your website directly by customers, and your recurring subscriptions will not (and should not) be classified as MOTO.

What’s the difference between MOTO and Unscheduled Card on File MIT Transactions?

MIT (Merchant Initiated Transactions) generally occur without any direct interaction with your customer, such as processing a transaction on a pre-approved schedule outside of a subscription environment, such as a Top Up or Resubmission scenario.