HyperPay

HyperPay's gateway includes tokenization, pre-authorization and recurring payments. Tokenization replaces stored card details with a reference that the merchant can use for a later authorized charge. Its recurring-billing outline follows that pattern: a customer subscribes, HyperPay creates the token, and the merchant uses it when payment is due.

For website checkout, COPYandPAY provides a payment form while a server-to-server API allows a more customized flow. The widget integration has three parts: prepare a checkout on the server with its amount and currency, display the form using the returned identifier, then retrieve the result after payment. The integration guide tells developers to compare the returned amount, currency and other identifiers with the expected order.

A checkout identifier expires after a successful payment or after 30 minutes. The payment-status endpoint also limits checks to two requests per checkout per minute. These details matter when handling a customer who reloads the form or returns after a delay.

Getting live involves a merchant agreement and an application through HyperPay's banking partner, followed by integration and account onboarding. Prices depend on the business's registration country and are supplied by its business-development team. HyperPay says settlement terms are agreed in writing during onboarding rather than using one timetable for every business.

The site names several regional markets, but the payment methods and settlement currency still depend on the local arrangement. A business collecting subscriptions should confirm that its chosen card and local payment methods support the intended repeat-charge flow.