When processing card payments, some payment processors require 3D Secure to be performed within their own system and not by an external provider. For these processors, PCI Booking’s integration skips our 3D Secure authentication altogether and relies solely on the processor’s authentication. If you process payments through one of these processors, this page does not apply to you. To check whether a processor performs 3D Secure itself, call Get Payment Gateways: it returns
ThreeDsSupportedBy = PaymentProcessor for these processors.Merchant Details in 3D Secure
Every 3D Secure authentication is performed in the name of a merchant. The cardholder sees the merchant’s name in the challenge, and each card network needs the merchant’s acquirer details. PCI Booking uses either its own default merchant details or merchant details that you provide from your acquirer.
Once you provide us with your merchant details, we perform 3D Secure only on the cards those details cover. Make sure you provide the details for all the card networks you want 3D Secure on.
Cards Without Merchant Details
In the card form, a card from a network that 3D Secure does not run on, such as JCB or Diners Club, is never authenticated. TheUnavailThreeDSAuth parameter of the card form request decides what happens: with Accept (the default) the card is tokenized without 3D Secure data, and with Reject the cardholder is sent to your failure URL.
A Visa, Mastercard, American Express or Discover card without merchant details cannot complete the challenge. Depending on the response, UnavailThreeDSAuth decides what happens, or the cardholder is sent to your failure URL.
In the Payments Library, list every card network you accept in the ThreeDsBrands of your CardPay settings. Cards from networks that 3D Secure does not run on, such as UnionPay, are charged without 3D Secure.
Passing a
merchantName that is not registered does not return an error. PCI Booking falls back to its default merchant, and the cardholder sees PCI Booking’s name in the challenge. If your own name is not appearing, check that merchantName exactly matches the reference you registered.What Information Is Needed
- Merchant identity. Business name (as displayed to the cardholder during the challenge) and website URL.
- Acquirer details. For each card network (Visa, Mastercard, American Express, Discover): Acquirer BIN, Merchant ID (MID) and Merchant Category Code (MCC).
- Reference (card form only). A unique name for each merchant, which you send as
merchantName.
Registering a Merchant
For one merchant, submit the online form. For several, fill in one row per merchant in the spreadsheet template and send it to support@pcibooking.net. Support confirms by email when each merchant is ready. Do not sendmerchantName for a merchant before that confirmation.
Next Steps
Hosted Card Entry Form
Card capture with 3DS support
Card By Link
Remote card capture with 3DS support
Payments Library
Card pay with 3DS support
3DS Auth Management
Manage stored 3DS authentication data

