Bank Transfer (RTGS/EFT)

Scope

This applies to scenarios where end users are making a transfer to:

1. Other Domestic (Kenya) Bank Accounts via RTGS

2. Other Domestic (Kenya) Bank Accounts via EFT

Under what circumstances should end users use RTGS/EFT instead of Pesalink for bank transfer?

Use Case	Why RTGS / EFT
Single transfer exceeding KES 999,999	RTGS: No upper limit (or limits up to ​KES 100 million), with ​real-time irrevocable settlement. EFT: Supports batch processing for large volumes, albeit with delayed settlement (e.g., T+1)
B2B payments requiring invoice references, contract IDs, or audit trails	Pesalink lacks metadata support, complicating reconciliation. RTGS/EFT provide ​detailed transaction records and comply with corporate governance standards.
Recipient banks not integrated with Pesalink. Corporate accounts barred from using Pesalink (common in B2B contexts)	RTGS/EFT are universally accepted across Kenyan banks, regardless of Pesalink participation

RTGS vs. EFT

Scenario	Recommended Channel	Rationale
Urgent, high-value (>KES 5M)	RTGS	Real-time, no cap, and irreversible settlement.
Non-urgent bulk corporate	EFT	Lower fees, batch processing, but delayed settlement (T+1).

Steps

1

Initiate Transfer Request

Call endpoint /trans/largeDomesticInterBankTransfer to initiate a transfer request

Status: 1-SUBMITTED

2

Confirm OTP

Call endpoint /common/sendOtp to request for OTP, filling the value of applicationId to businessId parameter. Call endpoint /common/confirmOperation to confirm the OTP code received.

Status: 2-VALIDATING

The endpoint /common/sendOtp can also be used to resend OTP.

3

Bank Validating

Status: 3-APPROVED or 4-REJECTED

4

Bank Processing

Status: 6-IN_TRANSIT

5

Get Onboarding Result

• Get it from 0023 - Inter-Bank Fund Transfer Result Notification

• Query transaction status by calling the endpoint /trans/getInterBankTransferDetails

Status