Sandbox does not bill you. Credits, payments, refunds and usage charges shown in Sandbox are simulations. They do not charge a card, debit a bank account, create a real amount owed or change your Live balance.
What you can test
- Submit application information and documents, then inspect an Origination and its risk package.
- Read normalized source data, consent records, connections and supporting evidence.
- Exercise within-policy, outside-policy, review-required and incomplete underwriting outcomes.
- Follow monitoring alerts, recoveries and signed webhook deliveries.
- Inspect request logs, exports, simulated funding and consumption records.
- Build recovery handling for invalid requests, retries, duplicate events and insufficient test credits.
Sandbox and Live compared
A completed scenario is not a lending approval. It means the test produced its expected outcome, which can include a declined payment, an outside-policy assessment or a failed provider. Your institution makes lending decisions; sample risk packages and verification observations are fictional.
Keep testing separate from operations
Use fictional or anonymized test information. Keep API keys on your server and verify the environment in responses and events. Sandbox keys cannot access Live resources, and generated IDs, connection sessions and cursors must not be reused in Live. Loading samples or switching environments does not move data between them. The scenarios help you verify behavior and data handling. They do not reproduce every provider response, establish production throughput or guarantee real-world provider timing. Before Live use, verify your authorized provider connections, webhook receiver, credentials and agreed operating limits separately.Get started
Choose your starting data
See the first-use setup screen and choose samples or an empty workspace.
Explore businesses and scenarios
Find the six sample businesses and run the outcomes your product needs to handle.
Understand simulated billing
Reconcile funding and usage without moving real money.
Automate your tests
Use API examples, the scenario catalog and a runnable client.