Environments
Sandbox and production share endpoints, contracts and data model. Start in sandbox at no cost and migrate to production when you're ready, the same code works in both.
Quick comparison
| Sandbox | Production | |
|---|---|---|
| Cost | Free | Per agreed pricing |
| PSD2 transactions | Against real banks, max €1 per payment | No amount limit |
| Capacity | Reduced (test environment) | High availability |
| Functionality | Identical across both environments | Identical across both environments |
| Portability | Same endpoints, contracts and model | Same endpoints, contracts and model |
Amounts in sandbox
PSD2 calls run against the production environments of the banking institutions, so payment initiations in sandbox are capped at €1 to minimize impact during your tests.
Sandbox
For development and integration, at no cost.
Full functionality, same endpoints
Sandbox faithfully replicates production: it offers the same functionality and uses the same endpoints, so the code you develop is directly portable without modifications.
PSD2 transactions
PSD2 calls run against the banking institutions' production environments. For payment initiations, the maximum allowed amount is €1, to minimize impact during testing.
Capacity and infrastructure
The sandbox environment has lower infrastructure resources than production. If you hit performance or availability limits during testing, keep in mind that production has greater capacity.
Endpoints
| Service | URL |
|---|---|
| Base URL | https://nc-api-sandbox.zertiban.com |
| Token | https://nc-api-sandbox.zertiban.com/idp/oauth2/token |
| Flows | https://nc-api-sandbox.zertiban.com/flow/v1/flows |
Production
For real traffic, with high availability and performance.
High availability and performance
This environment is sized to guarantee high availability and performance, with greater compute capacity and redundancy.
Costs per agreed pricing
Operations in production are billed according to the pricing agreed in your contract.
Endpoints
| Service | URL |
|---|---|
| Base URL | https://nc-api.zertiban.com |
| Token | https://nc-api.zertiban.com/idp/oauth2/token |
| Flows | https://nc-api.zertiban.com/flow/v1/flows |
Open the production dashboard →
Same path, different host
Only the host changes. The rest of the path is identical: if your integration hits /flow/v1/flows in sandbox, it will hit the same path in production.
Migration to production
Once your integration is finalized and validated in sandbox, follow these steps:
- Validate the integration in sandbox. Make sure your flows cover every operation state (COMPLETED, REJECTED, EXPIRED, CANCELLED) and that you verify the webhook HMAC signature.
- Request production credentials. Contact [email protected] and we'll coordinate the migration: registering the creditor IBAN, issuing
clientId/clientSecretand registering your webhook endpoint. - Switch the environment variables. Replace
ZERTIBAN_BASE_URL,ZERTIBAN_CLIENT_ID,ZERTIBAN_CLIENT_SECRETandZERTIBAN_WEBHOOK_SECRETwith the production values. Deploy. - Go-live. We coordinate the date with you and support you through launch.
Ready to go to production?
Once your integration is finalized and validated in sandbox, contact [email protected] to coordinate the migration and define the go-live date.