Using Invunion guide

Connect a test bank in sandbox

In a sandbox tenant, add a bank connection, choose SI (Slovenia), select Personal, and connect to Mock ASPSP. After simulated authorization, Invunion creates the test connection and immediately syncs the account’s available transactions from the last 90 days. Business test accounts may contain no sample transactions.

Browse documentation

Use the Mock ASPSP connection to evaluate bank synchronization without connecting a real account. Invunion uses Enable Banking for this test flow. New tenants default to sandbox mode and therefore receive the sandbox institution list.

The placement and wording of controls can change, but the required sandbox selections remain SI, Personal, and Mock ASPSP for the verified sample-transaction path.

Prerequisites

  • Access to an Invunion sandbox tenant.
  • Permission to manage connected internal bank accounts.
  • A browser that allows navigation to the provider authorization page and back to Invunion.
  • No real online-banking credentials. The test flow uses simulated authorization.

If the dialog reports production mode, do not proceed under the assumption that Mock ASPSP will be available. Tenant mode determines which Enable Banking environment and credentials the connection uses.

Steps

  1. Open the connection area. From the dashboard, locate Connected internal bank accounts. Select Add. If no connection exists, you can also use Connect my bank.

  2. Verify the sandbox notice. The dialog should say that test institutions are shown and should mention Mock ASPSP. This confirms that the current tenant is using sandbox mode.

  3. Set the country to SI. In Bank country, choose SI: Slovenia. The product may display the country name rather than the code, but the selected market must be SI.

  4. Set the account type to Personal. Choose Personal, not Business. The Enable Banking Mock ASPSP returns different test accounts depending on this selection. Personal exposes the sample current account and sample transactions; the Business default can expose only a card account with no transactions.

  5. Open the test bank picker. Select the button that continues to bank selection. The list is supplied for the chosen sandbox country and user type.

  6. Choose Mock ASPSP. Select the test institution named Mock ASPSP. Invunion starts an Enable Banking authorization and redirects your browser.

  7. Complete simulated consent. Follow the Mock ASPSP prompts. Do not enter credentials belonging to a real bank account. When authorization completes, the provider redirects you to Invunion.

  8. Confirm the callback succeeded. The dashboard should show a successful connection message and an active banking connection. The discovered account is listed beneath the connection.

  9. Wait for the initial synchronization. Immediately after the account is created, Invunion requests the available transactions for the last 90 days. Open Transactions to confirm that the sample entries are present.

  10. Record the visible sync state. On the connection card, note the status and account’s last-sync timestamp. These details are useful if you later need to diagnose a connection or sync issue.

Expected result

The dashboard shows an active Enable Banking test connection with a Mock ASPSP account. The Transactions page contains the sample transactions made available by the Personal test account. The initial request covers the last 90 days; it does not manufacture one transaction for each day or guarantee a particular count beyond the provider’s current test data.

Edge cases and troubleshooting

  • Mock ASPSP is not listed: verify that the tenant is in sandbox mode, the country is SI, and the picker finished loading. If the tenant is marked production, contact an administrator rather than trying test options repeatedly.
  • Authorization returns an error: restart from Invunion instead of reusing an old provider page. Capture the displayed error text before retrying.
  • Connection is active but there are no transactions: the most common sandbox cause is selecting Business. Disconnect the test connection, reconnect, and explicitly choose Personal.
  • The account appears but sync fails: use the sync icon only while the connection status is active. If it still fails, gather the connection status, account label, last-sync time, and the time of the attempt.
  • Repeated sync creates concern about duplicates: imported banking transactions are deduplicated by their source identity. Re-syncing the same provider records should skip existing entries rather than create new copies.
  • The browser does not return to Invunion: return to the dashboard and inspect the connection list. If no active connection exists, start a fresh flow; do not assume authorization completed.

Security and sandbox notes

Mock ASPSP is a test institution. Its balances, account names, and transactions are synthetic. Keep real credentials and unnecessary customer data out of the sandbox. A sandbox connection demonstrates the product workflow only; it is not a claim that production banking is available or that any named real institution is supported.

The connection is scoped to the current tenant. Removing it stops future synchronization but retains transactions already imported. This preservation prevents bank-history records from disappearing simply because a connection is replaced.

Next step

Open Import issued invoices to add records that can be compared with the sample incoming payments, then follow Complete your first reconciliation.

Updated

Was this article helpful?

Feedback helps us improve the next version of this guide.

Tell us what is missing