RecurrenceType: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
Line 25: Line 25:
The purchase is initiated by the merchant and '''the customer is not present''' during the payment. The customer previously authorized the merchant to charge for the services periodically the '''same amount'''.
The purchase is initiated by the merchant and '''the customer is not present''' during the payment. The customer previously authorized the merchant to charge for the services periodically the '''same amount'''.


In this case '''no 3DS''' authentication is required on the merchant's site.
In this case '''no 3DS''' authentication is required on the merchant's site. This type of transaction is exempted from the SCA (Strong Customer Authentication).
|}
|}

Revision as of 05:05, 14 July 2020

RecurrenceType enumeration

This enum indicates the type of recurrence that the payment represents.

API usage

This enum is used by the following API endpoints:

Enum list

Enum value Byte / int value Description
MerchantInitiatedPayment 0

The payment is initiated by the merchant, the customer is not present for the purchase.

In this case no 3DS challenge will be presented for the customer.

OneClickPayment 10

The purchase is initiated by the customer but instead of redirecting the customer to the Barion Smart Gateway the recurrence Id is used for a more convenient payment flow.

In this case 3DS authentication is required on the merchant's site.

RecurringPayment 20

The purchase is initiated by the merchant and the customer is not present during the payment. The customer previously authorized the merchant to charge for the services periodically the same amount.

In this case no 3DS authentication is required on the merchant's site. This type of transaction is exempted from the SCA (Strong Customer Authentication).