RecurrenceType: Difference between revisions
mNo edit summary |
m (→Enum list) |
||
| Line 13: | Line 13: | ||
|- | |- | ||
| OneClickPayment || 10 || | | 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. | '''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. | |||
<span style="color:red">In this case <u>3DS authentication is required</u> on the merchant's site.</span> | <span style="color:red">In this case <u>3DS authentication is required</u> on the merchant's site.</span> | ||
|- | |- | ||
| MerchantInitiatedPayment || 0 || | | MerchantInitiatedPayment || 0 || | ||
Merchant-initiated transactions (MITs) with non-fixed value: The payment is initiated by the merchant, the customer is not present for the purchase. | ''''Merchant-initiated transactions (MITs) with non-fixed value:''' | ||
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> | 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.''' | ||
|- | |- | ||
| RecurringPayment || 20 || | | RecurringPayment || 20 || | ||
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'''. | '''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'''. | |||
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>. | 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>. | ||
The liability in case of fraud is on the card issuer. | '''The liability in case of fraud is on the card issuer.''' | ||
|} | |} | ||
Revision as of 08:40, 7 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 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 SCA The liability in case of fraud is on the merchant. |
| RecurringPayment | 20 |
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. 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. |