RecurrenceType: Difference between revisions
m (→Enum list) |
Stankovicsa (talk | contribs) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 16: | Line 16: | ||
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. | ||
<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> More info: [[Token_payment_3D_Secure#Off-site 3DS v2 authentication|off-site 3DS v2 authentication]] | |||
|- | |- | ||
| MerchantInitiatedPayment || 0 || | | MerchantInitiatedPayment || 0 || | ||
'''Merchant-initiated transactions (MITs) with non-fixed value:''' | |||
The | 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 <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 32: | ||
'''Merchant-initiated transactions (MITs) with fixed value: ''' | '''Merchant-initiated transactions (MITs) with fixed value: ''' | ||
The | 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 <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.''' | ||
In case of this type the RecurringExpiry and RecurringFrequency subfields are mandatory in the PurchaseInformation field. More info: [[PurchaseInformation]] | |||
|} | |} | ||
Latest revision as of 09:35, 1 December 2021
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. More info: off-site 3DS v2 authentication |
| 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. In case of this type the RecurringExpiry and RecurringFrequency subfields are mandatory in the PurchaseInformation field. More info: PurchaseInformation |