Start here
Environments
Sandbox
Sandbox is for integration, mobile QA, partner demos, and destructive test cases. It should never move real money. Simulated rails are allowed to return failure states so mobile and backoffice can prove honest unavailable and retry paths.
| Surface | URL |
|---|---|
| API | https://sandbox-heritagepay-api.paypm.net/api/v1 |
| User portal | https://sandbox-heritagepay.paypm.net |
| Backoffice | https://sandbox-heritagepay-backoffice.paypm.net |
Developer documentation
| Surface | URL |
|---|---|
| Developer portal | https://developer.paypm.net |
| API reference | https://developer.paypm.net/api |
| Marketplace architecture | https://developer.paypm.net/marketplace-architecture |
Staging
Staging is for live provider validation and must be treated like a pre-production money environment.
| Surface | URL |
|---|---|
| API | https://staging-heritagepay-api.paypm.net/api/v1 |
| User portal | https://staging-heritagepay.paypm.net |
| Backoffice | https://staging-heritagepay-backoffice.paypm.net |
Rules
- Use sandbox for developer onboarding and automated smoke checks.
- Use staging only when the flow intentionally validates live money movement or provider behavior.
- Never copy secrets into tickets, docs, Git, screenshots, or chat.
- Keep API keys scoped to the environment that issued them.
- Treat staging webhook endpoints as real integration endpoints.
Last modified on