Glossary
Hosted checkout
A hosted checkout is a payment page that the payment platform serves, by a redirect or a link, instead of a page the merchant builds: the payer enters the card or chooses a local method there, and the card data goes straight to the platform's vault. The merchant integrates a link and a webhook and stays in the lightest PCI DSS scope; the brand on the page can still be the merchant's or the PSP's.
Hosted, embedded, own page
A hosted page by redirect keeps the merchant’s systems entirely away from card data. Embedded fields on the merchant’s page, served from the platform in frames, keep the number away too but put the merchant’s page in a longer questionnaire. The merchant’s own page with a server-to-server API puts the merchant in full scope. Most merchants of a PSP want the first; the API exists for the few that need the third.
What a good hosted page does
Loads fast on a mobile connection, speaks the payer’s language, shows only the methods that will work for this payment, runs 3-D Secure and the local methods’ flows on one page, returns the payer to the merchant with the result, and meets the payment-page requirements of PCI DSS version 4 so the merchant never has to.
On the platform
Tranzify’s hosted checkout is served under each network’s domain in 29 languages, shows the methods the routing allows, runs cards with 3-D Secure, wallets, Open Banking, QR and transfer methods, carries the brand of the network and ships with the headers, integrity checks and self-check the standard asks for.
Updated: 2026-11-08