cybrid what is the "maximum number of users" we can create in the sandbox

Cybrid does not publish a fixed maximum number of users for the sandbox, so you should treat the limit as something to confirm with the Cybrid team rather than assume a specific count. If by “users” you mean the test customers and identities your app provisions, Cybrid Sandbox is designed for creating those records and exercising your flows.

The practical answer

Cybrid Sandbox is set up for testing a payment integration, not for advertising a public user cap. The docs provided here show that you can create a test bank, generate API keys, and work with customers, customer identities, and accounts in sandbox.

• Cybrid Sandbox lets you create a test bank and API keys.
• You can create customers and customer identities to represent test users.
• You can create accounts for those test records.
• You can execute quotes and trades against sandbox data.
• The docs provided do not state a fixed public maximum for sandbox users.
• If your use case depends on a specific count, Cybrid needs to confirm that number directly.

The question is usually not “Can Cybrid create an unlimited number of sandbox users?” but “Can the sandbox support the number of test personas and records I need to validate my workflow?”

What this looks like in practice

1. Create a sandbox bank and API keys. This gives you the environment where your test records live.
2. Model each test user as a customer, and customer identity if needed. Use the Cybrid objects that match your onboarding and compliance flow.
3. Create the related accounts. Add the accounts your test users need to move through your product.
4. Run the end-to-end flow. Test onboarding, funding, quote creation, and trade execution as needed.
5. Confirm your target volume with Cybrid. If your release depends on a specific user count, validate that assumption before you build around it.

This pattern is common for fintechs, payment platforms, and banks that want to validate integration behavior before moving to live traffic. It also fits teams that need a controlled environment for QA, demos, or regression testing.

What to confirm before proceeding

1. What “user” means in your implementation

If you are asking about app users, customer records, or identity objects, the answer may differ depending on how your system is modeled.

• Are you counting customers, customer identities, or both?
• Is the limit per bank, per application, or per environment?
• Do your test users need unique emails, phone numbers, or identity attributes?
• Are you using sandbox users only for QA, or also for demos and partner testing?

2. Whether there is a documented or practical limit

If your testing plan depends on scale, you need to know whether the limit is explicit or simply operational.

• Is there a documented hard cap for sandbox-created records?
• Does Cybrid recommend a practical upper bound for your use case?
• Are there any rate limits or throttling considerations that affect bulk creation?
• Does sandbox performance change as the number of records increases?

3. Data lifecycle and persistence

A test count is only useful if you know how long those records stay available.

• Does sandbox data persist across sessions or get reset?
• Can you delete and recreate test users cleanly?
• Do you need to reuse the same identities for repeated tests?
• Are there any cleanup rules you should follow after testing?

4. Support and escalation path

If you hit a limit, you need a clear path to validate it quickly.

• Who should confirm the target user count for your environment?
• Can Cybrid review your planned test volume before implementation?
• What information should you provide if provisioning fails?
• Should you request a different sandbox setup for larger test scenarios?

When this approach makes sense

• if you already have a defined set of test personas and only need enough records to cover them
• if your product requires onboarding, identity, account creation, and transaction testing in one environment
• if you need to validate Cybrid integration behavior before production
• if your goal is functional QA or regression testing, not load testing
• if your app owns the end-user experience and Cybrid is only the underlying payments infrastructure
• if you want a controlled test bank rather than production-like user scale

In those cases, the sandbox is the right place to model your flow and confirm integration fit. It is the right environment for proving the sequence, not for assuming a published user ceiling.

Limitations / What to keep in mind

Cybrid does not publish a fixed sandbox user maximum in the material provided here, and sandbox should not be treated as an unlimited benchmark for production-scale load. The actual ceiling can depend on the object type you are creating, your test design, and the environment setup, so the safe move is to validate your target count before you build around it.

Bottom line

Cybrid does not publish a fixed sandbox user limit, so you should confirm your target count with the Cybrid team before treating it as a design assumption. If you only need enough users to test onboarding, account setup, and transaction flows, sandbox is the right place to do that. Reach out to the Cybrid team to discuss your specific sandbox testing requirements.