Testing
Using Demo Banks to create test scenarios
Trustly offers a Demo Bank and an OAuth Demo Bank in the Sandbox environment that can be used to trigger a number of testing scenarios. To access the Demo Bank, search for "Demo Bank" in the "Select your bank" view of the Trustly Lightbox. To simulate errors when using the Demo Bank, you can use the phrases below in the password field to generate errors.

Password | Use Case |
---|---|
NoEligibleAccounts | No eligible accounts found |
LoginError | Wrong username or password |
Unavailable | Bank Site cannot be reached. |
AccountLocked | User’s account is locked. |
BankAction | The bank requires the user to login and perform some action on their site. |
ConnectError | There was a connection problem when accessing bank site |
ConnectionError | There was a connection problem when accessing bank site |
BlockedIpError | The bank indicates the caller IP was blocked |
ChallengeError | Simulates retry scenario, where the user provide wrong challenge (or anything that isn't userid or password) and is allowed to retry |
ValidRouteCodeExtra | Connector returns 2 accounts whose route codes are larger than 9 digits: one of them has a valid route code as substring, so both accounts use the same valid code |
InvalidRouteCodeExtra | Connector returns a single account whose route code is larger than 9 digits, but no valid route code is found as substring. Hence, the account is ignored |
TimeoutError | In order to simulate a timeout, connector sleeps for at least a minute before actually doing anything. |
TestPrompts | This is not an error. This is to test the prompts on next page, including (Checkbox, radio, text, password, date, description and so on) |
NotEnoughFunds | Connector returns a single account with zero balance. This is similar to having no eligible accounts, but with different reason. |
NotEnoughFundsExtra | Connector returns two accounts. One with zero balance, the other with a valid balance. |
InvalidAccountNumberSize | Connector returns a single account, but with account number shorter than the required. This is to test how the screen filters invalid accounts |
InvalidAccountNumberSizeExtra | Connector returns two accounts. One with account number shorter (3 characters) than the required, the other with valid account number. |
PartialAccountNumbers | Connector returns two accounts, however only with partial numbers. Simulating when for example the account is new and we still don't have statements to get full account number. |
OnlyPartials | PartialAccountNumbers + NoRouteCode |
NoCustomer | Simulates as if FIC was not able to retrieve customer information |
NoRouteCode | Regular flow with 2 accounts, but none with route code. This prompts a question for account location, where user must select where the account was open (from the given options) |
InvalidRouteCode | Regular flow but simulates an invalid routing code (will simulate if ProfitStars returns invalid routing code) |
2FA | Simulates as the bank requested a challenge question to the user. The question should be answered with the word 'error' if it's necessary to simulate a wrong credential. Otherwise, it should be anything to have a successful access. |
WrongCredentials | Simulates retry scenario, where the user provide wrong challenge (or anything that isn't userid or password) and is allowed to retry |
SiteRequestError | Simulates as if the bank couldn't process a particular request, allowing user to retry it |
SessionTimeout | Simulates as if the user took too long to provide the requested information, since the bank session is already expired |
PreLoginError | Simulates an error before the user gets authenticated |
NotSupported | Simulates an user with no supported accounts |
AccountsWithNameAndAddress | Simulates an User with 2 accounts and each one with different names and addresses. |
ManyInformation | Simulates an User with until 10 accounts. |
AccountNotSupported | Simulates an User with an account not supported by our service (Chase Liquid, etc) |
AmountNull | Simulates the Demo Checking Account returning an amount with null value. |
AccNumberNull | Simulates the Demo Checking Account returning null value in the account number and routing number |
AccFromUsername | Returns the account number from the pattern {prefix}_{accountnumber} on the username. Ex: To return an account with number 1234445 you can enter the username user1_1234445 or anotheruser_1234445. |
RandomBalance | Returns account with random balance |
RandomAccounts | Returns an account with random account number |
LargeCustomerInfo | Returns account with very large customer information |
FICWarning | It simply add to log engine fic-warning one example message to simulate the FIC Warning flow |
EmailMFA | Simulates as the bank requested the user to select an email address to send him a MFA token. |
MixedMFA | Simulates as the bank requested the user to select an email address or a phone number to send him a MFA token. |
CreditCardsOnly | Returns an account only with credit card |
TCKAccounts | Returns an account that is valid on TeleCheck test environment |
AccountProfile | Returns accounts with Business, Personal, Other, Unknown and Null profiles. |
Balance{xxx} | Configures the account to have a balance of {xxx}. For example, Balance1000 will set the account balance to $1000. This is useful when testing transactions of larger dollar amounts. |
RandomAccWithSleep | Returns random accounts with random account numbers and sleeps (in seconds) during the number passed in the password field |
ExpiredSplitToken | Allows the transaction to be authorized but every refresh API call fails because of an expired split token. |
NotEnoughFundsOnRefresh | Allows the transaction to be authorized but every refresh API call returns 0.00 as balance for all accounts. |
Virtual | Return a valid Virtual Account Number (VAN) |
To simulate a delay, just enter Sleep
as username and the number of seconds as the password, The connector will wait for at least the given number of seconds before presenting any results.
Updated 4 months ago