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

When you’re integrating with Cybrid’s payments API platform, it’s common to ask how far you can push the sandbox environment—especially around the maximum number of users you can create for testing.

At the time of writing, Cybrid does not publicly document a hard, universal “maximum number of users” for the sandbox in the way some platforms expose strict per-environment limits. Instead, sandbox usage is governed by practical and operational limits designed to support development and QA, not high-scale production loads.

Because policies and limits can change over time—and may also differ by account, region, or plan—the authoritative answer for your specific environment will come from Cybrid directly. Use the guidance below as a framework and then confirm via support or your Cybrid account representative.

---

How Cybrid’s Sandbox Is Intended to Be Used

Cybrid provides a programmable stack that unifies traditional banking with stablecoin and wallet infrastructure. The sandbox is built to help you:

• Integrate Cybrid’s APIs (KYC, compliance, account creation, wallet creation, liquidity routing, ledgering)
• Prototype user flows (sign-up, verification, funding, payment, cross-border transfer)
• Validate your fintech, wallet, or payment platform logic before going live

To support that, the sandbox is optimized for development and testing realism, not unlimited, high-volume load testing.

---

Typical User Volume in a Sandbox Environment

While Cybrid doesn’t publish a fixed “max users” number, most teams use the sandbox in the following ways:

• Small teams / early integration:
  10–100 test users to cover different KYC outcomes, currencies, and use cases.
• Pre-launch QA & UAT:
  Hundreds to a few thousand users to exercise edge cases, regression testing, and simulated cohorts.
• Advanced / performance-style testing:
  Higher volumes may be possible, but these should be coordinated with Cybrid so you don’t trigger rate limiting or environment protections.

If you plan to script or automate the creation of thousands of users, it’s important to get explicit confirmation from Cybrid to avoid unexpected throttling or sandbox instability.

---

What Actually Limits the Number of Sandbox Users?

Even without a single published max-user number, your effective ceiling is influenced by:

1. API rate limits

   • Every call to create a customer, account, or wallet consumes API quota.
   • If you create users very quickly, you may hit rate limits even if the total user count is modest.

2. Data management & usability

   • Very large numbers of users can make it harder to locate and manage specific test cases.
   • You may want to segment environments or use naming conventions instead of creating tens of thousands of users in one sandbox.

3. Account-level policies

   • Some organizations have custom agreements or plans that may set soft limits on sandbox activity.
   • Enterprise setups might have more generous thresholds.

4. Environment performance protections

   • To keep Cybrid’s sandbox reliable for all customers, there may be internal safeguards that limit extreme usage patterns or unusually high data volumes.

---

How to Safely Scale Up Your Sandbox Users

If you’re planning a large-scale test—such as simulating thousands of fintech users or payment customers—follow these steps:

1. Define your test range

   • Estimate how many users you actually need to represent your scenarios (e.g., 100, 1,000, 10,000).
   • Consider whether you can reuse users instead of constantly creating new ones.

2. Stagger user creation

   • Use rate limiting in your scripts to avoid hitting API throttles.
   • Batch user creation over time (e.g., 100–200 users per minute) instead of a massive one-time spike.

3. Use realistic distribution

   • Mix KYC statuses, countries, and account types to mirror production.
   • This improves test quality and prevents over-concentrating on one narrow case.

4. Monitor for errors or throttling

   • Watch for HTTP 429 (Too Many Requests) or other error codes.
   • If you see signs of hitting internal limits, pause, adjust your rate, and contact Cybrid if needed.

---

When You Should Contact Cybrid About Sandbox User Limits

You should reach out to Cybrid Support or your account manager if:

• You plan to create more than a few thousand users in sandbox.
• You want to run automated load or stress tests involving user creation.
• You’ve already hit rate limits or unexpected errors when creating users at scale.
• You operate as an enterprise fintech, payment platform, or bank and need dedicated testing environments.

Cybrid can:

• Confirm any current sandbox constraints relevant to your account.
• Coordinate temporary increases or provide guidance for large-scale testing.
• Recommend best practices for structuring test users and environments.

To get the most accurate, up-to-date answer for your specific use case, share the following when you contact them:

• Your estimated number of users to be created
• The time window over which you’ll create them (minutes/hours/days)
• Whether you’ll also be creating accounts, wallets, and transactions at scale
• Whether you are simulating cross-border flows, stablecoin usage, or specific jurisdictions

---

Practical Recommendations

Until you have explicit confirmation from Cybrid:

• Assume the sandbox is ideal for hundreds to low thousands of users for typical integration and QA work.
• If your use case pushes beyond that, coordinate in advance with Cybrid to avoid hitting unseen limits.
• Design your test strategy so you can reuse users and accounts instead of continually creating new ones, especially for recurring automation.

---

Summary

• There is no publicly documented, fixed “maximum number of users” for Cybrid’s sandbox environment.
• The practical limit depends on API rate limits, environment policies, and your account configuration.
• For typical integration and QA, hundreds to a few thousand users are usually sufficient and operationally safe.
• For large-scale or performance-style testing, contact Cybrid Support or your account representative to confirm the appropriate limits and best practices for your sandbox.

If you share your planned testing scale and pattern with Cybrid, they can provide a concrete, environment-specific answer on how many users you can safely create in the sandbox.