Recurring Payment Scenarios

Recurring

Description

Recurring is merchant initiated transactions for automatic or systematically repeated payments, using previously saved customers' card data.

In order to use Recurring, at first, the card data has to be saved: learn more about it in the Payment Method Saving section. Card data can be saved either on the merchant's side or on the Cardaq side.

Two types of Recurring are supported:

  • Automatic (Merchant Initiated Transactions (MIT); unscheduled): off-session payments for which the cardholder does not participate and for which the merchant charges their customers irregularly and for different amounts. For example, taxi apps - the cardholder is charged for the final amount at the end of the ride, and the charging does not require cardholder’s confirmation;
  • Recurring (Merchant Initiated Transactions (MIT); scheduled): off-session payments for which the cardholder does not participate and for which the merchant charges their customers regularly for the same amount. For example, gym memberships - the cardholder is charged at the beginning or the end of the billing cycle and it is always done for the same amount.

Recurring is compatible with the following payment scenarios and additional capabilities:

  • One-Step Payment
  • Two-Step Payment
  • Full Refund
  • Partial Refund
  • Reversal
  • Use of Dynamic Descriptor
  • Use of Service Location details
  • QCash
  • SDWO Funding Payment
  • SDWO Purchase Payment
  • Taxes

Recurring (Automatic) is compatible with all of the above and:

  • Use of Travel Data
  • All types of Payouts (A2A, B2P, P2P, OG, SDWO)

Request Example


One-Click

Description

One-Click (Cardholder Initiated Transactions (CIT)) payments are on-sessions payments where the cardholder participates. Example, food delivery apps where the cardholder creates a cart and approves the final amount for authorization at the end.

In order to use One-Click, at first, the card data has to be saved: learn more about it in the Payment Method Saving section. Card data can be saved either on the merchant's side or on the Cardaq side.

One-Click is compatible with the following payment scenarios and additional capabilities:

  • One-Step Payment
  • Two-Step Payment
  • Full Refund
  • Partial Refund
  • Reversal
  • Use of Travel Data
  • Use of Dynamic Descriptor
  • Use of Service Location details
  • QCash
  • SDWO Funding Payment
  • SDWO Purchase Payment
  • Taxes

Request Example


Jump to
  • Recurring
  • One-Click