Your 3D Secure service

If you have implemented your own MPI service for the 3D Secure, when you may send the ECI, UCAF/CAVV, and XID values in (pre-) authorization request.
In this case, the transaction will be sent to the acquirer without any steps in between and the result is returned immediately to you.

Required parameters

Your request to payabl should include those parameters:

mpi_avv
mpi_eci: In the case of Visa: mpi_eci 5 or 05 (verified), 6 or 06 (attempted), 7 or 07 (not verified). In the case of Mastercard: mpi_eci 2 or 02 (verified), 1 or 01 (attempted), 7 or 07 (not verified).
mpi_ds_transaction_id: Needed for new EMV 3DS (formally 3DS 2.2) standards

Sandbox testing

You can test your 3D Secure flow in our Sandbox environment.

You need to add the above mentioned parameters and add "fake" data in the API request parameter.

Request example:

https://sandbox.payabl.com/pay/backoffice/payment_authorize?merchantid=gateway_test_3d&amount=10&payment_method=1&currency=EUR&orderid=Payabl-Test&notification_url=https://webhook.site/c542d9af-557c-4f45-9c2a-deb08cf56aa6&[email protected]&customerip=127.0.0.1&ccn=4149011500000147&exp_month=11&exp_year=2027&cvc_code=123&mpi_avv=testmpiavv&mpi_eci=05&mpi_ds_transaction_id=testmpids&signature=1512908ad71422ba93cc32565aae3200dcfa3a55

Response example:

transactionid=106398029&transid=106398029&status=0&errormessage=&errmsg=&amount=10&price=10&currency=EUR&orderid=Payabl-Test&user_id=1134553

🚧

Contact Technical support for information on Acquirer Merchant ID for registration in MPI.