New Case Study: A U.S. Issuer’s Experience with Visa’s IDX Solution

New Case Study: Visa’s IDX Solution

Read it here

3DS replay: What we are seeing and how you can maximize approvals

Imagine a scenario that goes like this:
You get an order and send it through to be authenticated and boom. An error is returned. Now what.

Well – if you are operating an online business in the EU (European Union) and are affected by government mandates and PSD2 SCA enforcement (right around the corner December 31, 2020), it means the order is declined.  That’s a lost sale and a hit to your bottom line. All because of a transaction error?

But there’s good news and this is where our 3DS replay solution comes in. Not only does 3DS replay give you liability shift, it helps you from losing a good sale. It can help you save revenue and lower the amount of declines due to EMV® 3-D Secure errors on transactions.

Based on early observations from our 3DS replay pilots:

In total, 67% of errors replayed have resulted in a status that has gained liability shift – for a total of $21.7 million saved in liability shift¹.

As a merchant, that’s got to sound good, right?

So, let us tell you how 3DS replay works.

– It’s a capability with three different dynamic routing scenarios that Cardinal built solutions to that solve for attempts and errors.
– When the merchant runs a transaction down the EMV 3DS protocol, if for any reason an attempts or an error is returned, Cardinal automatically replays that same transaction down 3DS 1.0 to maximize the chance of a successful authentication.
– It can be tailored based on what criteria each merchant wants their transactions routed down the 3DS 1.0 rails by – MID (merchant ID), PID (processor ID), network, or even by only errors, only attempts, or both.
– And – we route those transactions accordingly so that you get the most benefit. No work on the merchant’s part, we do all the heavy lifting!

In early results from our pilots, Cardinal has seen that when an ”attempts” status would have been returned, but the transaction was instead re-routed down 3DS 1.0:

– 74% of those attempts transactions that were replayed ended up as fully authenticated. That 74% translates into $12.4 MILLION that were upgraded to fully authenticated.¹

In certain instances, Cardinal has insight into whether a transaction needs to be re-routed based on issuer readiness before an authentication request is even built. We call this “authentication not available at ACS.” In these cases, early results have shown that:

– 67% of transactions ended up as fully authenticated. That 67% translates into $702 MILLION in transactions that would have been an attempts or worse, and became fully authenticated¹

These are early findings, but impressive ones. If you think your business could benefit from 3DS replay, let’s talk. Contact us today.