Authentication, applied proportionately.
EMV 3-D Secure 2 with frictionless and challenge flows, strong customer authentication where regulation requires it, and exemption handling where the route and jurisdiction support it.
Authentication is a conversion decision as much as a compliance one
Challenging every transaction is compliant and expensive: each extra step costs completed checkouts. Challenging none is not an option where strong customer authentication applies. The work is in applying the right treatment per transaction, using the exemptions and frictionless paths that the rules already permit.
From request to reconciled
Assess
Transaction attributes, market and the rules in force determine whether authentication is required, optional or exempt.
Share data
3-D Secure 2 passes richer context to the issuer, which is what makes a frictionless outcome possible.
Frictionless or challenge
The issuer decides. Most authentications can complete without the customer seeing anything; the rest present a challenge.
Apply exemptions
Where an exemption is available and appropriate on the route and in the jurisdiction, it is used to avoid an unnecessary step.
Authorize
The authentication result is carried into the authorization, including the liability position it establishes.
What 3ds & authentication covers
EMV 3-D Secure 2
The current protocol generation, with richer data sharing and a mobile-appropriate challenge experience.
Frictionless flow
Where the issuer is satisfied by the data shared, the customer completes without an additional step.
Challenge flow
A proper challenge experience when the issuer requires one, handled inside the hosted or embedded checkout.
Strong customer authentication
Applied where regulation in the relevant market requires it.
Exemption handling
Exemptions are requested where they are available and appropriate on the route and in the jurisdiction.
Liability treatment
A successful authentication can change the liability position for the transaction according to scheme rules.
Authentication analytics
Challenge rate, abandonment at challenge and authentication success reported per corridor and per issuer.
Integrated with routing
The authentication result is an input to the authorization and to retry and cascade behaviour.
Why teams choose it
- Fewer unnecessary steps. Frictionless and exemption paths keep customers out of challenge screens where the rules allow.
- Compliant where required. Strong customer authentication is applied where it is mandated, not skipped.
- Visible cost of friction. Abandonment at the challenge step is measured, so the trade-off is explicit.
How you connect
- Fully handled within the hosted payment page and embedded checkout.
- Server-to-server integrations receive the authentication result and the required redirect handling.
- Authentication outcome is available on the payment record and in webhooks.
What you can accept
- Cards
- Wallet-tokenized cards where a challenge applies
Availability depends on merchant category, jurisdiction, underwriting and the applicable payment or acquiring partner.
How it is controlled
- Authentication is performed by the issuer through the 3-D Secure protocol, not by Flowa Pay.
- Challenge screens are rendered inside the payment surface, never in your own form.
- Authentication results are recorded against the transaction for audit.
Flowa Pay provides the payment technology and orchestration layer. Acquiring, scheme settlement and regulated payment services are provided by licensed acquiring and payment partners under their own authorisations.
Common questions
No. With 3-D Secure 2 most authentications complete frictionlessly, because the issuer receives enough context to decide without involving the customer.
Only where an exemption genuinely applies and is supported on the route and in the jurisdiction. Where strong customer authentication is required, it is applied.
The issuer. Flowa Pay supplies the data that makes a frictionless outcome more likely, but the decision is not ours.
It can. A successful authentication can shift the liability position for the transaction under scheme rules, which varies by scheme, market and transaction type.
Ready to put 3ds & authentication to work?
Talk to our team about your corridors, your volumes and the routes that fit your business.