1
Flow for every acquirer
EEA and UK
Strong customer authentication
Both
Hosted pages and Altruon.js
Callback
Redirects returned to your page
What Altruon handles
Authentication in your checkout, not in each acquirer's
The customer sees one checkout and one 3D Secure step, whichever acquirer your routing picks. You build it once.
Challenges and redirects handled
Bank challenges and redirects run inside the hosted page and Altruon.js, then hand back to your page through a callback.
Frictionless when the issuer allows it
If the issuer approves without a challenge, the customer never leaves checkout.
One experience across acquirers
With the Altruon Vault, the same 3D Secure flow serves every acquirer you connect. Adding an acquirer never changes your front end.
Travels with a retry
If a payment is retried on another acquirer, the authentication can go with it, so the customer is not asked twice.
Result stored with the transaction
The authentication outcome is kept with the transaction, next to the acquirer response and the gateway reference.
First payments and card updates
The same flow runs at checkout and when a subscriber adds a new card through the hosted update flow.
How it works
From card entry to invoice in four steps
01
Customer submits the card
The card is entered in secure fields on the hosted page or in Altruon.js.
02
The issuer decides
Frictionless approval, or a challenge in the customer's banking app or browser.
03
Result passed to the acquirer
The authentication goes with the payment to the acquirer your rules pick.
04
Charged and written back
The acquirer authorises and the result lands on the invoice in your billing engine.
Disputes Coming soon
Alerts, evidence and refunds in one place, next to the authentication result for each transaction.
More in Protect
