Kesles PSP — Integration Docs
Confidential
This document is intended only for banks and acquirers that have an existing partnership agreement (NDA) with Kesles. Do not distribute to any other party.
Who This Is For
This documentation is intended for technical teams from banks and payment acquirers integrating with the Kesles Merchant platform as a PSP.
You get read-only access to merchant data whose NMID is issued by your acquirer.
Sections
| Section | Content |
|---|---|
| Integration | Integration contract, HMAC auth, flow overview |
| Events | Merchant lifecycle events sent by Kesles to the PSP |
| Testing | Sandbox environment and test scenarios |
| Reference | Endpoint list, error codes |
Onboarding
To begin integration as a PSP, contact the Kesles team with the following information:
- Bank/acquirer code — 4-letter SWIFT code (e.g.,
BMRI,BRIN,BBNI) - IP allowlist — production IP range that will be used for requests
- Technical PIC — name and contact for coordinating HMAC key rotation
- Signed NDA
The Kesles team will prepare:
- HMAC credentials (API Key ID + secret, delivered via a secure channel)
- Access to the sandbox/staging environment
- UAT schedule before go-live
Pre Go-Live Checklist
- NDA signed
- Bank code registered in the Kesles system
- IP allowlist configured
- HMAC credentials received via secure channel (1Password / Bitwarden)
- Signature computation verified on staging
- Merchant lookup (
GET /merchants/by-nmid/{nmid}) successful on staging - Timestamp freshness check (±300 seconds) implemented
- Retry with exponential backoff implemented
- Key rotation schedule agreed (every 90 days)
- UAT sign-off from both parties
Need Help?
Contact the Kesles team at support@kesles.com for technical questions about the integration.