Skip to content

Custom checkout

A checkout profile controls the data collected for a product. Open the product editor, choose Sales and settings → Checkout, and enable Custom checkout for this product. Products without a profile keep their existing checkout and webhook format.

  • Buyer: allow people, organizations, or both. Organizations provide their company name, tax ID and billing address. GUS lookup requires the GUS integration to be enabled.
  • Recipient: an organization buyer can specify a different recipient with its own tax ID and address. Leave it off when the buyer is also the recipient.
  • Phone: optional or required; stored in international E.164 format (for example +48500100200).
  • Quantity: set minimum and maximum seats (1–100). Choose a hidden fixed minimum, a checkout selector, or a product-page selector.
  • Participants: requires Quantity. Collect one first name, last name and unique email per seat. Optional participants may be left entirely empty. At one seat, buyer prefill is available.

Profiles support the default checkout template and one-time products. Subscriptions, tips, pay-what-you-want products, bundles and OTO are unsupported. Products issuing licenses cannot use quantities above one. Invalid combinations are rejected when saving.

A municipality buys five seats for a school. Configure Buyer (organization), Recipient, required Phone, Quantity (1–20) and required Participants. The municipality is the buyer and provides its billing address and tax ID. The school is the recipient and supplies its own address and tax ID. The contact provides a phone number and details for five participants. All names in this example are fictional.

An admin opens Payments → transaction details → Checkout data to read the saved buyer, recipient, phone, quantity and participant table. Additional custom field answers appear in this section too. An incomplete-details warning means required checkout data was not collected; the completed payment still grants access.

For a product with a profile, purchase.completed adds orderDetails with stable keys: buyer, recipient, phone, participants, quantity. Missing modules are null. The objects preserve the stored module format: buyer has v: 1, type, name/company, nip, address, postal_code, city, country and optional email; recipient has v: 1, differs and company/address fields. Phone and quantity use { "v": 1, "value": ... }; participants use { "v": 1, "people": [{ "first_name": "Anna", "last_name": "Example", "email": "anna@example.com" }] }.

For an organization, invoice uses the saved buyer: needsInvoice, nip, companyName, address, city, postalCode, country. A different recipient is included as invoice.recipient in its stored snake_case module format. Personal purchases without an invoice request omit invoice. Products without a profile do not receive orderDetails and retain their existing invoice format. Existing customFields continue to carry resolved answers.

See Webhooks for endpoint configuration and delivery settings.