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]

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.

MFA users

We have two test banks to test MFA challenges

• Pied Piper Bank: AU00002 (mfa-challenge always)
• Nucleus Bank: AU00003 (mfa-challenge intermittent - 50/50)