Solutions overview
Harness the power of your data
Support and investigations
Support services for Ravelin
Online payment fraud
Account security
Policyabuse
Marketplace fraud
3DSecure
Resource Zone
Deep dives on fraud & payments topics
API & developer docs
APIs, glossary, guides, libraries and SDKs
Global Payment Regulation Map
Track PSD2 & more with a full report
Blog
The latest fraud & payments updates
Insights
In-depth guides to fraud, payments & security
About Ravelin
Discover the story about Ravelin
Careers
Join our dynamic team
Customers
Read more about our happy customers
Press
Get the latest Ravelin news
Support & investigations
Accept more payments securely
Protect your customer accounts
Policy abuse
Stop policy abuse to protect your bottom line
Ravelin for marketplace fraud
3D Secure
Ravelin 3DS & SDKs
Resource zone
Global Payment regulation map
Read more about our happy custmomers
Blog / Other
An overview of the terminology used in association with PSD2.
Share this article:
PSD2: the payments industry’s favourite acronym. You may already be familiar with the legislation (don’t worry if you’re not - we wrote an introduction to it here), and you’ll know that there’s quite a few technical words thrown into mix.
Today we’re diving a bit deeper and talking through the different acronyms that you’ll often hear in association with the legislation.
See this blog post as your PSD2 glossary - bookmark it, share it with your friends - you know the drill.
3-D secure (3DS) is an additional method of security for preventing fraud during online payments. 3DS requires cardholders to provide additional verification when making a purchase, such as a password associated to an account, to prevent fraudsters from completing the transaction.
An API is a set of clearly defined methods of communication between software components. In the context of PSD2 it means a clear and simple set of methods and documentation that will make it easy to exchange information and transactions between a bank, a gateway and a merchant. This will be a key enabler of open banking. A good example can be found here (link to developer.ravelin.com) of a clear, concise and predictable API documentation.
Account Information Service Providers (AISPs) will be able to extract a customer’s account information data including transaction history and balances, likely to offer tailored finance products and money-saving opportunities, e.g. Moven and Mint. Banks, fintech companies and non-traditional financial services companies currently have the capacity to develop AISP solutions, but banks will likely dominate over third-party providers.
The European Banking Authority is an EU Authority which works to ensure effective regulation and supervision across the European banking sector.
The FCA stands for Financial Conduct Authority, and it is a regulatory body that regulates financial markets to protect consumers and provide a level playing field for the industry. The FCA ensures that the market is regulated and remains fair and effective and also promotes competition.
Know Your Customer (KYC) is a way for a business to verify and identify an online customer. Banks are required to apply appropriate KYC measures to their customers, which may be providing detailed information about a customer when opening an account or asking to provide specific documentary to identify and verify the consumer.
Payments Services Derivative 2 (PSD2) is a piece of European legislation that requires financial services to contribute to a more integrated and efficient payments ecosystem.
Payment Service Providers (PSPs) are companies such as Stripe and Braintree. PSPs are payment gateways that offer online businesses their services for accepting and processing electronic payments.
The Regulatory Technical Standards (RTS) are the regulatory requirements set by the EBA to ensure that payments across the EU are secure, fair and efficient.
Strong Customer Authentication (SCA) is the method of providing additional proof that you are you when purchasing a product. This step is highly effective at stopping fraudsters in their tracks as they additional security measures mean they won’t be provide the proof.
Strong customer authentication (SCA) becomes mandatory for all electronic payments under PSD2, although the provisions relating to SCA will only apply from 18 months after the date of entry into force of the regulatory technical standards (RTS), which is expected lin late 2019. SCA requires at least two of three categories of information for authentication:
At least one of the factors of authentication must be linked to the amount and payee.
Third Party Payment Service Providers (TPPs), also known as third party processors are processors that let you accept payments without a merchant account. A good example of a TPP is PayPal.
The advantage of TPPs is that they allow consumers with additional options to access their money without needing to directly interact with their bank. Under PSD2 regulation, TPPs need to ensure that there are structures in place to provide extensive security of information and consumer data that fit within the scope of the regulation standards.
To learn more about PSD2 and SCA visit our insights page.
Alara Basul, Head Of Content
Blog / Fraud Analytics
Fraud prevention is a delicate balance between stopping fraud and maintaining good customer experiences. But what is the most effective way to measure this outcome?
Ravelin Technology, Writer
Blog / Machine Learning
Online payment fraud is one of the biggest threats facing grocery merchants. And it’s only gotten worse. How are fraudsters using the cost of living crisis to take advantage of your business?
There’s a new fraud threat on the rise – and it’s your customers. First-party fraud is infamously tricky to catch and a huge revenue risk. How can you detect and deter criminal behavior in your customer base?