Banking Personas
This page defines the Banking personas that assist in the testing and validation of your data adapter build.
The Biza test cases explicitly rely on personas for execution, and there are some assumed preconditions regarding quantity of transactions, size and availability of accounts which make defining personas helpful.
List of Banking Personas and Preconditionsβ
| Persona A | |
| Accounts and Types |
|
| Transactions |
|
Β Β
| Persona B | |
| Accounts and Types |
|
| Transactions |
|
Β Β
| Persona C | |
| Accounts and Types |
|
| Transactions |
|
Β Β
| Persona D | |
| Accounts and Types |
|
| Transactions |
|
Β Β
One-Time-Passwords (OTP) Requirementsβ
Biza requires personas to be supplied where we can receive a OTP for authentication through the consent and dashboard login flow.
You have two options available to issue the OTP; via SMS or email. To facilitate testing we use an internal Slack channel to receive the OTP for all personas across our entire customer base. You must configure each persona to have either of the following values set as the destination of the OTP issued to that persona, which will then be forwarded to our slack channel.
- Mobile: 0472 881 143
- Email:
otp@biza.io
If you are unable to set up personas with the details above, there is an option to hardcode the OTP to a static value (i.e., it would not change). A valid persona would still be needed for authentication calls, but the OTP for all personas will be the same across the environment. Biza recommends this given the ability to simplify the testing process.
Customers wishing to set up email OTP have the option of creating multiple personas using a single email address (otp@biza.io) by utilising the + symbol e.g., otp+persona1@biza.io.
You will need to set up a mailtrap forward for issuing email OTPs for Biza (please see here for further information).