> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Pages

> Shareable checkout pages where anyone can pay you a fixed or open amount, with every payment recorded as a normal invoice

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

<Steps>
  <Step title="Open Payment pages">
    Go to **Commerce > Payment pages**.
  </Step>

  <Step title="Create the page">
    Give it a title, a slug (the last part of the URL), and a currency.
  </Step>

  <Step title="Work through the editor">
    The editor's left sidebar walks through the page in sections: **Basics**, **Fields & invoice**, **After payment**, **Webhook**, **Footer & legal**, and **Advanced**.
  </Step>
</Steps>

## Choose how the amount works

<CardGroup cols={2}>
  <Card title="Fixed amount" icon="lock">
    Every payer pays the same amount.
  </Card>

  <Card title="Preset buttons" icon="list">
    Offer a set of amounts for the payer to pick from.
  </Card>

  <Card title="Open amount" icon="pen">
    The payer enters their own amount. You can set a minimum and a maximum.
  </Card>
</CardGroup>

## 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.

<Info>
  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.
</Info>

## After payment

Choose what the payer sees once the charge succeeds:

<CardGroup cols={2}>
  <Card title="Thank-you page" icon="circle-check">
    Customize the heading and message shown after payment.
  </Card>

  <Card title="Redirect" icon="arrow-right">
    Send the payer to a URL on your own site instead.
  </Card>
</CardGroup>

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.

## Share the link

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](/how-tos/portal-custom-domain).

## 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?

<CardGroup cols={2}>
  <Card title="Payments" icon="credit-card" href="/commerce/payments">
    Connect a processor so payment pages can charge cards.
  </Card>

  <Card title="Use Your Own Domain for Billing" icon="globe" href="/how-tos/portal-custom-domain">
    Serve payment pages from billing.youragency.com.
  </Card>

  <Card title="Client Portal" icon="user" href="/commerce/client-portal">
    Where clients sign in to see and pay their billing.
  </Card>

  <Card title="Invoices" icon="file-invoice-dollar" href="/commerce/invoices">
    The records every payment-page payment creates.
  </Card>
</CardGroup>