Configuration
Owner-only settings for payments, email delivery, and legal information.
The Configuration tab is an owner-only section of Settings for payment processing, email delivery, and legal information. Only users with the Owner role can see and edit this tab.
Payments
Connect your Stripe account to accept online payments for ticket sales.
| Field | Required | Description |
|---|---|---|
| Stripe Publishable Key | No | Your Stripe publishable API key. Must start with pk_. Found in your Stripe Dashboard under Developers > API keys |
| Stripe Secret Key | No | Your Stripe secret API key. Must start with sk_ or rk_. This key authorizes charges and should be kept confidential |
| Stripe Webhook Secret | No | The signing secret for Stripe webhook events. Must start with whsec_. Found in your Stripe Dashboard under Developers > Webhooks, on the endpoint detail page |
How keys are stored: All three Stripe fields are encrypted at rest (AES-256-GCM). When you open the Configuration tab, existing values are masked, showing only the prefix followed by dots (e.g., pk_live_abc1****). If you save the form without changing a masked value, the original key is preserved; it will not be overwritten.
When to fill these in: Payments will not work until all three Stripe fields are configured. You need a Stripe account with API access enabled. Use test-mode keys (pk_test_, sk_test_) while setting up, then switch to live keys when ready to accept real payments.
Control how outgoing emails (ticket deliveries, invitations, order confirmations) behave.
| Field | Required | Description |
|---|---|---|
| Reply-to Address | No | The email address that appears as the reply-to on all outgoing emails. Must be a valid email address. If left empty, replies go to the system default sender |
| Blocked Email Domains | No | A comma-separated list of email domains to reject. Orders and invitations to addresses at these domains will be blocked. Example: tempmail.com, throwaway.org |
| Blocked Email Patterns | No | Regex patterns for blocking specific email addresses. Enter one pattern per line. Useful for more targeted blocking than domain-level rules. Example: ^test\+.*@ to block all plus-aliased test addresses |
Blocked Email Domains is useful for preventing disposable or temporary email services from being used during checkout. Buyers attempting to purchase with a blocked domain will see an error.
Blocked Email Patterns offers finer control. Each line is treated as a regular expression tested against the full email address. Use this when domain-level blocking is too broad.
Legal
Provide your organization's legal details. These appear in transactional emails, invoices, and the buyer-facing footer to comply with local regulations.
| Field | Required | Description |
|---|---|---|
| Legal Name | No | Your organization's official registered name (e.g., "ACME Events SRL") |
| Registration Number | No | Company registration or incorporation number (e.g., BCE number in Belgium, Companies House number in the UK) |
| VAT Number | No | Your VAT or tax identification number (e.g., "BE0123.456.789"). Shown on invoices when applicable |
| Legal Address | No | The full registered address of your organization. Shown in email footers and invoices. Use multiple lines for readability |
Why fill this in? Many jurisdictions require commercial emails to include the sender's legal identity and address. Filling in these fields ensures your ticket emails and order confirmations are compliant. Even where not legally required, showing this information builds trust with buyers.
Summary
Values saved here take precedence over any defaults set by the Praticable team during your initial setup.
| Section | Fields | Encrypted | Who can edit |
|---|---|---|---|
| Payments | 3 (Stripe keys) | Yes | Owner only |
| 3 (reply-to, blocked domains, blocked patterns) | No | Owner only | |
| Legal | 4 (name, registration, VAT, address) | No | Owner only |