Environments - sandbox vs production
Banks almost always need at least two logical environments: one for safe experimentation and one for live customer traffic. AIS follows that same split, but labels and URLs vary by program.
Typical naming (placeholders)
| Environment | Purpose | Bank expectations |
|---|---|---|
| Sandbox (or UAT / pre-production) | Integration testing, regression, training | Synthetic or masked data; may reset more often; slower SLAs acceptable |
| Production | Live decisions affecting customers | Strict change control, monitoring, and incident escalation |
Your runbook may call these SANDBOX / PROD, UAT / LIVE, or something else-align vocabulary in writing with your AIS project manager.
What AIS usually provides per environment
- Distinct base URLs for the Pro Gateway (and any other agreed HTTP entry points).
- Separate credentials (accounts, API keys, certificates). Never reuse production secrets in sandbox.
- Data isolation: sandbox databases and object stores are not copies of production for privacy reasons unless a controlled migration is explicitly approved.
Certificate and network edges
Many banks terminate TLS on their own reverse proxy or API gateway, then forward to AIS. mTLS, private link, and IP allow lists are common-document the final hop your packets take and who owns certificates at each layer.
:::caution Contract is source of truth
SLAs, maintenance windows, and whether a permanent sandbox exists are contractual. This portal uses generic framing only.
:::
Next: Reliability, limits & webhooks · Back: Overview