API Integration
Encryption & Key Exchange
AES-256 payload encryption and RSA-2048 session key exchange for secure API communication.
M2P supports optional request/response body encryption for production environments.
Encryption Architecture
SDK Key Exchange (Recommended)
When using the M2P SDK, encryption is handled automatically:
- Key Exchange — SDK performs ECDH key exchange on initialization
- Auto-Encryption — All subsequent requests are encrypted transparently
- Auto-Decryption — All responses are decrypted transparently
No manual encryption implementation needed when using the SDK. The
KEY_EXCHANGE API call establishes the secure session.Direct API Encryption
For server-to-server integrations without SDK:
| Layer | Algorithm | Key Size | Usage |
|---|---|---|---|
| Payload | AES-256-CBC | 256-bit | Encrypt request/response body |
| Session Key | RSA-2048 | 2048-bit | Encrypt the AES session key |
| Transport | TLS 1.2+ | — | All API communication |
Encryption Flow
Payload encryption is optional in UAT and enabled at the end of UAT cycle before production deployment.