Difference between revisions of "RecurrenceType"

From Barion Documentation
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
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 payment is initiated by the merchant, the customer is not present for the purchase.  
+
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.  
  
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>
+
For subsequent payments '''no 3DS''' authentication (challenge) is required. This type of transaction is out of scope of the <abbr title="Strong Customer Authentication">SCA</abbr> framework.
  
 
'''The liability in case of fraud is on the merchant.'''
 
'''The liability in case of fraud is on the merchant.'''
Line 31: Line 31:
 
'''Merchant-initiated transactions (MITs) with fixed value: '''
 
'''Merchant-initiated transactions (MITs) with fixed value: '''
  
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 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'''.
  
In this case '''no 3DS''' authentication is required on the merchant's site. This type of transaction can be exempted from the <abbr title="Strong Customer Authentication">SCA</abbr>.
+
For subsequent payments '''no 3DS''' authentication (challenge) is required. This type of transaction can be exempted from the <abbr title="Strong Customer Authentication">SCA</abbr> framework.
  
 
'''The liability in case of fraud is on the card issuer.'''
 
'''The liability in case of fraud is on the card issuer.'''
 
|}
 
|}

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.