Public
3D-Secure
Operation confirmation with 3D-Secure
What is the 3D-Secure confirmation?
Authentication of the card on the side of the issuer bank, which guarantees the security of the transaction.
Possibilities
  • Self-supporting work with 3D-Secure issuer bank - API MPI
  • Passage by the client 3D-Secure, on the side of LiqPay, with the return to the company's website
  • Passage by the client 3D-Secure, on the side of LiqPay, with the return to checkout LiqPay
How the 3D-Secure conformation works
1
Without returning to the site
  1. Client pays for the goods or service on your website.
  2. You send the request for withdrawal from client's card by the one of LiqPay APIs.
  3. As a reply from LiqPay API, returns status 3ds_verify - it means, confirmation is required from 3D-Secure to finish the payment.
  4. For 3D-Secure confirmation, you are redirecting client to the redirect_to, received as a reply from LiqPay API.
  5. Client confirms payment via 3D-Secure.
  6. LiqPay returns the transaction status to the server-url of the company.
2
With returning to the website
  1. Client pays for the goods or service on your website.
  2. You send the request for withdrawal from client's card by the one of LiqPay APIs.
  3. As a reply from LiqPay API, returns status 3ds_verify - it means, confirmation is required from 3D-Secure to finish the payment.
  4. To confirm 3D-Secure, you redirect the client to the received redirect_to, by adding an additional GET parameter return_to, to the request, specifying the address in which to return the client after passing the 3DS.
    For example: https://www.liqpay.ua/api/3ds/request/fsjj4234hkhjk?return_to=https://yoursite.com/3dsreturn
  5. After verifying 3DS the client will be redirected to the address return_to. In addition to this address as the GET parameter will be sent liqpay_token.
    For example: https://yoursite.com/3dsreturn?liqpay_token=fsjj4234hkhjk
  6. To complete the payment, you must send the request according to the documentation.