To provide a quick and convenient buying process for the customer, one-click card payments can be used. The customer is present and is offered to store card details (tokenization) without the need to re-enter it each time for future payments, improving the checkout experience. However, as Strong Customer Authentication (SCA) requirement applies to all customer-initiated online payments within Europe, the 3DS authentication might be required during the payment process, depending on the customer’s card issuer’s decision. Merchants must obtain customer consent for initial storage of the payment credentials and establish an agreement with the customer for ongoing/future payments.

Tokenization is possible only when a customer can log in to the merchant’s system/e-shop using authentication.

To initiate the CIT payment first the merchant needs to get card token for the initial payment.

How to initiate CIT payment

  1. to initiate CIT payment, make POST /payments/cit request
  2. to complete the payment, make POST /payments/charge request by adding “payment_reference” (returned in step 1 (POST /payments/cit)) and token (returned with the initial tokenization payment, use  (GET /payments/{payment_reference})) parameters
  3. in the response, initiated payment data will be returned containing the “payment_link” to which the customer should be redirected
  4. customer continues with 3DS authentication (depends on the card issuer, this step might be skipped)
  5. when payment is processed, Payment Gateway sends a Callback notification to merchant specified Callback URL containing “payment_reference” parameter indicating that the status of the payment has changed
  6. to check the payment status, make GET /payments/{payment_reference} request
  7. customer is redirected back to the merchant showing the outcome of the payment
in Integration
Did this article answer your question?