A hosted payment page is a checkout page that your payment provider runs on its own servers. When a customer clicks a pay button on your website or invoice, they land on that page, enter their details there and return to you once they have paid. Because the details never touch your systems, it is usually the simplest, lowest-risk way for a small business to take payments online.
A hosted payment page is a payment form served entirely by a payment processor or gateway, to which a merchant sends customers by link or redirect to complete a purchase. The merchant sets the amount and the branding, while the provider collects and processes the payment details.
How a hosted checkout works
From the customer's side it looks like a single checkout. Underneath, there is a handoff:
- The customer clicks "Pay" on your website or in an emailed invoice.
- Your system tells the payment provider the amount and a reference, and the customer is redirected to the provider's page.
- The page shows your logo and business name alongside the amount. The customer enters their details and submits.
- The provider runs the payment and shows a confirmation, or, where the provider supports it, sends the customer back to a page you choose.
- The provider notifies your system that the payment succeeded, usually by a webhook (an automatic message from one system to another), so the invoice or order is marked paid.
The address bar changes during step 3, which is the visible sign that the customer is on the provider's page rather than yours. Branding can make much of the rest feel like your own checkout.
Hosted page, embedded fields or your own form
There are three common ways to collect card details online, and they differ mainly in where the card number is typed and whose code serves the form.
| Hosted payment page | Embedded fields (iframe) | Your own form via API | |
|---|---|---|---|
| Where the customer types the card number | On the provider's page | In provider-served fields placed inside your page | On your page, in your form |
| Does the customer leave your site? | Yes, briefly | No | No |
| Design control | Logo and colors, within the provider's layout | Most of the page; the fields follow provider styling options | Complete |
| Development work | Little or none | Moderate | Significant |
| Your PCI DSS burden | Smallest | Small, but your page must be protected against malicious scripts | Largest, because card data passes through your systems |
A hosted page is also the natural partner for pay by link: the link simply opens the hosted page with the amount already set. If you are unsure which part of the payment chain does what, the difference between a gateway and a processor is set out in payment gateway vs payment processor.
Why a hosted page shrinks your PCI scope
Any business that accepts cards is expected to follow the Payment Card Industry Data Security Standard (PCI DSS), maintained by the PCI Security Standards Council. Smaller merchants usually show compliance by completing a self-assessment questionnaire (SAQ), and which questionnaire applies depends on how card data reaches the merchant's systems. The fewer systems that touch card data, the shorter the questionnaire.
The shortest is SAQ A. In the version published for PCI DSS v4.0 (April 2022), the PCI Security Standards Council describes SAQ A as covering merchants whose account data functions are completely outsourced to PCI DSS compliant third parties. To use it, a card-not-present merchant confirms, among other things, that:
- all processing of account data is outsourced to a PCI DSS compliant service provider;
- it does not electronically store, process or transmit any account data on its own systems or premises;
- any account data it keeps is on paper only, such as printed reports or receipts; and
- for e-commerce, every element of the payment page delivered to the customer's browser comes only and directly from the compliant provider.
A hosted page is built to meet that last condition. Two cautions apply. First, the same document notes that some requirements still cover the web server that hosts the redirect to the payment page, because that server affects where customers' card data is sent, so your website still needs securing. Second, the SAQ A revision for PCI DSS v4.0.1, effective 1 April 2025, added a criterion: the merchant confirms its site is not susceptible to attacks from scripts. In a February 2025 FAQ explainer, the Council said this criterion applies only to merchants whose pages embed a provider's payment form, and not to merchants that redirect customers to the provider or send them an emailed link to the provider's payment page. The Council also tells merchants to confirm with their acquirer (the bank or processor that handles their card payments) which questionnaire applies, and that is the step to take before relying on any of this. Check the current SAQ version in the Council's document library too, since the standard is revised from time to time.
Pros and cons of a hosted payment page
What you gain
- Card data stays off your website and computers, which keeps your PCI obligations as small as they can be.
- Little or no development: most providers configure the page through settings.
- One page serves every entry point, from a website button to a payment link.
- New payment methods the provider adds, such as wallets, can appear on the page without changes on your side.
What you give up
- Full design control. You work within the provider's layout.
- Your own domain in the address bar. During payment it usually shows the provider's, which a few customers will notice.
- Some flexibility over custom fields and multi-step checkouts.
- Independence: if the provider's page is down, so is your checkout.
For most service and B2B businesses, whose customers pay invoices and deposits rather than filling shopping carts, the gains outweigh the losses comfortably.
A worked example
Say a trade association collects annual dues of $350 from 1,200 members (the figures are hypothetical). That is $420,000 in card and bank payments in a single renewal season. With a renewal email that links to a hosted page, none of those card numbers touches the association's website or staff inboxes. Its web developer adds a "Renew now" button and sets up a confirmation page, and the payment provider does the rest. Building its own card form instead would bring the association's website, and whoever maintains it, into scope for far more of the standard.
Branding a page you don't host
Most of the trust a customer feels on a hosted page comes from recognizing the business. Configure these before you send anyone to it:
- Your logo and colors, so the page looks like a continuation of your site or invoice.
- Your business name exactly as customers know it, and matching the name that will appear on their card statement.
- A clear description of what is being paid, such as the invoice number or service.
- Return and cancel pages on your own site, if your provider supports them, so the customer ends up back with you either way.
- A receipt email that carries your name and contact details.
Among the tools PayLink can set up for a client is a hosted payment page: a secure, branded page customers can pay from at any time. The developer documentation for it also describes a "Pay Now" button for sites built on common website platforms, WordPress and Shopify among them. The platform page has the detail, and payment links open the same page.
Setting one up
- List every place a customer will start a payment, from your website to printed QR codes.
- Configure branding and the payment methods you want to offer.
- Set confirmation and cancel addresses on your website, where the provider allows it.
- Turn on payment notifications, by webhook or email, so paid invoices update without anyone checking manually.
- Run test payments in the provider's sandbox or test mode, including a declined card, before going live.
- Ask your acquirer to confirm which PCI questionnaire applies to your setup.
Frequently asked questions
Is a hosted payment page the same as a payment link?
Not quite. The hosted page is the checkout itself; a payment link is one way of sending a customer to it. A website button or a QR code can open the same hosted page. The link usually carries the amount and a reference, so the page arrives filled in for that customer.
Will customers trust being sent to another website to pay?
Most will, since paying on a provider's page is a familiar step for people who shop online. Trust drops when the page looks unrelated to the business that sent the customer there. Consistent branding and a description that matches the invoice do most of the work. Mentioning on your invoice that payment is handled by your processor also helps.
Can a hosted payment page take recurring payments?
Often, yes. Many providers let the first payment on a hosted page store the customer's payment method, with their consent, so that later charges run automatically on a schedule. The card details stay with the provider. If you plan to bill this way, read how recurring billing works and what authorization you need before you store anything.
Sources
- PCI Security Standards Council: Self-Assessment Questionnaire A and Attestation of Compliance, for use with PCI DSS Version 4.0 (PDF, April 2022), accessed 15 November 2026
- PCI Security Standards Council: FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants (28 February 2025), accessed 15 November 2026