Enter the checkout email address
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Provide a valid required email up to 191 characters.
What this guide helps you do
Provide a valid required email up to 191 characters. This section documents identity fields, payment choices, mandatory terms, rate limiting, order tokens, native invoices and branded email.
Follow these steps
- Go to /shop/checkout and open the workflow that matches “Enter the checkout email address”. Confirm the page or record context before making a change.
- Check the cart.
- Go to Checkout.
- Sign in when guest checkout is disabled or native invoice payment is required.
- Complete name, email, phone, shipping address and notes.
- Select an available payment method.
- Accept terms and place the order once.
- Use the public order page and, for native invoice checkout, the secure host invoice payment URL.
Fields and options
- Guide focus: Provide a valid required email up to 191 characters.
- Name, email, phone, shipping address and notes
- native_invoice, bank_transfer or cash_on_delivery
- Mandatory terms acceptance
- Checkout idempotency key
- Client/contact IDs for signed-in users
- Public order reference and token
- Invoice ID and payment URL
- Email templates and internal recipient
Rules and limits
- Checkout is limited to 20 attempts per hour per IP.
- Name and valid email are required.
- Terms acceptance is always required.
- native_invoice is available only to an eligible signed-in client when enabled and host payment modes exist.
- Guest users can use bank transfer or cash on delivery when guest checkout is enabled.
- Order token is stored as a hash.
Check it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- One public order is committed and shown through its tokenised URL.
- Eligible native-invoice orders have an invoice/payment URL.
- Enabled email notifications are sent through the host mail system.
Safety checks and troubleshooting
- Do not expose token hashes or reuse public links in public logs.
- Do not enter payment-card data into notes or bank fields.
- Check the existing order before resubmitting after a network interruption.
Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.
