Glossary
Every term below was observed in the live dashboard. Where two terms sound similar (Payment request vs. Invoice; Bills vs. Invoices; Subscription vs. Bills), the entry calls out the distinction.
Application
A registered integration in the Connect section. Each Application gets its own API Key (secret, server-side) and Public Key (safe in browsers/mobile). One Application per integration is the right granularity.
API Key
The secret half of an Application's credentials — a long signed token used to authenticate server-side calls. Treat as a password. See API keys.
Bills
Bills your suppliers send you — accounts payable. The platform helps you log them, route them through approval, and schedule payments. The opposite of Invoice. See Bills.
Branding
Account-level visual configuration — logo, checkout image, brand colours, fonts applied to the customer-facing surfaces. See Settings → Branding.
Company Merchant ID
A read-only identifier for the merchant account, shown on Settings → Company. Use this when contacting support.
Connect
The developer hub — at /connect/applications. Where you create Applications and get API Keys.
Customer
A person or business you charge. Listed in Customers. Customers can be tagged with Customer Groups and assigned an Account Manager.
Customer Group
A label segmenting customers (e.g., Wholesale / Retail / VIP). Used for filtering and (likely) per-group config.
Invoice
A structured request for payment sent to a customer — line items, due date, status (Draft / Unpaid / Overdue / Paid). The customer pays through a hosted page; the resulting payment shows up as a transaction. See Invoices.
Order
A unit of in-shop fulfilment, tracked through New → In-progress → Completed on the Orders board. Always scoped to one Shop.
Owner
The user role with full administrative permissions on a merchant account. Set up under Settings → Manage users.
Payment provider
An acquirer or payment method enabled on the account (cards, wallets, bank rails). Toggleable per method under Settings → Payment providers.
Payment request
A shareable payment link — you create it, send it to a customer (any channel), they pay through a hosted page. Two modes: Amount (you specify a number) and Products (catalog-driven). Lighter weight than an Invoice. See Payment requests.
Two extra modes on the form:
- Stored Card Mode — capture the card on file (typically for future charges).
- Pre-Authorisation — authorize a hold rather than capture immediately.
Public Key
The non-secret half of an Application's credentials — prefixed pk_development_… or pk_live_…. Safe to ship in browsers and mobile apps.
Receipt
The customer-facing confirmation of a payment. What appears on it is configured under Settings → Receipt information. Optional toggles: Security code, Confetti animation, Emoji rating, Email receipt.
Refund
A return of funds to a customer for a previously successful transaction. Initiated from the transaction detail.
Shop
A physical sales channel — typically a location with its own static QR code that customers scan to pay. Listed in Shops. A shop has a status (Online / Offline) and a type (observed: Scan & enter amount).
Subscription
The merchant's plan with the platform — what they pay to use the dashboard. Has a Subscription code (e.g., STANDARD), an amount, and a frequency. Visible on Subscription (left-nav label: Billing). Distinct from Bills.
Supplier
A vendor or contractor you pay. Source of Bills. Can be added manually or synced from Xero or QuickBooks. See Suppliers.
Transaction
A single payment record — successful, failed, or refunded. The Transactions page is the source of truth for what's happened in the account.
The side-nav entry didn't navigate when clicked, suggesting it's enabled per account. Document the page once you have an account where it's active.
Verified
The state of a merchant company after KYC is complete. Several Company fields lock once verified.