A merchant using the One-click Payment function is integrated using a WS API (the ProcessRecurringPayment or processTokenPayment 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 one-click payments scenario the merchant offers to their customers in their e-shop or application:
One-click Payment:
A customer clicks the “Pay” button in the e-shop or in the merchant’s application and is then redirected to their issuer for strong customer authentication.
In this case, the merchant will implement the new processCardOnFilePayment method (see the up-to-date version of the “GP webpay API WS – Technical Specification”) document) and also an HTTP API (in the same scope as merchant using the 3D Secure card payment) to redirect the customer to their issuer for strong customer authentication.
The acquirer authorises the One-Click Payment function for the merchant.
If strong customer authentication takes place, the liability for chargebacks is transferred to the issuer, who is liable for potential losses.
Providing that, based on a previous agreement between the acquirer and the merchant, the TRA exemption from strong customer authentication is applied by the acquirer with whom the merchant has concluded an agreement on payment cards acceptance on the Internet, the liability for chargebacks is not transferred to the issuer, and the acquirer is liable for potential losses, and may transfer this obligation to the merchant.
Providing that the TRA exemption from strong customer authentication is applied by the issuer, the liability for chargebacks is transferred to the issuer, who is liable for potential losses.
Usage-based Payment:
A customer clicks the “Pay” button in the e-shop or in the merchant’s application but the payment is initiated by the merchant and processed via the GP webpay WS API later without redirecting the customer to the GP webpay payment gate – for example, payments initiated by a transport service application.
In this case, the merchant will implement the new processUsageBasedPayment method (see the up-to-date version of the “GP webpay API WS – Technical Specification”) document). The acquirer authorises the Usage-Based Payment function for the merchant; with this type of payment, the liability for chargebacks does not transfer 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.