Implementation Guide
Everything you need to configure and launch your prepaid card program on the M2P Platform.
This guide walks you through everything needed to configure and launch your prepaid card program — from tenant setup through notification templates.
Prerequisites
Before starting implementation, ensure you have the following from your M2P onboarding package:
Tenant Credentials
A unique TENANT identifier and API credentials for authentication.
JWT Credentials
Username and password for obtaining JWT tokens via the Authentication Service.
Encryption Keys
RSA public key and AES key for gateway-level encryption (required for sensitive operations like PIN management).
Webhook Endpoint
A publicly accessible HTTPS URL to receive real-time event callbacks from the platform.
IP Whitelisting
Your server IP addresses must be whitelisted in M2P's firewall before API access is enabled.
All credentials are environment-specific. You will receive separate credentials for Sandbox, UAT, and Production environments.
Implementation Roadmap
Sections
Tenant Setup
Configure your tenant identity, bank partner routing, and system of record model.
Product Configuration
Define card programs with limits, fees, KYC requirements, and wallet caps.
BIN Setup
Understand BIN allocation, card types, and network-specific configurations.
Card Lifecycle
Master the card status state machine — from issuance to blocking and replacement.
Notification Setup
Configure SMS, email, push, and webhook notification templates.