All card schemes may have unique merchant onboarding requirements for 3D Secure. This page outlines what we are aware are the current requirements of the card schemes we support through Ravelin 3DS.
We strongly recommend that all Ravelin customers speak to their acquirer(s) or the card schemes directly, to understand what may be required. We have provided some guidance here based on what we currently understand for each card scheme we are certified with.
American Express encourages merchants to speak to their acquirer(s) to ensure that authentication data can be passed in the authorisation and other payment related messages. They also have the following acquirer responsibilities for merchant enrolment:
You can contact American Express here.
We are not aware of any specific enrolment requirements for Cartes Bancaires. The migration of a merchant does not require any prior declaration to them either.
You can contact Cartes Bancaires here.
We are not aware of any specific enrolment requirements for China UnionPay.
You can contact China UnionPay here.
Discover adopts a trust model for the onboarding of merchants. This allows them to trust and accept all incoming traffic from merchants connected to compliant 3D Secure providers.
You can contact Discover here.
We are not aware of any specific enrolment requirements for eftpos.
You can contact eftpos here.
We are not aware of any specific enrolment requirements for JCB.
You can contact JCB here.
Merchant enrolment is handled at the acquirer level. Mastercard recommend that acquirers and merchants remain aligned on the values used for acquirerBIN and acquirerMerchantID.
You can contact Mastercard here.
We are not aware of any specific enrolment requirements for Visa.
You can contact Visa here.
Was this page helpful?