How to make a Mail/Telephone Order (MOTO) transaction without 3DS?

This is a common query that we encounter, and we understand that it can cause a bit of confusion. 3D Secure (3DS) is a security protocol designed to add another layer of security for online credit and debit card transactions. While this has been highly beneficial in reducing fraud and enhancing customer security, we acknowledge that not all transaction scenarios may fit into this security structure.

One such scenario is the Mail Order/Telephone Order (MOTO) transaction. MOTO transactions are those which are processed when the card is not physically present. In these cases, the customer provides their card details over the phone, through mail, fax, or via an online form.

Given that 3DS is particularly geared towards securing 'Cardholder Not Present' (CNP) transactions, it may seem that MOTO transactions should always trigger the 3DS protocol. However, MOTO transactions are traditionally considered a separate category, often exempted from 3DS protocols due to the inherent trust in the transaction process.

If you're finding that your MOTO transactions are consistently enforcing 3DS, it's possible that a setting adjustment is necessary or that there might be some misunderstanding in how these transaction categories are being processed. Understanding these nuances can help ensure you're leveraging the security benefits of 3DS where needed, while still maintaining the smooth, user-friendly experience that MOTO transactions can offer.

Solution

In order to correctly flag the transaction in the card network using the wallee API you need to make sure that when you create the transaction, that you set the customer presence flag correcty. Here an arbitrary example, where the relevant part is highlighted.

{
"currency": "CHF",
"customersPresence": "NOT_PRESENT",
"lineItems": [
{
"amountIncludingTax": "15",
**"name": "CNP Transaction",
**"quantity": "1",
"type": "PRODUCT",
"uniqueId": "1"
}
]
}

In this case, the transaction will be performed without 3DS and will be flagged as CNP Transaction. This will cause the issuer to understand that the transaction is exempted and should be authorized with the corresponding liability shift.

Solution ​

Solution