Advanced Settings

The Settings abstraction allows administrators to fine-tune the behavior of their Organization.

Notifications (Email, Slack, SMS)

Under Settings > Notifications, you define how the platform communicates with your team and your buyers.

• SMTP Service: Configure your outbound mail server credentials (host, port, TLS). The gateway decrypts these credentials entirely on-the-fly when sending emails.
• Slack Webhooks: Receive real-time channel alerts for specific payment.succeeded or payment.failed event types.
• Templates: Customize the HTML/Text of emails sent to customers (e.g., the "Invoice Created" template).

Templates

Under Settings > Templates, you can manage both notification templates and document templates.

• Notification Templates: Email, Slack, and related outbound communication templates.
• Document Templates: PDF layouts for invoices, credit notes, and receipts.

Document templates can be created from scratch, duplicated from a system default, previewed, set as defaults, and assigned to invoice flows. Invoicing settings can point to an organization-wide default PDF template, while sites can override that template for storefront-specific branding.

Invoicing

Under Settings > Invoicing, organizations configure two independent document-number layouts: one for invoices and one for credit notes.

• Each layout controls prefix, optional middle text, suffix, start number, digit width, year basis, visible date detail, separator, and reset policy.
• Fiscal-year labels are derived by the backend from the issue date and the configured fiscal-year start month.
• Sites may override only the invoice and credit-note prefixes. They do not create their own sequence counters or fiscal/calendar rules.

The full API payload shape for these settings is documented in the Admin API reference (see Organization Settings on the Admin API page).

Data Retention & Geolocation

The platform includes organization-scoped retention controls to support your data minimization and lifecycle policies.

Data Retention

Under Settings > Retention, you can configure:

• Transaction Data Retention:
  • Enable or disable automatic transaction-data cleanup.
  • Set retention period in days (minimum 30, maximum 2555 / ~7 years in UI).
• Customer Data Retention (per field category):
  • IP Addresses
  • Billing Address
  • Shipping Address
  • Customer Email
  • Transaction Items
  • Optional "retain country information" toggle

0 can be used for immediate deletion on supported customer-data fields.

[!IMPORTANT] Retention values should be aligned with your legal/accounting obligations. Some jurisdictions require minimum retention periods for financial records.

Geolocation Rules

Under geolocation settings, you can configure provider-backed geo checks and apply policy decisions in checkout flows (for example, restriction handling for specific jurisdictions).

The Tax Engine

The gateway features a robust, multi-national tax capability.

1. Tax Rates: Define specific percentages (e.g., Standard 20%). Crucially, these rates feature an EffectiveFrom timestamp. If a government passes a law increasing tax to 21% starting next year, you can program it today; the engine handles the temporal switch exactly at midnight UTC.
2. Tax Rules: Connect a Rate to a demographic. You define rules like "If Seller=DE and Buyer=Any EU Country, and the item is a Digital Service, apply the Buyer's local rate (OSS)".
3. EU VAT OSS Configuration: Specifically configure your physical presence, and the gateway will automatically mandate the collection of 2 non-contradictory pieces of location evidence (e.g., IP vs Billing Country) for 10-year safe-keeping.

Reporting and API: Tax by country, revenue by country, and VAT OSS filings in the Admin Panel are backed by canonical tax records and report endpoints (see Invoicing & Tax architecture and the Tax Management / Tax records tables in the Admin API). Programmatic rate maintenance includes POST /api/v1/tax-rates/replace-defaults (scoped tax_rate:execute).