API References
Payment Transfers
API reference for processing payments and transfers.
1. Transfer EFT/RTC
Initiates an Electronic Funds Transfer (EFT) or Real-Time Credit (RTC) payment.
Subject: svc.account.<partner_id>.transfer_eft_rtc
Request
| Field | Type | Required | Description |
|---|---|---|---|
account_id | string | required | UUID of the account making the transfer |
clientTxId | string | required | Client side tx id to avoid duplicate transactions (UUID) |
amount | number | required | Amount in cents as int64 (min: 100 = R1.00, e.g., 1000 = ZAR 10.00) |
ref | string | required | Reference for the recipient |
pay_and_clear | boolean | optional | True for RTC (instant), false/omit for EFT (batch) |
own_ref | string | required | Your reference (2-50 characters) |
account_number | string | required | Recipient account number |
branch_code | string | required | Recipient bank branch code |
name | string | required | Recipient name |
Response
| Field | Type | Description |
|---|---|---|
tx_id | string | UUID of the created transaction |
amount | string | Amount as string |
Possible Errors
400 Bad Request: Invalid request data or insufficient funds401 Unauthorized: Authentication failed409 Conflict: Duplicate transaction (same clientTxId used within cache duration)500 Internal Server Error: Server-side error occurred
Notes
- RTC vs EFT: Set
pay_and_clear: truefor instant transfers (RTC) orpay_and_clear: falsefor batch processing (EFT) - Amount format: The amount field is int64 in cents (request), but returns as string (response)
- Reference validation: Ensure
own_refis 2-50 characters - Idempotency: The
clientTxIdprovides idempotency. The cache duration is environment-specific.