Deployment Model
Environments, multi-tenancy, and infrastructure topology for the M2P Prepaid Platform.
The M2P Prepaid Platform is deployed as a multi-tenant SaaS platform where each issuer or partner operates as an isolated tenant with dedicated configuration, data isolation, and independent webhook endpoints.
Environments
Sandbox
Development & Testing
Use the Sandbox environment for initial integration development and functional testing with test cards and simulated bank responses.
https://sandbox-api.m2p.com
UAT
Pre-Production Validation
The UAT environment mirrors production configurations and is used for end-to-end certification testing before go-live.
https://uat-api.m2p.com
Production
Live Traffic
The production environment handles real transactions with live card networks and bank partners.
https://api.m2p.com
Multi-Tenancy Model
Each tenant is fully isolated with its own configuration scope:
Tenant Isolation Guarantees
| Aspect | Isolation Level |
|---|---|
| Customer Data | Encrypted at rest with tenant-scoped access controls |
| Configuration | Independent BIN ranges, limits, fees, and templates |
| Bank Routing | Configurable bank partner per tenant |
| Webhooks | Dedicated endpoint URLs per tenant |
| API Credentials | Unique JWT credentials per tenant |
| Notifications | Independent templates and channel configurations |
Every API call requires the TENANT header to identify which tenant context the request belongs to. This header is validated against the JWT token to prevent cross-tenant access.