A payment portal for your website — hosted, PCI-scoped, one link away.
BazPay hosts the portal; you link to it from your website, invoices, emails or QR codes. Cards, wallets and local payment methods run through the same page, and a signed webhook confirms every successful payment straight to your systems.
Built for merchants across the EU, UK, Australia, Canada and New Zealand — professional services, membership sites, course platforms, digital publishers and small e-commerce. No checkout code on your website, merchant SAQ A scope, and direct regional acquiring under the hood.
Why a hosted payment portal beats a home-built checkout
A home-built checkout on a small website is a maintenance load out of proportion to the volume it collects. Four properties make a hosted portal the pragmatic default.
-
No checkout code on your website
The portal is served from BazPay — you link to it from a button, an email or an invoice PDF. Your website never touches raw card data, so your annual PCI return stays at merchant SAQ A.
-
One link, every payment method
The same portal page offers cards, Apple Pay, Google Pay and local payment methods. Shoppers pick the method they already use; you do not build one flow per rail.
-
Custom amount or fixed price
Portals can present a set amount for an invoice or renewal, or let the payer enter their own — the difference is a dashboard flag. Metadata you set at creation rides through to the settled charge.
-
Confirmation you can trust
A signed webhook lands on your endpoint the moment the payment succeeds. Wire it into your invoicing, CRM or membership tool and mark the record paid without a manual reconcile step.
Four portal patterns the same platform ships
The portal is one product with four common configurations. Every one uses the same underlying charge object and confirmation webhook — pick the pattern that matches how you invoice or renew.
-
Invoicing
Invoice-pay portal (fixed amount)
Attach an amount, an invoice reference and a description at creation. Send the link on the invoice; the portal renders the amount, collects the payment and fires a signed webhook keyed to your invoice reference on success.
- Fixed amount
- Invoice reference
- Descriptor
-
Request-to-pay
One-off payment requests
A support agent or finance team member creates a one-off portal from the dashboard, sends the link and marks the debtor paid the moment the webhook lands.
- Dashboard-created
- Ad-hoc
- Time-limited
-
Renewals
Membership renewal portal
A portal that renews a membership on the shopper's saved card or takes a new card for the next term. Card-on-file support means returning members clear a single click, first-time renewals collect card details on the portal itself.
- Card-on-file
- First-time card capture
-
Custom amount
Donation or top-up portal
Let the payer enter the amount inside a minimum and a maximum you configure. Useful for membership top-ups, professional services retainers and any pay-what-you-choose flow.
- Min/max range
- Payer-chosen amount
Prefer to render checkout inside your own page instead? See hosted checkout products. Wire payments inside a product admin instead of on a marketing site? See integrated payment solutions.
From portal creation to confirmed payment
Six stages from creating the portal to reconciling the settled dollar. Each stage is visible in the dashboard and each stage change fires a signed webhook.
-
Create
Create a portal from the dashboard or with one API call. Attach the amount (or amount range), your reference and metadata.
-
Share
Send the returned HTTPS link on an invoice, in an email, on a landing page or as a QR code on printed collateral.
-
Shopper opens
The portal renders on mobile and desktop, offering the payment methods you enabled. Card details are collected in our PCI environment.
-
Authenticate
3-D Secure 2.2 runs only when the risk earns it — PSD2 exemption logic keeps most portal checkouts frictionless.
-
Confirm
The portal shows the shopper a success screen. A signed webhook fires to your endpoint keyed to the reference you set at creation.
-
Reconcile
Settlement lands per scheme cycle. Refunds fire from the dashboard or via API — the same charge object powers the whole flow.
Hosted portal vs building your own checkout
Building a card-accepting form inside your own website works, but it comes with PCI responsibility, a maintenance load and a set of edge cases most small teams do not want to own. The comparison below shows where each approach earns its keep.
| Dimension | BazPay hosted portal | Home-built checkout |
|---|---|---|
| Your PCI scope | Merchant SAQ A — no PAN on your site | Full PCI where your form posts PAN |
| Time to launch | Minutes — create link, share link | Weeks of front-end work |
| Method coverage | Cards, wallets, local APMs on one page | One integration per rail |
| Mobile parity | Portal renders responsively by default | You build the responsive layout |
| 3-D Secure 2 | Handled by the portal, PSD2-compliant | You implement the challenge flow |
| Change safety | Portal updated by BazPay across merchants | You maintain and re-test on every change |
Rate structure on the pricing page. Boarding path on merchant acquiring. Ongoing service envelope on payment gateway services.
Features you configure on every portal
Every capability below ships on the standard integration. Turn features on with a dashboard toggle when you create the portal — no premium tier gates the primitives.
-
Fixed or open amount
Present a set amount for an invoice, or let the payer enter their own inside a min/max range you configure at creation.
-
Metadata on creation
Attach an invoice reference, a customer ID or any custom tag; the metadata rides through to settlement, refund and dispute events.
-
Cards, wallets and APMs
The portal accepts Visa, Mastercard, Apple Pay, Google Pay and local payment methods on one page — no extra config per rail.
-
3-D Secure 2.2 by default
Authentication with automatic exemption logic. Frictionless flow first; challenge only when the risk or the issuer requires it.
-
Signed webhooks
HMAC-signed, replay-protected success and refund events land on your endpoint. Retry schedule up to 72 hours if your endpoint is unreachable.
-
Receipts and success screen
Shoppers see a clear success page and receive an email receipt. Your logo, colour and copy override the defaults.
-
Card-on-file for renewals
Portals for known payers reuse the stored network token; a card reissue does not force the shopper to re-enter details.
-
Refunds by API or dashboard
Full or partial refunds on any portal-collected charge. Refund events fire on the same signed webhook stream.
Create a portal in one API call
Post an amount, a currency and any metadata; get back a signed HTTPS URL you can share. The portal renders responsively, collects payment through hosted fields inside our PCI environment and confirms success through a signed webhook keyed to your reference.
POST /v1/payment_links
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"description": "Invoice INV-10842",
"metadata": { "invoice_id": "INV-10842", "customer": "cus_5F9k" },
"payment_methods": ["card", "apple_pay", "ideal"],
"success_url": "https://example.com/thanks"
}The response returns the portal URL and a portal_id you can reuse to query state. Complete schema in the API reference; handler samples in the developer docs.
Where merchants add a payment portal to their website
Four merchant profiles below already run BazPay-hosted portals in production. Each configuration differs in whether the amount is fixed, whether renewal is involved and which methods are enabled.
-
Professional services invoicing
Agencies, consultancies and B2B firms sending invoices with a pay-now link. The signed webhook marks the invoice paid inside the ledger without a manual step.
-
Membership sites
Renewal pages that reuse a stored card for returning members or capture a new one for first-time renewals — with dunning-aware retries on soft declines.
-
Course and event tickets
Fixed-amount portals for a course, an event or an add-on; each portal carries the SKU as metadata for reconciliation per session.
-
Ad-hoc collection
Finance and support teams sending one-off request-to-pay links from the dashboard for late invoices, deposit collection or refund top-ups.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record and does not act as a marketplace of third-party PSPs.
Security and compliance signals on every portal
The portal runs inside a PCI DSS Level 1 environment assessed each year. Because raw PAN never touches your website, your annual return stays at merchant SAQ A. Authentication runs on every portal card charge with 3-D Secure 2.2 and automatic exemption logic.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment that hosts the portal
- Merchant SAQ A
- No PAN on your site — your annual return stays at the smallest merchant scope
- Authentication
- 3-D Secure 2.2 with automatic exemption logic on every portal card charge
- GDPR
- In-region data residency; DPA on request
- Portal HTTPS
- Portal URLs served over HTTPS with modern TLS, HSTS preload eligible
Questions merchants ask about the payment portal
What exactly is a payment portal for a website?
A payment portal for a website is a hosted page — served from BazPay, not from your servers — that collects a payment on your merchant's behalf. You link to it from your site, an email, an invoice PDF or a QR code. The customer opens the link, chooses a method, pays, and a signed webhook confirms the payment to your systems. Your website never handles card data.
How do I create a payment portal without writing checkout code?
The dashboard has a portal builder that creates a link from a short form — amount, description, reference and enabled methods. Save it, copy the HTTPS link, paste it wherever you need. Engineering teams that want automation create the same portals via one API call.
Can I use a custom domain or brand the portal to match my website?
Yes. The portal supports your logo, brand colour and success-message copy inside the dashboard, and can be served under a subdomain of your website via a documented CNAME setup. The URL your customers see reads as part of your brand while the acceptance environment stays under BazPay's PCI scope.
Does the payment portal for my website work on mobile?
Yes. The portal renders responsively on phones, tablets and desktop, and shows Apple Pay or Google Pay when the shopper's device supports them. The same URL works on any browser — there is no separate mobile page to build or maintain.
Can the portal handle subscription renewals, or is it one-off only?
Both. A standard portal collects a single payment. A renewal portal reuses a stored network token for returning members and takes a new card for first-time renewals. For full subscription lifecycle management with dunning and MIT exemptions, see the recurring-billing product; the portal is the pay page in front of it.
How are refunds handled on a portal-collected payment?
Refunds are issued from the dashboard on the charge record or via API. Full or partial refunds are supported; the refund event fires on the same signed-webhook stream as the original charge, keyed to the reference you set at portal creation. Refunded funds settle in the next scheme cycle.
Which merchant types can add this payment portal to their website?
Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses, digital publishers, membership sites and course platforms. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not support marketplace-style aggregation for third-party sellers.
How does the portal compare to embedding hosted fields directly on my site?
Hosted fields give you a checkout inside your own page, with more control over the surrounding UX. A hosted portal is faster to launch, requires no front-end code and works for links inside emails or PDFs where you cannot host a form. Both surfaces keep your PCI scope at SAQ A; the choice depends on where the shopper needs to pay from.
Add a payment portal to your website today
Share your business model and typical ticket size. A payments specialist will confirm boarding fit and walk you through creating the first portal inside one working day. See also real-time analytics, payment fraud prevention and payment gateway services.