Testing

Trustly provides a Sandbox environment for development and testing. The Sandbox environment supports all features and functionality of the production environment, but payment operations do not result in any funds activity.

The primary method for simulating scenarios is through Demo Banks accessible within the Trustly UI, using specific passwords to trigger desired outcomes.

Environment URLs

When deploying your application or libraries, ensure you use the correct base URL and authentication credentials for each environment.

Sandbox usage and best practices

To access a Demo Bank, integrate the Trustly UI (Lightbox or Widget) into your application and use the search bar to select the desired Demo Bank.

General guidelines

• Default Behavior (Happy Path): By default, any unique string used as a username and three or more alphanumeric characters used as a password will simulate a successful transaction, allowing the selection of a standard checking or savings account.
• Use Unique Usernames: Avoid using generic usernames (for example, test, demo). Use unique, descriptive names for each test scenario (for example, happy_path_test_01, ineligible_user) to ensure the fastest and most reliable sandbox response.
• Simulating Delays: To simulate a delay, enter Sleep as the username and the number of seconds (for example, 30) as the password.

Extended Decline Code Testing

To simulate specific fraud or velocity check declines (which map to extended reason codes), use the special password pattern in the Demo Bank.

1. Create an authorization using a Demo Bank. Use the following credentials:

• Username: <"anyusername">
• Password: Use extendedreasoncode_ followed by the code you wish to trigger (for example, extendedreasoncode_10000).

2. Create a capture referring to the previously created authorization.

The transaction is expected to be denied by the Response Codes associated with the extended reason code provided in the password.

3. The decline or fail notification should present the following attributes, among others:

• paymentProviderTransaction.status: SW054
• paymentProviderTransaction.reasonCode: 1
• paymentProviderTransaction.extendedReason.code: 10000

Simulation keyphrases

To manipulate the outcome of the bank authorization or the associated data, enter the corresponding keyword or phrase into the password field when logging into the Demo Bank.

User interaction and error scenarios

Conditional data and API responses

Manual entry and verification data

This data should be used when testing manual entry fields for micro-challenge deposits or manual account verification requests.

United States manual entry test data

The following are samples of Account Number and Routing Number pairs that simulate various risk scores (all routing numbers are 124003116):

International manual entry test data

Mobile OAuth testing

To test deep linking and user experience for native mobile apps, use the specialized OAuth Demo Bank.

1. Access the OAuth Demo Bank via the Trustly UI search bar in your application.
2. Download the Companion App:
   • iOS: Use the iOS TestFlight download.
   • Android: Email amer.developer.experience@trustly.com with the subject “Android Demo Bank App” to request access for the email addresses that need to be invited.
3. Testing Flow: When selecting the OAuth Demo Bank, the system will trigger a redirect that opens the companion app on the device or simulator, allowing you to proceed with the authenticated login flow.