Skip to main content
Fluz runs two fully separate environments. Knowing which one you’re in, and that nothing crosses between them, avoids most first-run authentication problems.

​
Staging environment

The Fluz staging environment lets you explore the platform’s features. Use it to experiment, build integrations, and train your team.
Purpose: Staging mirrors the capabilities and transactions of the live environment, but without real money. Use it to test your integration thoroughly before moving to production. Data usage: Only use dummy or test data in staging, created explicitly for testing. It must not include production data such as customer details, financial data, or personally identifiable information (PII). See the sandbox test data pages.

​
Production environment

The live environment is where real transactions occur, and actions are final. To protect your business data, don’t use this environment for testing. Production data includes sensitive information such as customer details, financial data, and PII.
Purpose: The live environment is where you make purchases, earn cashback, and manage your account. Everything here uses real data and has real-world consequences. Data usage: Only use real, verified data in the live environment. Actions here affect your actual account and can’t be undone.

​
What’s separate between them

Staging and live don’t share anything. Each has its own:
  • users and logins — sign up separately in each;
  • accounts — personal and business accounts, balances, cards and transactions;
  • applications and API keys — a key from one environment is unknown to the other;
  • OAuth grants and webhook configuration.
An application created while logged in to fluz.app is a live application, even if you only mean to test with it. Create test applications at uni.staging.fluzapp.com. From the live dashboard you can reach staging under Resources → Open Staging.
A live key sent to the staging endpoint (or the reverse) fails with 401 Error verifying API basic token. See API credentials. Application activation and restricted capabilities, such as registerUser and VERIFY_KYC, are granted per application. That means separately in each environment. See How accounts work.

​
Funding a staging wallet

A new staging account has a zero balance, so card issuing and gift card purchases fail until you add funds.
1

Find the spend account

Call getUserCashBalances and take the userCashBalanceId of the spend account you want to fund. getWallet.cashBalance may only reflect the default spend account.
2

Ask Fluz to seed it

Send your staging account ID, the userCashBalanceId, and the amount to your Fluz contact. This is the reliable way to fund staging today.
3

Or deposit from a test funding source

Deposit from a test bank card or test bank account, passing the userCashBalanceId from step 1.

​
Moving from staging to live

Before you switch, test every flow thoroughly in staging and resolve any bugs. Then:
  1. sign up (or log in) at fluz.app;
  2. recreate your application there, from the same template, and ask Fluz to activate it and enable the same capabilities;
  3. swap in the live API key, OAuth client credentials, and endpoint;
  4. re-register webhooks and redirect URIs.
The full checklist is in Deploying to Production.

​
Next steps

Prepare your accounts

Sign up in staging and create the right type of application.

Idempotency

Safely retry money-moving mutations without creating duplicates, in either environment.