Environments
Production and sandbox base URLs, keys, and what sandbox does not do.
Environments
Sandbox and production are fully separate: different base URLs, different keys, and separate data.
Showing gateways for this deploy (Staging docs). Keys still use sk_live_ / sk_test_ against the matching base URL.
| Environment | Base URL | Key prefix |
|---|---|---|
| Production | https://stggateway.momen.co/v1 | sk_live_ |
| Sandbox | https://stggateway-sandbox.momen.co/v1 | sk_test_ |
Sandbox behavior
- Never moves real money.
- Never contacts a bank or payment provider.
- Checkout pages cannot be opened yet.
- Use
POST /sandbox/simulateto drivepaid,failed, orexpiredoutcomes and the matching webhooks.
Docs deploy (staging vs production)
This documentation site is built once per host. Set:
# Production docs → gateway.momen.co / gateway-sandbox.momen.co
NEXT_PUBLIC_IS_PRODUCTION=true
# Staging docs → stggateway.momen.co / stggateway-sandbox.momen.co
NEXT_PUBLIC_IS_PRODUCTION=falseOptional overrides (win over the flag):
NEXT_PUBLIC_LIVE_API_URL=https://stggateway.momen.co/v1
NEXT_PUBLIC_SANDBOX_API_URL=https://stggateway-sandbox.momen.co/v1The try-it console always uses the sandbox URL for this deploy and refuses non-sk_test_ keys.