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 / News
Increasing approval rates and stopping fraud for merchants is our bread and butter. And building our own EMV 3DS Server allows us to do this and more. Senior Product Manager for our 3DS solution, Catherine Jones, shares what this means for PSPs and your online business…
Share this article:
The introduction of 3D Secure 2 (3DS2) presented us with an interesting decision. Yes, we would continue to support your use of 3DS through your payment service provider (PSP) as we always have. But could we offer even more value by building our own Server and software development kits (SDKs) rather than partnering with a third party?
By choosing to go ahead, we knew we could provide our merchant clients with better data and an improved user experience. It would also allow us to give you more control over your authentication and exemption preferences.
So what does this really mean for the merchants and PSPs that work with us…
Great 3DS authentication relies on quality data being formatted correctly and shared with the right stakeholders. Issuers need all the data available to make informed decisions about whether to apply frictionless authentication instead of a challenge, or approve an exemption.
PSPs and merchants also need as much data as possible to support fraud and authentication strategies. This data is critical to monitor performance and identify potential issues in the authentication flow.
Frustrations around lack of 3DS data is something we have encountered time and time again. And this has played a huge role in our decision to build our own Server.
By taking this into our own hands, we remove all of this red tape. We can provide access to all the data you need, and analytics and reporting to show exactly what responses we get.
We simply couldn’t guarantee access to this level of data with a third party provider.
We’re a strong and established brand in the fraud detection market. We’re known for our machine learning approach, which prioritizes your individual business over generalized market data. Our existing payment fraud capabilities make all the difference here. Especially with the ability to initiate the authentication process and determine what fields are sent over to the issuer.
Most of the fields in the 3DS Authentication Request (AReq) are similar to those we currently use and enrich to detect payment fraud, such as the browser IP. There is also a ‘suspicious account indicator’ field, which our existing fraud detection capabilities can fill accurately.
On top of the data benefits, 3DS is another tool that can be used to help reduce fraud and chargebacks. With our insights, we know when 3DS is the right tool to use – whether that be for suspicious customers or when regulation requires authentication.
The PSD2 roll-out has highlighted the range of different responses to strong customer authentication (SCA) and 3DS across Europe. One size definitely doesn’t fit all.
Merchants and PSPs are still testing new strategies to provide the optimum experience for consumers with different issuers and across regions. We believe you should have the freedom to decide when to request a challenge, an exemption or just data share with issuers.
The 3DS Requestor Challenge Indicator is a field in the Authentication Request where you can decide just that. We include this field in our 3DS API, so that you can let us know your preference. Our 3DS Server will then send your request onto the card schemes and issuers.
You can get the insights you need to decide what action to take, and we will act on your decision. We can also help you decide what to do with 3DS through our payment fraud and transaction optimization capabilities.
We know that frictionless authentication and exemption capabilities are important. And our goal is to support you in providing the best possible buying experience for your customers. Only the latest 3DS versions can guarantee this.
By building our own 3DS Server, we can support these versions for your chosen card schemes much sooner than others in the market. Better still, we can prioritize what matters to our customers – be that card schemes, certifications or versions.
For our customers, building our own 3DS Server and SDKs ultimately means that you have the best authentication experience possible. We can provide you with as much data as you need to test and define the ideal 3DS strategy for your business. We commit to staying on the pulse with updates and certifications, so that you can take advantage of the latest 3DS advances and benefits. And total transparency is a must, so you can make use of the best available data with nothing held back.
Learn more about how you can take control of your authentication process.
Catherine Jones, Senior Product Manager
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?