Mock Financial Institutions

Below you will find a list of mock financial institutions that can be used for testing purposes. They are divided in 2 sections:

• API/Open Banking
• Legacy/Screen Scraping

API/Open Banking

This is the list of mock banks that can be used to test api connections that follow the same authentication flow as Open Banking.

---

Moneyhub Open Banking Mock

Bank Id: 1ffe704d39629a929c8e293880fb449a

This mock bank can be used for:

• Creating a new financial connection
• Making payments

Credentials

You can authenticate with the Mock Bank simply by clicking the "Log in as demo user" button. This will log in as our demo user, which has a selection of accounts and transactions set up for testing.

Credentials for test users with customised accounts and transactions may be available on request.

Payments

All payments are always successful unless using the following values for the payment reference:

• INVALID REQUEST : This will cause for the payment to fail on the initial request before redirecting to the bank for user consent.
• INVALID SUBMISSION : This will cause for the payment to fail on payment submission after being redirected back from the bank.

Payment charges

If you wish to try out a payment with charges applied, set the payment reference to INCLUDE CHARGES

Webhooks

This bank can be used to test the following webhooks:

• newTransactions: The initial connection will send this webhook with the new transactions that have just been added.
• paymentCompleted: This webhook is fired after a payment was successful.
• paymentError: This webhook is fired when the payment fails using the INVALID SUBMISSION reference.
• reauthReminder: The reauth reminder can be tested by following the steps below:
  • Create a connection with Open Banking Mock
  • Use the PATCH /users/{userId}/connections/{connectionId} endpoint to update the expiresAt field to a date that is within 5 days. This can currently only be used if the client uses their own consent screens.
  • An alternative to using the PATCH /users/{userId}/connections/{connectionId} endpoint is using the expirationDateTime claim to set the expiry of the connection. This can be used by clients using Moneyhub consent screens. See here for more information about expirationDateTime. Please be advise using expirationDateTime claim will be mean tppConsent is always false. However the reauth process is still testable in this way.
  • If the expiresAt value has been changed to be within the next 5 days then a reauthReminder webhook should be generated on the next scheduled connection sync i.e. within the next 4 hours.

---

Ozone Open Banking Mock

Bank Id: 5233db2a04fe41dd01d3308ea92e8bd7

This mock bank can be used for:

• Creating a new financial connection
• Making payments

Credentials

Webhooks

This bank can be used to test the following webhooks:

• newTransactions: The initial connection will send this webhook with the new transactions that have just been added
• paymentCompleted: This webhook is fired after a payment was successful

Legacy/Screen Scraping

This is the list of mock banks that can be used to test legacy connections that follow the same authentication flow as Screen scraping connections.

📘

Legacy scope required

This type of test connections require the legacy scope enabled for your API client, this scope is not enabled by default and you will need to contact us if you wish to test screen scrapping connections.

---

DAG Legacy Mock

Bank Id: 06995ed5c6c6f25e323b34dc45968426
Name: Dag Site

This bank returns different account types depending on credentials used.

This mock bank can be used for:

• Creating a new financial connection
• Refreshing an existing financial connection

DAG Multi Factor Authentication Legacy Mock

Bank Id: c76bdfeb26e68aae528b0416a96975ba
Name: Dag Site Multilevel

This bank can return cash, savings and credit cards.

MFA is always required when creating a connection. When refreshing a connection MFA is not required if it has been submitted already in the previous 15 minutes.

This mock bank can be used for:

• Creating a new financial connection
• Refreshing an existing financial connection
• Test Multi factor authentication

DAG Site Security QA

Bank Id: 93a35913d9cd588bba5e48bef9e3fe6b
Name: Dag Site SecurityQA

This bank returns different account types depending on the credentials used. This mock bank can be used for:

• Creating a new financial connection
• Refreshing an existing financial connection
• Test security

Security questions:

• What is the name of your state?: Texas
• What is the name of your first school?: w3schools

DAG Savings Legacy Mock

Bank Id: 1b3cd579899b5f5b666c15561a48c8b6
Name: Dag Site

This bank returns savings accounts with transactions

• Creating a new financial connection
• Refreshing an existing financial connection