Accounts & modes

A merchant account is a fully segregated tenant on digid pay: its own keys, plans, transactions, webhook endpoints and settlement views. Nothing crosses between merchants — a request authenticated for merchant A can never read merchant B's data (cross-tenant lookups return 404).

Account states

stateDiagram-v2
    [*] --> sandbox: signup
    sandbox --> pending_activation: submit for activation
    pending_activation --> live: operator approval
    live --> suspended: operator action
    suspended --> live: operator action
    suspended --> closed
    live --> closed
    pending_activation --> sandbox: request changes

State	Meaning
sandbox	Auto-created at signup. Full API + test rails; no real money.
pending_activation	You submitted for live access; operator review in progress.
live	Real payments; live keys minted.
suspended	Live traffic stopped (keys revoked, connector disabled, webhooks halted).
closed	Terminated account.

Modes

Sandbox and live are modes on the same account, not separate accounts:

	Sandbox	Live
Keys	pk_sandbox_… / sk_sandbox_…	pk_live_… / sk_live_…
Rails	test rails provisioned by digid pay	real acquiring via our European acquiring partner
Money	none moves	real, settles directly to you
Access	at signup	after activation

A sandbox key can never initiate a live-mode intent; a live key can never hit test rails.

Signup

Signup is self-serve (https://digid.cc/signup) and immediately provisions an isolated sandbox account with a key pair — no human in the loop. Email verification is required; MFA is enforced at first login.

Status: signup + auto-provisioned sandbox is planned (being built). Once shipped this page flips to live.

Activation

Going live is operator-gated — never automatic:

1. From the dashboard, submit your account for activation (confirm your business details and plan).
2. The digid pay operator reviews the request (FR-2).
3. On approval your account moves to live, you are notified, and live keys can be minted.

Every activation/revocation carries an operator approval record. There is no path from signup to live capability without that recorded approval.

Multi-merchant platform operators

An agency or platform can hold many merchant accounts, each segregated. A platform's own account is itself just a merchant account — there is no implicit visibility across the merchants it manages unless each consents and is configured accordingly.

Related

• Plans & pricing — what you pay per transaction.
• Authentication — key pairs per mode.
• Go live — the activation checklist.