Answers
How do you test 3DS2?
In short
3DS2 testing covers frictionless and challenge flows, exemptions, fallback to 3DS1, issuer behaviour, scheme test cards and end-to-end authorisation outcomes.
Short answer
3DS2 testing covers frictionless and challenge flows, exemptions, fallback to 3DS1, issuer behaviour, scheme test cards and end-to-end authorisation outcomes.
What this actually means in practice
Use scheme test cards to cover frictionless, challenge, decline, attempt and trial scenarios. Validate exemption claims (TRA, low-value, recurring) end-to-end. Test issuer step-up. Test fallback. Validate that the authorisation message carries the correct ECI and CAVV and that authorisations decline cleanly when 3DS data is missing.
The most common pitfall
Cert passes, production fails — usually a config drift between the cert and live processor.
What to do next
Add a 3DS2 regression pack to CI that exercises every exemption path and fallback.
Frequently asked questions
Does Forth Systems help with this?
Yes — Forth Systems works with banks, payment institutions, insurers and infrastructure operators on exactly this kind of work. Engagements start with a fixed-scope assessment so you see the shape before committing.
How experienced is the team?
Engagements are staffed by named, UK-based senior engineers — not a rotating offshore pool. References from the second line of comparable clients are available on request.
Where are you based?
Edinburgh-based, delivering UK-wide with onsite presence in London and across Scotland as required.
How fast can we start?
Most engagements start within 2-4 weeks of a signed SoW, faster where an existing supplier framework is in place.