> ## Documentation Index > Fetch the complete documentation index at: https://developers.pcibooking.net/llms.txt > Use this file to discover all available pages before exploring further. # 3DS Merchant Setup > Configure 3D Secure merchant settings in PCI Booking. MPI credentials, 3DS2 support, and card scheme enrollment. 3D Secure authentication requires merchant information to be presented to the cardholder during the challenge screen. By default, PCI Booking provides its own merchant details, meaning the cardholder sees "PCI Booking" as the merchant name during the 3DS challenge. To display your own merchant name instead, you can provide your merchant details to PCI Booking. ## 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](https://pcibooking.net/3d-secure-merchant-information-required/) 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. 1. Download the [merchant information spreadsheet template](https://pcibooking.net/wp-content/uploads/2023/06/3DS-merchant-data.xlsx). 2. Fill in the merchant details for each of your merchants. 3. Submit the completed spreadsheet to [support@pcibooking.net](mailto:support@pcibooking.net). 4. When generating a card capture form, include the `merchantName` parameter 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 `merchantName` parameter in your API calls. For a single merchant, submit via the [online form](https://pcibooking.net/3d-secure-merchant-information-required/). For multiple merchants, download the [spreadsheet template](https://pcibooking.net/wp-content/uploads/2023/06/3DS-merchant-data.xlsx), fill in one row per merchant, and send to [support@pcibooking.net](mailto:support@pcibooking.net). ## Next Steps Card capture with 3DS support Remote card capture with 3DS support Manage stored 3DS authentication data