Authenticate payments through 3dsecure.io's JSON API integrated via Juspay Hyperswitch as an external 3DS authentication provider.
3dsecure.io connects to Hyperswitch as an external AuthenticationProvider. It facilitates 3-D Secure verification for online credit and debit card transactions via a JSON API. 3dsecure.io is currently available in Sandbox status on Hyperswitch — it is not yet available for live production traffic.
3dsecure.io uses HeaderKey authentication — a single API key sent as a Bearer token on every request.
API Key
Bearer token issued by 3dsecure.io. Obtained during 3dsecure.io onboarding.
3dsecure.io handles the following flows within Hyperswitch's external 3DS authentication:
Pre-Authenticate
Initiates 3DS authentication — sends card and order details to 3dsecure.io's 3DS server
Post-Authenticate
Completes the flow — retrieves CAVV, ECI, and DS Transaction ID for use in payment authorization
3dsecure.io is available for sandbox/testing use on Hyperswitch. Use this connector to test external 3DS authentication flows before enabling a production 3DS provider.
API key rejected Symptom: Authentication requests return 401 Unauthorized. Fix: Verify the API key stored in Hyperswitch matches the one issued by 3dsecure.io. Keys are environment-specific — sandbox keys do not work in production.
Authentication not completed Symptom: Post-Authenticate returns no result. Fix: Confirm Pre-Authenticate was called first and returned a valid transaction ID. The 3DS flow must follow the pre/post sequence.
A registered 3dsecure.io account. Contact 3dsecure.io for onboarding.
A registered Hyperswitch account, accessible from the Hyperswitch control center.
API Key provided during 3dsecure.io onboarding.
Steps to activate a connector on the Hyperswitch control center
Connector implementation: crates/hyperswitch_connectors/src/connectors/threedsecureio.rs.
Last updated
Was this helpful?
Was this helpful?
