Skip to main content
Payment Forms let customers answer your questions and pay through one shared link. Use a fixed amount or let customers choose existing products, with your Payment Page branding and available payment methods.

Create a payment form

Start with a template or build your own form.

Before you publish

You can prepare a private draft first. Publishing requires an active Payment Page and an available connected payment provider for the form’s currency. Forms work with eligible PayPal, Mollie, Stripe, Revolut and Payoneer connections. Availability depends on your account, provider and currency. You do not need to connect PayPal specifically. When there is one eligible connection, customers do not need to choose a provider. Your normal PayRequest plan fees and payment-provider fees apply.

Create and publish a form

1

Choose a template or start from scratch

Open Payment Forms → Create payment form. Search the template library or filter by events and courses, orders, services or contributions. Select a card, then choose Use template. You can also start entering your own offer without applying a template.
2

Describe your offer

Enter a title and description. Optionally upload a JPG, PNG or WebP cover image, up to 5 MB. The cover is separate from files customers upload as answers.
3

Choose your pricing

Select Fixed amount or Existing products, then choose a supported currency and review the tax settings. All paid options and the final total are calculated by PayRequest.
4

Add questions and availability

Add the details you need, optional paid extras, conditional questions or customer uploads. Add terms, a closing date or a booking limit if appropriate.
5

Save and publish

Save draft keeps your changes private. Publish makes the form available through your Payment Page. Review and publish later draft changes explicitly.

Available templates

Templates configure editable questions; they do not automatically create products, reserve appointments or establish a subscription. The library has ten illustrated cards, a search field and category filters. Scroll within the gallery to see more cards; the apply button stays below it. Filtering does not discard your selected template.
Preferred dates are requests, not confirmed bookings. Fixed contributions use a seller-set amount. Payment Forms currently do not provide security-deposit authorizations, recurring subscriptions or customer-chosen amounts. Use the appropriate native PayRequest flow for those needs.

Fixed amounts and paid options

With Fixed amount, set a base price of at least 0.50 in your selected currency. The base price and paid question options include the chosen form tax rate. You can add up to 20 questions using short answers, long answers, email, choice lists, checkboxes and file uploads. A choice or checkbox can add a fixed amount. Mark answers as required where needed. For example, an event form can collect a participant’s details, offer standard or priority registration, and add a paid extra. Customers see an updated total before paying.

Sell existing products

Choose Existing products to include up to ten compatible active, one-time products in the same currency.
  • Let customers choose exactly one product or select multiple products.
  • In multiple-product mode, mark products that must always be included.
  • Set permitted quantities for products that support quantity selection.
  • Keep each product’s existing price, tax settings and supported delivery.
There is no additional base charge in product mode. The form tax rate applies to paid question options; product tax settings remain authoritative. A one-product form can use that product’s image when you have not uploaded a form cover. Bookings, subscriptions, physical shipping, limited stock, Discord provisioning and products with their own checkout options use their existing checkout flows. They cannot be added simply by choosing a template. If product pricing changes while someone has the form open, they may need to reload before paying. For supported digital products, verified payment creates the native product order and starts the existing delivery flow. A completed form alone does not grant downloads or access.

Show questions conditionally

For a dependent question, choose Show this question when, select an earlier choice list or checkbox, and choose the matching answer. For example, show a personalization text field only when a customer selects a personalization extra. Hidden questions are not required and their paid options are not charged. Conditions must reference earlier questions. If you remove or reorder a source question, correct its dependent conditions before saving.

Receive private customer files

Add a File upload question for a customer’s logo, briefing, photo or reference document. Files are private. The account owner downloads them from the form’s submissions dashboard; they do not receive public image URLs and are not sent as email attachments. File answers can also be required or conditional.

Set a booking limit or closing date

Under Availability, optionally configure:
  • Maximum paid bookings to limit the number of checkouts.
  • Close for new payments at to set a closing date and time in UTC.
  • Closed message to explain why new payments are no longer accepted.
Each checkout reserves one booking, regardless of product quantity. Pending or uncertain payments keep their place until the final payment outcome is known. Recorded failed, canceled, expired or refunded payments release it.
This is a form-wide checkout limit, not per-product inventory or a count of all attendees in a group booking. Use separate forms or the appropriate native product flow when capacities differ.
A closed form remains readable, but its checkout is disabled. Existing payment attempts can still complete after the closing time. Unpublishing also stops new checkouts without deleting existing submissions or canceling payments already started.

Share your form

Published forms use your Payment Page address:
Your avatar, banner and Page branding remain visible. Customers can select their language in the header. Desktop separates the offer from the scrollable form; mobile stacks the content. Share the link directly or use Send to customer to email a published form to an existing customer in your account. Sending a link does not create a paid order. Older UUID-based form links redirect to the current readable address.

Checkout and payment confirmation

Customers see selectable payment methods supported by the connected provider. Methods depend on the merchant account, currency, amount and, where applicable, the customer’s device. Some methods require additional billing details. The standard payment button starts the provider’s secure checkout; PayPal uses its PayPal payment flow. Submitting answers, returning from checkout or receiving a customer record is not proof of payment. PayRequest confirms the provider’s payment status before granting paid delivery. If a payment is still being checked, customers should wait for confirmation rather than paying again.

Manage submissions and export

Open a form’s submissions to:
  • Filter All, Paid, Open, Failed or Refunded payments.
  • See confirmed-paid totals grouped by currency.
  • Review answers, selected products, paid options and accepted terms.
  • Download private customer files.
  • See reserved bookings when a capacity limit is configured.
  • Inspect linked product-order delivery and open the native order.
  • Export a CSV using the selected payment-status filter.
A submission marked Not confirmed is not a paid sale. Product delivery follows the existing order flow; some services or manual deliveries need further action from you.