> ## Documentation Index
> Fetch the complete documentation index at: https://developer.pagou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments

> Choose the correct base URL, credentials, and release discipline for sandbox and production.

Use the same integration code in both environments. Change configuration, not behavior.

## Base URLs

| Environment | Base URL                       | Use it for                                                  |
| ----------- | ------------------------------ | ----------------------------------------------------------- |
| Sandbox     | `https://api.sandbox.pagou.ai` | local development, automated tests, staging verification    |
| Production  | `https://api.pagou.ai`         | live traffic, production reconciliation, operator workflows |

## Rules

* Keep sandbox and production tokens separate.
* Use different webhook endpoints for sandbox and production.
* Never expose production credentials in browser code.
* Roll out by switching config only: token, base URL, webhook target, and monitoring.

## Why this matters

Environment drift is a common source of launch bugs. If your request shapes are identical in both environments, production cutover becomes an operational change instead of a code deploy risk.

## Release checklist

1. Validate auth against sandbox.
2. Run a full happy path with Pix, voucher, or card.
3. Confirm webhook delivery, deduplication, and reconciliation.
4. Verify logs capture `requestId`, resource IDs, and your `external_ref`.
5. Switch only credentials and base URL at go-live.

## Next steps

* [Authentication](/start-here/authentication)
* [Go-live Checklist](/start-here/go-live-checklist)