PSD2 and 3DS FAQs in Mews Payments

The second Payment Services Directive, or PSD2, is a European regulation that requires payment providers to authenticate all payment transactions in order to protect consumers. Mews Payments uses an authentication solution called 3-D Secure, or 3DS, for PSD2 compliance. 3DS is the step where the cardholder confirms a card payment with their bank before the payment goes through. PSD2 includes Strong Customer Authentication, or SCA, requirements. SCA is the requirement that the cardholder proves their identity in two ways, for example with a password and a code on their phone, before a payment is approved. You can learn more about SCA requirements and the affected countries on the Stripe support page Strong Customer Authentication.

 

These FAQs are for properties that take card payments with Mews Payments and for the users who manage payments at the property. You need these answers when a guest's payment is waiting for authentication, when a payment is declined because the guest did not approve it, or when you want to charge a stored card after the guest has left. You see the status of each payment in the Billing tab of the customer profile in Mews Operations. 3DS only applies to cards issued in the European Economic Area and the United Kingdom, and the card issuer makes the final decision on every exemption. When a guest authenticates a payment with 3DS, the card issuer, not your property, is liable for fraud chargebacks on that payment.

 

In this article, you can find answers to the following questions:

 

What is 3DS?

3DS is an authentication solution that provides an extra layer of security for your payments. 3DS requires users to authenticate payments by entering a code or password or using fingerprint unlocking on their device.

 

How does 3DS work?

The 3DS flow works like this:

 

  1. A guest makes a booking.

  2. The booking triggers a payment.

  3. The bank decides whether to authorize the payment.

  4. The card issuer sends an authorization email to the guest for payments waiting for authorization.

  5. The guest receives the email and verifies the payment.

 

Payments can take longer to process depending on whether they are on session or off session.

 

  • On session are payments where the user provides their card details and the card is charged simultaneously. For example, if a guest books a stay with the booking engine.

  • Off session payments are payments where the user provides their card details for the property to charge their card later. For example, if Mews Operations stores the card, then charges it later for minibar charges.

 

The processing speed depends on the time it takes the guest's bank to verify the payment, but typically the verification of On session payments is faster.

 

Which payments are subject to 3DS?

Physical, not virtual, payments from cards issued in the European Economic Area, or EEA, and the United Kingdom are subject to 3DS. There are some notable exemptions:

 

  • Payments below EUR 30: Transactions below EUR 30 are considered “low value” and may be exempt from Strong Customer Authentication, or SCA.

  • Authorization for multiple charges: Once a guest validates a card at your property, you don't need to validate payments on that card later.

  • Mail Order or Telephone Order, or MOTO: MOTO payments are payments where the cardholder is not present, for example payments that an online travel agency passes on to your property. You can learn more in the question When is a transaction considered a MOTO? in this article.

 

As with all exemptions, the issuer makes the final decision about whether the payment requires authentication.

 

When is a transaction considered a MOTO?

According to recent SCA regulation updates, Mews can process all third-party payments, such as payments from online travel agencies, or OTAs, as MOTO payments, that is, Mail Order or Telephone Order payments. MOTO payments are applicable for an exemption from 3DS verification, but the cardholder's bank makes the final decision.

 

The MOTO flow works like this:

 

  1. A guest makes a payment through an OTA.

  2. Mews payment providers process the payment and request an exemption from the cardholder's issuing bank.

    • If the bank declines the exemption, your customer must verify their payment through 3DS.

    • If the bank accepts the exemption, the payment goes through without verification, as do all subsequent payments with that card.

 

Are preauthorizations subject to 3DS?

Preauthorizations are subject to 3DS payment flows just like other payments. A preauthorization is a temporary hold on an amount on the guest's card that you can later charge or release.

 

Can I still charge a credit card after the guest has left?

You can still charge a credit card after the guest has left if the guest has already authorized a payment on that card. Once a guest validates a card at your property, you don't need to validate later payments on that card.

 

How can I collect money from guests that do not approve the payment?

To collect money from guests who do not approve a payment, process payments through your Mews Terminal to prevent unapproved payments as much as possible. Mews Terminal payments, requiring guests to input a personal identification number, or PIN, are not subject to 3DS. Mews now has multi-charge authentication enabled, so you can prevent unapproved payments by ensuring your guests validate their first payment at your property.

 

You can learn more about Payment Card Industry, or PCI, compliance in the help article PCI compliance.

 

Additional resources:


Was this article helpful?
10



Feedback