Integrate with Equity Bank's Jenga API for payments, transfers, account queries, and financial transactions across East Africa. Use this skill for remittances, balance inquiries, transaction queries, PesaLink transfers, RTGS payments, and multi-country operations in Kenya, Uganda, Tanzania, Rwanda, DRC, and South Sudan.
⚠️ Partner/Enterprise Access Only. The Jenga API is not publicly self-service. Access requires manual onboarding through Equity Bank's partner program — apply via finserve.africa or contact your Equity Bank relationship manager. Expect a 2–6 week approval process including business verification and legal agreements. There is no sandbox self-signup.
⚠️ RSA Request Signing. In addition to Bearer token authentication, some Jenga API endpoints require RSA digital signature of the request body. You sign a hash of the request payload using your RSA private key (RS256), and include the signature in the
Signatureheader. Ensure you handle this during onboarding — Equity Bank provides your keypair as part of the partner onboarding process.
Equity Bank's Jenga API is a comprehensive fintech platform providing access to banking and payment services across East Africa. It enables developers to build payment applications, fintech solutions, and banking integrations with support for remittances, account management, real-time payments, and transaction history queries.
You're building a fintech application, payment platform, mobile wallet, accounting tool, or banking solution that needs to integrate with Equity Bank Group — East Africa's largest bank by asset base. Use Jenga API when you need to:
Jenga API bridges Equity Bank services with modern applications across Kenya, Uganda, Tanzania, Rwanda, Democratic Republic of Congo, and South Sudan.
Jenga API uses Bearer token authentication with merchant credentials. Tokens are obtained via the merchant authentication endpoint and must be refreshed before expiry.
POST /authentication/api/v3/authenticate/merchant
Content-Type: application/json
Api-Key: {your_api_key}
Body:
{
"merchantCode": "your_merchant_code",
"consumerSecret": "your_consumer_secret"
}
Response:
{
"accessToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...",
"refreshToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...",
"expiresIn": 3600,
"issuedAt": "2025-02-24T10:00:00Z",
"tokenType": "Bearer"
}
Token Details:
accessToken: JWT token for API requests (expires in 1 hour typically)refreshToken: Token to refresh access without re-authenticatingexpiresIn: Token lifetime in secondstokenType: Always "Bearer"Cache the token and refresh before expiry. Implement 401 error handling to detect expired tokens.
UAT/Sandbox: