Difference between revisions of "RecurrenceType"

From Barion Documentation
Jump to navigation Jump to search
 
Line 20: Line 20:
 
|-
 
|-
 
| MerchantInitiatedPayment || 0 ||  
 
| MerchantInitiatedPayment || 0 ||  
''''Merchant-initiated transactions (MITs) with non-fixed value:'''
+
'''Merchant-initiated transactions (MITs) with non-fixed value:'''
 
   
 
   
 
The customer authorizes the merchant to charge her in the future. Subsequent payments are initiated by the merchant and the customer is not present for these purchases.  
 
The customer authorizes the merchant to charge her in the future. Subsequent payments are initiated by the merchant and the customer is not present for these purchases.  

Latest revision as of 12:59, 23 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

Consumer-initiated transactions (CITs):

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 3DS authentication is required on the merchant's site.

MerchantInitiatedPayment 0

Merchant-initiated transactions (MITs) with non-fixed value:

The customer authorizes the merchant to charge her in the future. Subsequent payments are initiated by the merchant and the customer is not present for these purchases.

For subsequent payments no 3DS authentication (challenge) is required. This type of transaction is out of scope of the SCA framework.

The liability in case of fraud is on the merchant.

RecurringPayment 20

Merchant-initiated transactions (MITs) with fixed value:

The customer authorizes the merchant to charge for the services/products periodically, typically in case of subscriptions. Subsequent payments are initiated by the merchant and the customer is not present during these payment. Subsequent charges can only be the same or lower as the initial amount.

For subsequent payments no 3DS authentication (challenge) is required. This type of transaction can be exempted from the SCA framework.

The liability in case of fraud is on the card issuer.