How It Works
When a 3DS challenge is triggered during card capture, the card network displays merchant information to the cardholder. This information helps the cardholder recognize the transaction and reduces false declines. If you do not provide your own merchant details, PCI Booking’s default merchant information is used. With the default configuration, 3DS authentication is limited to Visa and Mastercard cards only.Three Scenarios
You only collect cards
You capture card details on behalf of another entity (e.g. an OTA collecting cards for a hotel), and payment processing happens outside PCI Booking. No additional configuration is needed. PCI Booking’s default merchant information is used for the 3DS challenge.You collect and charge directly
You capture card details and process payments directly as the merchant (e.g. an online retailer). Submit your merchant information through the 3DS merchant information form to replace PCI Booking’s default details with yours. The cardholder will see your merchant name during the 3DS challenge.You collect and charge on behalf of multiple merchants
You capture cards and process payments for multiple different merchants (e.g. a PMS provider serving multiple hotels). Each merchant needs its own 3DS merchant details.- Download the merchant information spreadsheet template.
- Fill in the merchant details for each of your merchants.
- Submit the completed spreadsheet to support@pcibooking.net.
- When generating a card capture form, include the
merchantNameparameter to specify which merchant’s 3DS details to use for that transaction.
What Information Is Needed
The data falls into three categories:- Merchant identity. Business name (as displayed to the cardholder during the 3DS challenge), website URL, and country.
- Acquirer details. The acquiring bank name, plus per-card-network identifiers: Acquirer BIN, Merchant ID (MID), and Merchant Category Code (MCC). Only provide these for the card networks you process (Visa, Mastercard, American Express, Discover).
- Reference. A unique identifier for each merchant, used to match the
merchantNameparameter in your API calls.
Next Steps
Hosted Card Entry Form
Card capture with 3DS support
Card By Link
Remote card capture with 3DS support
3DS Auth Management
Manage stored 3DS authentication data

