One system, six roles, permissions that stack.

Open the system URL and sign in with the email + password assigned to you. Accounts can only be created by a higher role (Sales by Manager/Master; Manager/Onboarder/Master by Master). Switch 中文 / English from the top-right at any time.

After signing in you land on the dashboard. Three stat cards show Merchants / Contracts / Onboarded — the numbers scope to your role: Sales sees only their own, Manager their Provider, Master everything. The left menu is exactly the set of features you are authorized for (shown here as Master, with every item).

On the Merchants page: a search box (fuzzy over name / NZBN / provider / sales, or paste a MID to find its owner), three filter dropdowns (status / provider / sales), + New Merchant, and Batch intake (paste text, AI splits it into merchants — everyone except Onboarder / Viewer). Master also gets a Delete button per row and a Deletion log at the top. Click a merchant name to open its detail.

1. Click + New Merchant to open the dialog.
2. Enter the merchant name; click “Look up NZBN by name” to auto-fill the NZBN and company number.
3. Pick a provider (Sales is auto-assigned to their own).
4. Click Create.

⚠️ If the company is already registered as a service provider, the system refuses to also create it as a merchant.

Panels include: KYB (Refresh KYB, download the certificate of incorporation and directors/shareholders extract), Bank account (account name / number / bank, with a one-click Check against statement; every change is logged), MID / platforms (record the merchant's account number on each payment platform, active / closed), Terminal Service Agreement (Open contract, see next step), Documents upload (bank statement / director ID / proof of address / other, stored securely and not public), and Contact.

The “Change status” dropdown is visible to Master only and can move the merchant to any status. An Onboarder instead sees an “Onboarding complete” button here. A Viewer sees everything masked except the merchant name. Pulling KYB auto-advances the status to KYB done.

1. On the detail page click Open contract.
2. While it is a draft, fill in the terms / rates: pick Plan A (flat monthly subscription) or Plan B (per-transaction card-present rates); the Online channel is independent — tick it to fill, works under either plan; plus a global fixed fee per transaction (no GST), a chargeback fee, and optional Special Conditions (ticked → a separate page 3). Click Save.
3. Click Merchant link and Guarantor link to generate the two role-scoped signing links; send each to the signer (each unlocks only their own fields and signature).
4. The header shows the live Merchant / Guarantor signing status; once both have signed, the owner clicks Lock to finalize — the contract and the merchant status both advance to Signed.

Where the merchant signs: Commercial Schedule (page 1) + Policy Terms (page 2) + Special Conditions (page 3, only if ticked) — any missing page is rejected with a prompt. The guarantor signs once (Personal Guarantee, only when a guarantor is filled in).

Signing links expire in 7 days: after that the link is dead — it can't even be opened to view; re-sending gives another 7 days. For offline signing, upload the signed scan in the Agreement panel (equivalent to Lock, with the scan kept as the signed record), or have Master mark it Signed.

⚠️ Once a signing link is generated (status becomes “Sent”), the contract is locked — rates and terms can no longer change. To edit, do it in the draft stage before sending; a wrong send must be voided. A signed contract can't be edited — to change it, start a new contract (the old one stays in force until the new one is signed).

The Team page is accounts only: each person’s Merchants / Signed counts, with Reset password. Click a button to create an account — the scope field depends on the role: creating a Manager picks a provider; creating a Leader / Sales picks a group (the group fixes the provider, so you don’t pick a provider separately); creating a Master / Viewer needs no scope. Creation stacks by tier: Leader creates Sales in their group; Manager creates Leader / Sales in their provider; Master creates any role. Master can click a person’s Signed count to open their commission settlement page in a new tab (settle / unsettle per row, or settle all).

Sales groups (Master only): Master's left nav has a “Groups” page to create / list sales groups (pick a provider + name it); each group row also has a group-level agreement entry. The Team page keeps only account actions.

The Service Providers page creates / edits the company entities that onboard merchants on the platform (not login accounts). Click + New Provider → enter the legal name → (optionally Look up NZBN by name) → Create. The list shows each provider’s merchant count and status; Edit updates details.

The Onboarders page lists each onboarder’s onboarded count; click Details to see their onboarding history (date / merchant, with a date filter). (The sample environment below has no onboarders yet.)

Reached from the Deletion log button on the Merchants page — audits who deleted which merchant and when (including the status at deletion, provider, NZBN). Only unsigned and unsettled merchants can be deleted; signed / settled ones cannot.

The Devices page registers terminals: device number / model / responsible person / destination (assigned to a provider or a merchant). Terminals reporting in are auto-discovered and registered; if the MID they report is already on a merchant, the destination is auto-set to that merchant (only when empty — it never overwrites a manual assignment). The list shows last-seen time / store, whether it was auto-discovered, and whether details are complete.

The System Settings page has three parts: default per-transaction rates (a fallback for Plan A merchants whose contract leaves the per-transaction cells blank; editing these never changes an already-sent contract), contract versions (clause text is frozen per version; a contract is pinned to its version when sent, so changing terms means releasing a new version), and payment platforms (the acquirer list behind every MID; retiring one only hides it from new entries).

The POS Orders page aggregates platform-wide payment / refund traffic, matched to merchants by MID. Filter by MID search, by outcome (approved / declined / cancelled / error), or show unmatched orders only. Merchant takings are visible to Master only.