Skip to main content
Payment pages are shareable “pay us any amount” checkout pages. You create a page once, share the link, and anyone can pay you: a deposit, a retainer top-up, a one-off fee, no invoice to draft first. Each page lives at /pay-to/your-slug on your own domain when one is connected, and every payment lands in Commerce as a normal invoice and payment record.

​
Create a payment page

1

Open Payment pages

Go to Commerce > Payment pages.
2

Create the page

Give it a title, a slug (the last part of the URL), and a currency.
3

Work through the editor

The editor’s left sidebar walks through the page in sections: Basics, Fields & invoice, After payment, Webhook, Footer, and Advanced.

​
Choose how the amount works

Fixed amount

Every payer pays the same amount.

Preset buttons

Offer a set of amounts for the payer to pick from.

Open amount

The payer enters their own amount. You can set a minimum and a maximum.

​
Payer fields

Collect what you need and nothing more. Name, company, phone, and memo fields are available; each has a required toggle, and you can reorder them.

​
Tax and exemptions

Set an optional tax rate on the page. If some of your payers are tax-exempt, turn on Allow tax-exemption claims: payers can mark themselves exempt and enter an exemption number.
An exempt payer is charged the same total; the difference is in the paperwork. Their invoice records zero tax along with the exemption number they provided.

​
After payment

Choose what the payer sees once the charge succeeds:

Thank-you page

Customize the heading and message shown after payment.

Redirect

Send the payer to a URL on your own site instead.
You can also customize the confirmation email the payer receives. It sends from your branded sender, and you can test-send it to yourself before going live. When the confirmation email is enabled, it replaces the default receipt.

​
CRM automations

Each payment can feed your CRM automatically: the payer’s company is created or linked for you, and you can optionally create a deal in a pipeline you choose.

​
Webhook

Notify your own systems about every successful payment:
  • Hiveku sends a POST to your https URL on each successful payment
  • Requests carry a bearer secret in the header, so your endpoint can verify they came from Hiveku
  • A Send test button and an example payload are shown right in the editor

​
Analytics

Every page tracks views, conversion rate, payments, and revenue. The numbers appear in the payment pages list and in the editor header, so you can see at a glance which pages earn their keep. The copy and open buttons use your own domain automatically: your custom billing domain when one is connected, or your free youragency.hiveku.io address otherwise — the page itself always lives at /pay-to/your-slug on that host. To put payment pages (and the client portal) on a subdomain like billing.youragency.com, see Use Your Own Domain for Billing.

​
Behind the scenes

Every payment made through a payment page creates a normal invoice and payment record, so your reporting, AR aging, and exports work unchanged. Card-testing protection and reCAPTCHA run automatically on every page; there is nothing to configure.

​
What’s next?

Payments

Connect a processor so payment pages can charge cards.

Use Your Own Domain for Billing

Serve payment pages from billing.youragency.com.

Client Portal

Where clients sign in to see and pay their billing.

Invoices

The records every payment-page payment creates.