Aerosync Test Banks

The production environment contains thousands of banks that a user can connect with, but in the sandbox environment we provide Aerosync branded banks to develop and test against.

There are 3 separate Aerosync test banks which simulate different bank connection experiences: MFA, OAuth, and Security Question. It is important to test with all 3 bank types to ensure you're accounting for all test cases. Keep in mind, if you're integrating Aeropay in a mobile application, you'll need to use a deeplink to correctly handle the OAuth bank flow.

Aerosync Bank	Information	Credentials
Aerosync Bank (MFA)	This test bank will mimic the flow of logging into a financial institution and triggers an MFA (multi-factor authentication)	Any string can be used for the login credentials and the MFA code
Aerosync Bank (OAuth)	Some live banks will connect a user via OAuth - in these cases, an external window will open where a user will log in directly on the bank's website. This test bank will mimic that flow	Any string can be used for the login credentials
Aerosync Bank (Security Question)	This bank mimics the flow of a financial institution that requires the answer to a security question. For example, "What's your favorite color?"	Any string can be used for the login credentials and the security question answer

Linking a bank account to Aeropay

If integrating Aeropay via API, a request to Aeropay's POST /linkAccountFromAggregator endpoint will be necessary to link the bank account to Aeropay. The onSuccess() event data attributes from the Aerosync widget will include a user_id and user_password - these should be included in the payload to this endpoint.