Here’s everything you need to know to make sure you’re in compliance with the Payment Services Directive (PSD2) by the end of 2020
There’s a good chance you’ve heard a lot of talk about the Payment Services Directive (PSD2) recently—and for good reason. It’s about to change the relationship between financial institutions, merchants, and consumers across the European Union (EU) and the European Economic Area (EEA) in a pretty massive way.
In this post, we’ll quickly review what PSD2 is as well as why PSD2 compliance is so important in today’s ever-evolving e-commerce environment, so you can be prepared for what the future of widespread open banking has in store for your business.
Explaining PSD2 in the simplest way possible
If there’s one thing we’ve grown to accept these days, it’s that there’s no shortage of regulations, each with its own ominous-sounding acronym, challenging and changing the status quo of the e-commerce industry. This comes at a time when growing concerns around data privacy and payment security—in the face of new technological innovations—continue to be top-of-mind for regulators, financial institutions, merchants, and consumers. It was really only a matter of time until the broader rules of how we transact online had to fundamentally change.
So, what is PSD2 exactly? In short, it was developed to create a safer, more integrated European payments market, one that ultimately puts more control in the hands of consumers and sets a new standard for online payments across the EU. It was also conceived to even the playing field and increase cooperation and collaboration between banks and fin-tech players.
PSD2 officially went into effect on September 14, 2019. However, because of mounting technical difficulties and delays faced many key players—banks (issuers and acquirers), payments service providers (PSP), merchants, and other fin-tech institutions—when becoming PSD2-compliant, especially around the implementation of Strong Customer Authentication (see below), the European Banking Authority granted an extension for full implementation to the end of 2020.
Once implemented, the most notable changes affecting merchants will include:
Banning (certain) surcharges
Merchants will no longer be allowed to pass through credit card transaction fees (“surcharges”) to their customers for payments made using “consumer” credit or debit cards—i.e. those issued in the name of the purchaser. Merchants will, however, still be able to pass on these surcharges for payments made using business or corporate cards—i.e. those issued in the name of corporate entity—when purchasing business-related goods or services.
Strengthening customer authentication
PSD2 champions Secure Customer Authentication (SCA) and, thus, will require all customers to confirm their identity, assuring that they are the rightful owners of the credit or debit cards they are using to make purchases, via two-factor authentication (2FA). The objective here is to protect both consumers from fraud—due to credit card theft—and merchants from processing potentially fraudulent chargebacks.
As an additional safety measure, Visa and Mastercard will also require merchants to implement 3D Secure (3DS) and/or Apple Pay security solutions in their online and mobile stores.
After implementation, customers will be required to identify themselves via two of the following three methods (for payments made within the EEA):
Not all transactions will require strict SCA compliance. For a full list and explanation of the various exemptions, check out this useful documentation created by Visa.
What comes next?
Obviously, there’s quite a bit that needs to happen before the end of the year to ensure that PSD2 goes into full effect. Here are some key milestones to keep top of mind:
PSD2 compliance made easy with Nexway
Our goal here was to simplify the complexity of PSD2 as much as possible and, hopefully, give you a little more line of sight into what the rest of the year holds as we all work towards full PSD2 SCA compliance. The good news for you: with Nexway as your Merchant of Record, your online sales will automatically be fully compliant with these new regulations. This includes:
With PSD2 compliance looming in the not-too-distant horizon, there’s no better time than now to get prepared.
Nexway can help make this easier than ever. Contact us today to learn more.
Cookie | Type | Durée | Description |
---|---|---|---|
__zlcmid | persistent | 1 year | Ce cookie est utilisé par le chat en direct de Zendesk et sert à stocker l'identifiant du chat en direct. |
_ga | session | 2 years | Ce cookie est installé par Google Analytics. Le cookie est utilisé pour calculer les données relatives aux visiteurs, aux sessions, aux campagnes et pour garder une trace de l'utilisation du site pour le rapport d'analyse du site. Les cookies stockent des informations de manière anonyme et attribuent un numéro généré de manière aléatoire pour identifier les visiteurs uniques. |
_gid | session | 1 day | Ce cookie est installé par Google Analytics. Le cookie est utilisé pour stocker des informations sur l'utilisation d'un site web par les visiteurs et permet de créer un rapport analytique sur le fonctionnement du site. Les données collectées comprennent le nombre de visiteurs, la source d'où ils viennent et les pages visitées sous une forme anonyme. |
AWSALB | third-party | 1 week | AWSALB est un cookie généré par l'équilibreur de charge de l'application dans les services Web d'Amazon. Son fonctionnement est légèrement différent de celui de AWSELB. |
bcookie | third-party | 2 years | Ce cookie est défini par linkedIn. Le but du cookie est d'activer les fonctionnalités de LinkedIn sur la page. |
cookielawinfo-checkbox-necessary | persistent | 1 year | Ce cookie est défini par le plugin GDPR Cookie Consent. Les cookies sont utilisés pour stocker le consentement de l'utilisateur pour les cookies dans la catégorie "Nécessaire". |
cookielawinfo-checkbox-non-necessary | persistent | 1 year | Ce cookie est défini par le plugin GDPR Cookie Consent. Les cookies sont utilisés pour stocker le consentement de l'utilisateur pour les cookies dans la catégorie "Non nécessaire". |
lidc | third-party | 1 day | Ce cookie est défini par LinkedIn et utilisé pour le routage. |
test_cookie | third-party | 15 minutes | Ce cookie est défini par doubleclick.net. Le but du cookie est de déterminer si le navigateur des utilisateurs supporte les cookies. |
UserMatchHistory | third-party | 1 month | Linkedin - Utilisé pour suivre les visiteurs sur plusieurs sites web, afin de présenter une publicité pertinente en fonction des préférences du visiteur. |