A merchant using the Recurring Payment function is integrated using WS API (the processRecurringPayment method).
The requirements of the PSD2 RTS and card schemes impact this merchant, who needs to make changes in the current integration using a WS API according to the relevant scenario for subscriptions (recurring payments) based on their previous agreements with the customer:
Usage-based Subscription:
A customer agrees with the merchant on a “direct debit from a payment card” (similar to a direct debit from a bank account), for example regular payments for billing from a mobile telephone network operator (variable amount/fixed date).
In this case, the merchant will implement the new processUsageBasedSubscriptionPayment method (see the up-to-date version of the “GP webpay API WS – Technical Specification” document).
The acquirer authorises the Usage-Based Subscription for the merchant; this payment does not transfer the liability for chargebacks to the issuer, and the acquirer is liable for potential losses, and may transfer this obligation to the merchant.
Regular subscription:
A customer agrees with the merchant on a regular subscription, e.g. a subscription to digital services (fixed amount/fixed date).
In this case, the merchant will implement the new processRegularSubscriptionPayment method (see the up-to-date version of the “GP webpay API WS – Technical Specification” document).
The acquirer authorises a Regular Subscription for the merchant; this payment does not transfer the liability for chargebacks to the issuer, and the acquirer is liable for potential losses, and may transfer this obligation to the merchant.
Prepaid subscription:
A customer agrees with the merchant on recharging a prepaid service, e.g. a payment to recharge a prepaid card of a mobile telephone network operator with a fixed amount initiated by the stored value dropping below a defined level (fixed amount/variable date).
In this case, the merchant will implement the new processPrepaidPayment method (see up-to-date version of the “GP webpay API WS – Technical Specification” document).
The acquirer authorises the Prepaid Subscription for the merchant; this payment does not transfer the liability for chargebacks to the issuer, and the acquirer is liable for potential losses, and may transfer this obligation to the merchant.
Please send your inquiries or requirements for implementation support to the email address gpwebpay@gpe.cz.