StatusTR
Getting StartedPayment OrchestratorWalletBank AccountsInsuranceFraud & Fraud AIIdentitySanctionAutomationSDKDemo
Bank Accounts
Test Environment

Test Environment

The test environment uses the same endpoints, the same fields and the same webhook event as live. The difference is that the connection goes to a simulator bank, not a real bank; no real account data is read.

There is one base URL; your key determines the environment. With your test key (mk_test_…) you send requests to the same https://api-gateway.lunixi.com/api/v1/bank-connect address; there is no separate test address. → Test Environment (general)

Trying it end to end

Connect a simulator bank in the test environment

In the panel, set the Environment selector to Test and connect one of the simulator banks listed on Banka Bağlantıları › Bankalar with Connect with Lunixi. Only simulator banks are listed in the test environment. → Connect a Bank in the Panel

Grant your test key access

Add the Bank Connections product (BANK_CONNECT) and the bank-connect:view and bank-connect:transactions:view permissions to your test key. → API Introduction › Permissions

Read accounts and transactions

Once the connection is ACTIVE, call the Accounts, Balances and Transactions endpoints with your test key. The simulator bank provides sample accounts and past transactions.

Create a webhook endpoint

Create an endpoint with productCode: BANK_CONNECT, environment: TEST and eventTypes: ["bank_account.*"]. → Webhook Events › Subscription

Wait for new transactions

The simulator bank produces new sample transactions during the day. They are found in regular reads, so a bank_account.transaction.received event arrives for each one. No event arrives for the past transactions read when the connection is first set up; this is the same as live.

Simulator data

  • Accounts, IBANs and transactions are not real.
  • The accounts and past transactions of the same connection come back the same on every read; your tests are repeatable.
  • To let you test your integration, the simulator also produces cases seen in real life: a bank reporting a transaction late, the same transaction arriving from the bank again, and a transaction that cannot be mapped to one of the common types (OTHER). Test your sync and deduplication logic with these cases. → Keeping transactions in sync

Test and live data never mix. A test key does not see live connections; a live key does not see test connections. A connection you set up in the test environment is not carried over to live.

Going live

  1. In the panel, set the Environment selector to Live and connect your bank in the live environment; the application and setup steps are done separately for live.
  2. Give your live API key the same product and permissions.
  3. Create your webhook endpoint separately with environment: LIVE.
  4. Only the key changes in your code; the base URL and calls stay the same.
LimitsFAQ