3DS v1: Workflow descirption
This page describes how to integrate 3‑D Secure v1 with 8B PSP. It outlines the full sequence model we use, and lists the API calls, request/response fields, and webhook behaviour you need to implement.
Applicable Payment Methods
| Payment Method Name | Country | PM API Code |
|---|---|---|
| Bank Cards | 🇺🇿 Uzbekistan | BankCardUZ |
Roles & Terminology
| Term | Description |
|---|---|
| Frictionless Flow (FF) | Issuer authenticates without a visible challenge |
| Challenge Flow (CF) | Issuer requires a cardholder challenge (OTP, app confirm, etc.). |
| Method URL / 3DS Method | A lightweight background call in a hidden iframe that helps the issuer collect device data. |
| paReq: | Payer Authentication Request - message sent from the merchant to the issuer via ACS to start 3DS auth. |
| termUrl | Merchant’s callback URL where the ACS sends the authentication result after challenge completion. |
| mdOrder | Merchant data field (often order identifier) used to correlate 3DS authentication with the transaction. |
| acsUrl | Access Control Server URL provided by the issuer for redirecting the cardholder during challenge flow. |
End‑to‑end Sequence Overview
Download in high resolution
Statuses
All challenge-related actions will be carried out during the "AUTHORIZATION_REQUESTED" status.
Updated about 1 month ago