There’s nothing worse than developing against an API with crappy test data. We get that! This is why we have put a lot of effort into ensuring that our test data mimics real production data that your app will consume.
The test data that we provide (below) has been designed to mimic a real life user. This means that just a like a real user would spend and receive funds throughout the day - our test accounts have been designed to do the same thing. Therefore you should expect to see new transaction records being created throughout the day, and the account balances adjusted accordingly.
The transaction data is completely random to best replicate the type of data that you should expect to see for your own customers.
Sandbox environment
You can use our sandbox environment for free right now - just grab an API key to get started (via the Developer Dashboard). We recommend using our test bank
Hooli.
Note: There is a limit of 500 for sandbox connections. If you reach your limit and need to have this increased, feel free to reach out to [email protected].
🆕 Initial Testing and Billing Policy
For initial testing, BASIQ services are available at no cost. This free access allows you to extensively test our platform's capabilities using our sandbox environment. However, once you transition from testing to becoming a paying customer, charges will apply for any users on your platform. This billing policy ensures that you have the opportunity to fully explore and understand the value of BASIQ services before any financial commitment is required.
If you have questions about transitioning to a paying customer or about our billing structure, please contact our support team at [email protected].
loginId | password | persona | suitable use case |
|---|---|---|---|
Wentworth-Smith | whislter | This is a joint account. income (transaction account): 2 sources of salary, monthly stable salary & fortnightly stable salary. liabilities: mortgage (mortgage account) and car loan (payments in the transaction account) expenses: has predictable expenses (credit-card account) |
|
Whistler | ShowBox | income (transaction account): 1 source of salary, fortnightly salary liabilities: has BNPL (transaction account), no mortgage / personal loan expenses: no daily expenses risk flags: large amount of external transfer (debit to Jared) |
|
Gilfoyle | PiedPiper | income (transaction account): stop fortnightly salary, unemployment benefits liabilities: increase in BNPL (transaction account) expenses: has predictable expenses (credit-card account) risk flags: late fee (credit-card account) |
|
gavinBelson | hooli2016 | income (transaction account): 1 salary + 1 additional earning, increase monthly salary + extra income (tutoring weekly volatile) liabilities: personal loan (loan account) expenses: predictable expenses (credit-card account)
|
|
jared | django | income (transaction account): weekly volatile income from uber + credit transfers from Whistler liabilities: unshared mortgage account (payments in the transaction account), car loan (payments in the transaction account) expenses: predictable expenses (credit-card account) assets: term deposit |
|
richard | tabsnotspaces | income (transaction account): high stable fortnightly income, 2 rental incomes liabilities: 3 mortgages (1 shared mortgage account & 2 unshared mortgages), 2 car loans (payments in the transaction account), 4 credit cards (1 shared credit card account & 3 unshared credit card accounts) expenses: predictable expenses (credit-card account) |
|
laurieBream | business2024 | Happy path persona with business fields and business consumer consent |
|
ashMann | hooli2024 | income (transaction account): 1 salary monthly income, rental income liabilities: unshared credit card transactions (payments in the transaction account) expenses: predictable expenses (credit-card account), rental expense risk flags: gambling behaviours, cash withdrawal, crypto exchange |
|
Unhappy path test users
Unhappy path test users
The following users will always return the same errors at the same job step. We created them to ensure you could fully test the unhappy paths your user may encounter while connecting their accounts via DDC and handle them appropriately. See here on how to best handle these scenarios.
loginID | password | Failure scenario |
|---|---|---|
bighead | password | Error: |
erlich | aviato | Error: |
jianYang | nothotdog | Error: |
MFA users
We have two test banks to test MFA challenges
- Pied Piper Bank (
mfa-challengealways) - Nucleus Bank (
mfa-challengeintermittent - 50/50)
| loginId | password | mfaChallengeMethod | mfaChallengeInput | mfaChallengeSolution |
|---|---|---|---|---|
| jared | django | token | ["OTP Password"] | ["1234"] |
| richard | tabsnotspaces | token | ["OTP Password"] | ["1234"] |
| gavinBelson | hooli2016 | security-questions | ["What's your first company?"] | ["Hooli"] |
| Gilfoyle | PiedPiper | security-questions | ["What's your first company?"] | ["Hooli"] |
| Whistler | ShowBox | security-questions | ["What's your favourite company?", "What's the ID of this institution?"] | ["Basiq", "AU00000"] |
| Wentworth-Smith | whislter | security-questions | ["What's your favourite company?", "What's the ID of this institution?"] | ["Basiq", "AU00000"] |