RecurrenceType: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 14: Line 14:
| OneClickPayment || 10 ||  
| OneClickPayment || 10 ||  
The purchase is initiated by the customer on the merchant's website, but instead of redirecting the customer to the Barion Smart Gateway the recurrence Id is used for a more convenient payment flow.
The purchase is initiated by the customer on the merchant's website, 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 '''no 3DS''' challenge will be presented for the customer. This type of transaction is not part of the <abbr title="Strong Customer Authentication">SCA</abbr>


|-
|-
| MerchantInitiatedPayment || 0 ||  
| MerchantInitiatedPayment || 0 ||  
The payment is initiated by the merchant, the customer is not present for the purchase.  
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. This type of transaction is not part of the <abbr title="Strong Customer Authentication">SCA</abbr>
The liability in case of fraud is on the merchant.
The liability in case of fraud is on the merchant.



Revision as of 14:34, 6 November 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
OneClickPayment 10

The purchase is initiated by the customer on the merchant's website, 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 no 3DS challenge will be presented for the customer. This type of transaction is not part of the SCA

MerchantInitiatedPayment 0

The payment is initiated by the merchant, the customer is not present for the purchase. The liability in case of fraud is on the merchant.

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 can be exempted from the SCA. The liability in case of fraud is on the card issuer.