Payment
Credit Card

Credit Card Payment Flow

11min

There are 4 types of  flows for  payment methods, namely Direct 3Ds, Redirect 3Ds, Direct non 3Ds, and Redirect non 3Ds.

  •  channels that are only found in Payment products are Direct 3Ds and Direct non 3Ds.
  •  channels that are only found in Checkout products are Redirect 3Ds and Redirect non 3Ds.

What is 3Ds?

3 Domain Secure (3Ds) is a  security standard that allows cardholders to obtain identity verification in an OTP (One Time Password) form to a registered cell phone number during   .

The 3Ds  involves 3 parties, namely cardholders,  Issuing Banks, and Merchants or Payment Gateways. It is done to prevent attempts at  theft and fraudulent acts when transacting with .

The difference between 3Ds and Non 3Ds

  • In  3Ds Flow,     will go through  3Ds security protocol with identity verification in  form of OTP and additional security, namely  FDS (Fraud Detection System).
  • In  Non-3Ds Flow,  only goes through  FDS (Fraud Detection System) security  without using OTP authentication from 3Ds after   enters their  data.



Direct 3Ds



In  Direct 3Ds ,   will continue   registration  on  's  display after going through  FDS calculation  and checking  OTP authentication. The difference with  Redirect  is with   used. The Redirect  uses 's  view after using  OTP authentication checking .

CC Payment Flow - Direct 3Ds
CC Payment Flow - Direct 3Ds


A step-by-step description of   Direct  flow with 3Ds:

  1. The  checks out.
  2. The  submits a  to  .
  3. The  registers  data.
  4. The  sends a response in the form of a card data form to  .
  5. The  enters card data.
  6. The  sends card data  to  .
  7. The  sends an application using  Registration  to .
  8.  stores orders.
  9.  sends a response to the .
  10. The  submits payments using   to .
  11.  requests 3Ds with  .
  12. The  verifies  application.
  13. The  sends a 3Ds URL response to .
  14.  sends an authentication  to  .
  15. The  sends OTP to .
  16. The  sends  entered OTP to  .
  17. The  performs OTP validation.
  18. The  sends  3Ds results to .
  19.  does  FDS calculation.
  20.  submits a /charge to  .
  21. The  performs   .
  22. The  sends a  response to .
  23.  sends  notifications using callBackUrl and dbProcessUrl to Merchants.
  24. The  receives notifications.
  25. The  submits a  check to .
  26.  sends a  check response to the .
  27. The  receives  final status.
  28. The  sends  results of  order to  .



Redirect 3Ds



This  flow is only found in Checkout products.

In  3Ds Redirect ,   will continue   registration  on  display  provided by  after going through  FDS calculation  and checking OTP authentication. Redirects will be very useful when Merchants don't need to develop their own website appearance, because  has provided special  facilities to make it easier for Merchants. The 3Ds Redirect  uses  Checkout API.

CC Payment Flow - Redirect 3Ds
CC Payment Flow - Redirect 3Ds


A step-by-step description of  Redirect   flow with 3Ds:

  1. The  checks out.
  2. The  sends checkout data to the .
  3. The  submits a checkout using  Registration to .
  4.  registers checkout data.
  5.  transfers payments to 's  to  .
  6. The  sends     to  .
  7. The  selects a  .
  8. The  enters card data.
  9. The  sends card data  to .
  10.  processes FDS calculations.
  11.  requests 3Ds with  .
  12. The  performs 3Ds validation.
  13. The  sends a 3Ds URL response to .
  14.  receives a verification response.
  15.  redirects   to  ACS authentication .
  16. The  makes an OTP response.
  17. The  sends OTP to  .
  18. The  receives an OTP.
  19. The  enters OTP.
  20. The  sends  OTP to  .
  21. The  verifies  OTP.
  22. The  sends  3Ds results to .
  23.  received  inspection results.
  24.  submits  to  .
  25. The  performs   .
  26. The  sends  notifications to .
  27.  redirects callbackUrl to .
  28. The  displays  callbackUrl results to  .
  29.  sends  notifications to  .
  30. The  receives notifications.
  31. The  submits an inquiry to .
  32.  accepts applications.
  33.  automatically sends a response inquiry to  .
  34. The  receives  final status.
  35. The  sends   result  to  .



Direct Non 3Ds



In  Non-3Ds Direct ,   will continue   registration  on  's  display after carrying out  FDS (Fraud Detection System) calculation  without using an OTP. The difference within  redirect  is on   used. The Redirect  uses 's  view after proceeding  FDS (Fraud Detection System) calculation .

Payment Flow CC - Direct non 3Ds
Payment Flow CC - Direct non 3Ds


A step-by-step description of  Direct   flow with Non-3Ds:

  1. The  checks out.
  2. The  submits a  to  .
  3. The  submits  to .
  4.  register checkout data.
  5.  sends a response containing a card data form to  .
  6. The  enters card data.
  7. The  will send card data  to  .
  8. The  will send an application using  Register  to .
  9.  stores orders.
  10.  sends a response to  .
  11. The  submits payments using   to .
  12.  processes FDS calculations.
  13.  requests a charge to  .
  14. The  verifies  application.
  15. The  submits  confirmation.
  16. The  submits .
  17. The  performs   .
  18. The  sends  to .
  19.  sends callBackUrl and dbProcessUrl  notifications to Merchants.
  20. The  receives a .
  21. The  submits   to .
  22.  sends  check results.
  23. The  receives  final .
  24. The chant sends  results of  order to  .



Redirect Non-3Ds



This  flow is only found in Checkout products.

In  non 3Ds redirect ,   will continue   registration  on   view provided by  after carrying out  FDS (Fraud Detection System) calculation  without using an OTP. Redirects will be very useful when Merchants don't need to develop their own website appearance, because  has provided special  facilities to make it easier for Merchants.

CC Payment Flow - Redirect non 3Ds
CC Payment Flow - Redirect non 3Ds


Description of Redirect   flow steps with Non 3Ds:

  1. The  checks out.
  2. The  submits a  to  .
  3. The  registers  data.
  4. The  sends a response in  form of a card data form.
  5. The  submits a  to  .
  6. The  registers orders using  Registration  with .
  7.  saves order registration.
  8. } redirects  to   .
  9. The  sends    to  .
  10. The  selects a .
  11. The  enters card details.
  12. The  submits payments using   to .
  13.  does  FDS calculation.
  14.  submits  to  .
  15. The  verifies  application.
  16. The  sends a  confirmation application to  .
  17. The  submits a /charge to  .
  18. The  performs   .
  19. The  sends a  response to .
  20.  sends  notifications using callBackUrl and dbProcessUrl to Merchants.
  21. The  receives notifications.
  22. The  submits a  check to .
  23.  sends a  check response.
  24. The  receives  final .
  25. The  sends  results of  order to  .



See also

  Credit Card Feature  to find out   feature on  .

  Credit Card Integration & Testing  to find out how to perform  and  of    .

  Credit Card Glossary  to find out  particular term used on .

  Credit Card FAQ  if you want to find out frequently asked questions related to .



Updated 28 Aug 2024
Did this page help you?
PREVIOUS
Credit Card
NEXT
Credit Card Feature
Docs powered by Archbee