Skip to main content
Tilta’s sandbox environment is a fully isolated replica of the production system, configured identically so that you can develop and validate your integration end-to-end before going live. Credit bureau calls are simulated (no real risk data is queried), and all payment movements are mocked (no real money is transferred). Everything else – the API contracts, onboarding flows, checkout experience, and event behavior – behaves exactly as it does in production.
Never use real personal data, real business registration details, or real financial information in the sandbox. All test buyers, merchants, and orders must use fictional or clearly test-only data. Tilta may purge sandbox data periodically without notice.

​
Getting access

Sandbox credentials are provisioned by the Tilta team. To request access, contact support@tilta.io with your company name and a brief description of your integration use case. You will receive an API key scoped to the sandbox environment along with login credentials for the sandbox Platform Portal. If you need existing sandbox test data deleted (for example, to reset a buyer’s state), contact support@tilta.io and the team will handle it for you.

​
Environment URLs

Use these URLs during development and testing. Switch to the production URLs only when you are ready to go live with real buyers and real transactions. All API requests to the sandbox are authenticated the same way as production – include your sandbox API key in the Authorization header:

​
Default sandbox behavior

When you create a buyer in the sandbox, Tilta’s simulated underwriting engine automatically approves them with a €8,000 credit facility by default. You do not need to do anything special – simply complete the buyer onboarding flow and the credit facility will be available. Any order you create within a buyer’s available credit facility limit will be approved automatically. This lets you test the happy path without any additional configuration.

​
Test scenarios

Use the special company names and external_id values below to trigger specific underwriting and fraud outcomes. These are the only way to simulate non-default behaviors in the sandbox – all other buyers and orders follow the defaults described above.

​
Buyer credit facility scenarios

Control the approved credit facility amount and rejection outcomes by setting the buyer’s legal name to one of the following values during onboarding:
Use Ultramarathon GmbH when you need to test large orders or scenarios where the buyer’s credit facility must comfortably cover a high-value purchase. Use the rejected names to test how your platform handles a failed onboarding outcome and communicates it to the buyer.

​
Order fraud & risk scenarios

Control order approval and rejection outcomes by setting the order’s external_id to a value that begins with one of the following prefixes:
The prefix match is case-sensitive. For example, order_fraudulent_001 and order_fraudulent_test will both trigger a rejection, but order_Fraudulent_001 will be treated as a normal order and approved.

​
Sandbox limitations

The sandbox is designed for functional and integration testing, not performance or load testing. Keep the following constraints in mind:
Underwriting decisions in the sandbox are entirely simulated using the legal name rules above. The sandbox does not query any real credit bureau or financial data source, so you cannot use it to preview how a specific real business would be underwritten in production.
invoice capture does not trigger actual SEPA transfers in the sandbox. Merchant payout events and buyer repayment reminders are fired as normal webhook events, but no funds change hands. Use this to validate your event-handling logic, not your reconciliation processes.
Tilta may reset or purge sandbox data without prior notice. Do not rely on sandbox data persisting across development sessions. If you need a specific dataset to be removed to re-test an onboarding flow from scratch, contact support@tilta.io.
The sandbox infrastructure is shared and not sized for high-volume load or stress testing. Run any performance testing against a dedicated environment – contact support@tilta.io to discuss options if you require volume testing before launch.