Flexible 3D is a feature that allows you to enable/disable 3D Secure at an API level. The Flexible 3D forces whether or not to complete a transaction with the 3D secure verification.
Fraud related chargebacks can be avoided altogether by using 3D Secure, given the extra layer of security imposed by the cardholder needing to identify him or herself. Fraud-based chargebacks are no longer possible when using the 3D secure.
Example 1:
Credit card transactions which are processed with the 3D Secure verification, require a form of authentication of the customer during a payment process. When the 3D secure is required upon releasing a payment, setting the Flexible 3D to false, will disable the 3D secure verification process. Resulting in releasing a payment that is “Not Enrolled, Liability”.
Example 2:
When Flexible 3D is set on true, the verification is mandatory to finalize and release a successful payment. Credit card transactions which were originally processed without the 3D Secure protocol are now required to complete the 3D Secure verification too. By enforcing this measure - finalizing the payment only upon completing the 3D Secure verification - all released payments will be enrolled with the 3D authentication. 3D Secure Result: Enrolled Liability
Flexible 3D Secure and Dynamic 3D Secure settings Activating Flexible 3D secure will override the rules of the Dynamic 3D settings. For more information about Dynamic 3D Secure, please refer to the page, Dynamic 3D, What it is
Flexible 3D is a feature that allows you to enable/disable 3D secure at an API level.
For Full API calls on Flexible 3D, please refer to the API section on our documentation.
Parameter | Type | Description |
---|---|---|
type | string | Specifies the payment flow for the checkout process. Options: redirect and direct. |
gateway | string | The unique gateway_id to immediately direct the customer to the payment method. You retrieve these gateways using a gateway request. Option: VISA and MASTERCARD. |
An extra step is required when processing a direct credit card transactions. Because a direct “server to server” credit card payment takes place on the checkout page of the webshop instead of on the payment page of MultiSafepay, it is up to the merchant to refer the customer to the verification page to complete the payment.
Parameter | Type | Description |
---|---|---|
reference_id | string | Authorise 3D response reference_id |
MD | string | Authorise 3D response MD |
Feedback
You're missing something out and would like us to fix it? Suggest an improvement to this page!
Other languages
Liever uitleg in
het Nederlands? Neem contact op met uw accountmanager.
Vuoi ricevere
informazioni in italiano? Contatta il tuo account manager.
Falls Sie eine deutschsprachige Erklärung bevorzugen, kontaktieren Sie bitte Ihren Kundenbetreuer.
Prefieres tener la
explicación en Español? Contacta con tu gerente de cuentas.
Vous préférez une
explication en français? Contactez votre gestionnaire de compte.