Test Bank Documentation

In order to test the integration a test bank is available in the playground environment. To access the test bank the sort code 88888888 has to be entered when selecting a bank.

When it comes to testing the integration it is very useful to cover different scenarios. Entering the following values as a password instructs the underlying systems to execute different scenarios that can happen at different banks:

Password Functionality
slow will pretend that the answers from that bank will take several seconds, e.g. at least 5 seconds per request towards the bank
wrong will pretend that the credentials were wrong and a login to the bank was denied
complete will present a second challenge so the consumer has to enter something additional
no-sendtan will pretend that there is no authorization needed to do a transfer
one-account will only return one account instead of a whole list of accounts
one-account-no-trans will only return one account that does not have the possibility to do transfers instead of a whole list of accounts
no-account will return no accounts

If "complete" is used as a password in the first step there is also the possibility to enter specific passwords for the next step to test even further:

Password Functionality
next will pretend to require another step for the authentication

Also for the authorization-step there are some special keywords to create specific behaviors:

Password Functionality
next will pretend to require another step for the authorization
wrong will pretend that the authorization-data was entered wrong
remit-denied will pretent that the bank rejects the transfer for some reason
slow will pretend that the answer from the bank takes at least 10 seconds
xslow will pretend that the answer from the bank takes at least 90 seconds

results matching ""

    No results matching ""