Sandbox and country-specific testing

This page contains test-only identities and account numbers. Never use them in production. Never copy a real person’s identity, account, or credential into Sandbox.

Choose a testing mode

Sandbox behavior differs from production because the available test data varies by country. Norway, Denmark, and Sweden support two onboarding modes:

1. Reserved ZTL scenarios use organization numbers that deterministically reach Accepted, ManualHandling, or Rejected. ZTL supplies the company data, beneficial owners, signing combinations, and screening results through its own sandbox logic instead of using the normal external integrations.
2. Integrated sandbox flows exercise external test environments. They are closer to the normal integration but their data and final outcome can be less predictable.

Reserved organization numbers are reusable

Reserved organization numbers can be reused even when a company or a previous successful onboarding already exists for your partner integration.

Use reserved scenarios for deterministic status handling. Use integrated flows for realistic handoffs and signing.

Norway onboarding

Testing in Norway sandbox supports two onboarding modes: reserved scenarios for a predictable final status and the normal integrated Tenor flow for testing external handoffs.

Reserved scenarios

Organization number	Expected status after signing
111111111	Accepted
222222222	ManualHandling
333333333	Rejected

Start with country NO, leave the supplied beneficial owners unchanged, and complete the signing option shown in the onboarding UI.

Integrated Tenor companies

ZTL uses Tenor test data from the Norwegian Tax Administration, which provides thousands of test companies. This table is only a sample; other valid Tenor test companies can also be used. See the Tax Administration test-data source.

Organization number	Organization name
312701103	LEKKER GILD STRUTS UAB
312246538	OPPRETT SKAMFULL STRUTS AB
312587629	NÆR HÅRSÅR STRUTS LTD
310211036	POMPØS KNUSLETE LEOPARD ASA
310223719	FREDELIG TYPISK GIRAFF SPAREBANK
313513408	FALSK ØDE TIGER AS
314208641	EKSTRA KLOK TIGER AS
210129812	SPETTETE INNSIKTSFULL HUND DA
314270320	TRÅDLØS MATT TIGER AS
313513580	OVERSIGHT HELLIG TIGER AS
310163449	SENTRAL UKLAR PUMA
310274682	HEL VERD NISE PENSJONSKASSE
310219622	STOLT UMUSIKALSK ALLIGATOR

Start with one of these companies or another valid Tenor test company, choose the signing option displayed, and complete signing in Signicat. The shared Norwegian test user normally asks only for:

• one-time password: otp
• password: qwer1234

Important: Norwegian test users are shared

The pre-generated Norwegian test users are shared by everyone using sandbox. They can become temporarily unavailable when another tester enters an incorrect password too many times.

If the shared user fails, create a personal Signicat test user and enter that test SSN if prompted; the same one-time password and password above apply. A personal test user avoids conflicts with shared users. If you test this flow often, keep your personal test user’s SSN available for reuse.

The signer identity is normally prefilled, so Signicat normally asks only for the one-time password and password.

Tenor supplies all company information except signing combinations. Those come from a separate source with a small predefined pool of approximately 10 test companies. Sandbox maps a Tenor company to one of those companies, so different organizations can return the same signing combinations. This mapping exists only in sandbox and is expected behavior, not incorrect company data.

Denmark onboarding

Testing in Denmark sandbox supports two onboarding modes: reserved scenarios for a stable, repeatable final status and the normal integrated flow for testing external environments.

Reserved scenarios

Organization number	Expected status after signing
11111111	Accepted
22222222	ManualHandling
33333333	Rejected

Start with country DK, leave supplied beneficial owners unchanged, and use any available sandbox signer supported by the onboarding UI. These organization numbers do not require a specific signer identity or signing method.

Integrated companies and MitID

Organization number	Matching person
23456788	Christian Svanholm-Nielsen
41773863	Sven Holst
12345674	Tage Olsen
38724991	Bettina Christiansen

For these organizations, the normal integrations are used:

• company information and beneficial owners come from external test-data sources;
• signing combinations come from an external test-data source; and
• screening runs in the AML provider’s test environment.

Those environments have limited and sometimes inflexible data, so they do not guarantee a particular final status.

For complete signing:

1. Create a test identity with the MitID test tool.
2. Use the name matching the organization in the table.
3. Start onboarding with that organization and select the displayed signing option.
4. Sign with the matching MitID test user.

Sweden onboarding

Testing in Sweden sandbox supports two onboarding modes: reserved scenarios for a predictable final status and the normal integrated flow for testing company data and BankID signing.

Reserved scenarios

Organization number	Expected status after signing
1111111111	Accepted
2222222222	ManualHandling
3333333333	Rejected

Start with country SE, leave supplied beneficial owners unchanged, and complete the signing option shown.

Integrated companies and BankID

Organization number	Matching personal number and name
5560572850	—
5565002465	—
8430025331	—
5569030264	—
6805029268	196805029268 – Petra Efternamn2401
5564779444	196805029268 – Petra Efternamn2401
5569994600	197904182396 – Kuno Efternamn2993
9168937861	—
5590506506	196501022773 – Pinoz Harem
5164010133	—
5590672613	—
8110022392	198110022392 – Ebbe Efternamn3672
9697715770	—
5564866803	196805029268 – Petra Efternamn2401
5564881422	198110022392 – Ebbe Efternamn3672

Rows with — can test company-data stages but cannot complete signing with a matching identity. For end-to-end signing:

1. Choose a row with a person.
2. Obtain a Swedish test BankID for that personal number.
3. Start onboarding with the matching organization.
4. Select the displayed signing option and complete it with that BankID user.

Supported sandbox banks

These are the banks officially supported in Sandbox. Banks not listed here may still work, but they are not officially supported and may stop working at any time.

If you need support for additional banks, please reach out to us.

Bank	Country	BIC	Organization requirement	User ID	Notes
DNB	Norway	DNBANOKK	None	TX99999 or TX99998	Accounts 12095221031 and 12024833710 require two approvers
Nordea	Norway	NDEANOKK	9 digits	Valid Norwegian test SSN	—
Nordea	Sweden	NDEASESS	10 or 12 digits	Non-empty	Sandbox payments may not show completed status reliably
Swedbank	Sweden	SANDSESS	None	Valid Swedish test SSN	Sandbox and production BICs differ
Nordea	Denmark	NDEADKKK	8 digits	Non-empty	—
Mock bank	Denmark	ZTLXDKXX	None	Non-empty	See the trigger scenarios below

Denmark mock bank

The Denmark mock bank provides deterministic happy paths and status triggers. Its behavior may evolve with testing needs.

Consent and accounts

A consent created with user ID REJECTED or EXPIRED reaches that outcome after the user follows the SCA link. Any other user ID is accepted. Accounts primarily support happy paths; balances and entries reflect completed transactions and are not randomly generated.

Payment triggers

All payments begin in Unsigned. Recipient account behavior is applied after the first approval unless noted:

Recipient account	Result	Timing or action
99990000000001	Rejected	After approval
99990000000002	CustomerActionRequired / PartlySigned	Requires approvals by two different users
99990000000003	CustomerActionRequired / SmsConfirmationRequired	Changes after approximately one hour
99990000000004	CustomerActionRequired / InsufficientFunds	Reason appears on dueDate; becomes Rejected the following day
99990000000005	InProgress	Moves without approval
99990000000011	Approval REJECTED	Any payment in the approval triggers this result
99990000000012	Approval CANCELLED	Any payment in the approval triggers this result

Do not use its trigger account numbers outside sandbox.

General limitations and safe handling

• External identity, company-data, screening, and bank sandboxes can be slow or unavailable independently of ZTL.
• Reserved scenarios verify your state handling but do not reproduce every external integration.
• Timing-based scenarios are approximate. Poll with bounded intervals instead of sleeping a fixed time and assuming the result.
• Keep test credentials in sandbox-only configuration. Do not log identity values, consent links, SCA data, or access tokens.
• Test 401, 404, 409, 422, and server errors through controlled fixtures or agreed scenarios; do not generate abusive traffic.
• Ask ZTL to confirm a scenario that stops working before changing production logic around a sandbox-only observation.