Release notes: Banking.Live 3.9
PECP-1134: PayControl RSA key generation update for SHA-512 support
PayControl SecureAPI has been updated to support RSA-OAEP encryption with SHA-512 when using 2048-bit RSA public keys, while retaining SHA-1 for legacy 1024-bit keys. The Session ID logic now automatically selects the appropriate hash algorithm based on the key size to align with the backend SHA-512 migration.
This update:
- aligns PayControl with the backend SHA-512 migration
- supports stronger encryption standards
- reduces reliance on weaker SHA-1 and 1024-bit RSA configurations
- avoids disruption for existing integrations that still rely on 1024-bit keys
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | NA | NA | Core – Portals |
Enablement
No manual switch is required in PayControl. To use SHA-512, clients must configure a 2048-bit RSA public key and ensure their backend is configured for RSA-OAEP with SHA-512.
Technical info
To use SHA-512, clients must:
- configure or rotate their PayControl public key to a 2048-bit RSA key
- ensure their backend is configured for RSA-OAEP with SHA-512 for PayControl traffic
Hash selection works as follows:
- 2048-bit RSA public key → RSA-OAEP with SHA-512
- 1024-bit RSA public key -→ RSA-OAEP with SHA-1
Example:
2048-bit RSA key → RSA-OAEP with SHA-512
1024-bit RSA key → RSA-OAEP with SHA-1
CLR-1208: Improved performance for Mastercard settlement file processing
Performance of Mastercard settlement file processing has been improved to better support large settlement files and reduce high memory usage during processing. This helps to:
- improve handling of large settlement files
- strengthen processing efficiency during settlement runs
- reduce performance pressure during high-volume processing
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Mastercard | NA | Processing – Clearing |
Enablement
No enablement required.
Technical info
NA.