Skip to main content
Remittances move funds across corridors and require extra KYC fields. The flow mirrors payouts/collections: accept immediately, then finalize via webhook.

​
Quick flow

Authenticate -> Sign -> Send remittance -> Receive acceptance -> Receive webhook -> Reconcile (optional status check).

​
Prerequisites

​
Endpoint

POST /payments-api-service/v1/remittance Required headers 
Authorization: Bearer <access_token>
Content-Type: application/json
X-Custom-Signature: <base64-signature>
Idempotency: reuse the same transaction.reference for retries of the same logical remittance.

​
Request body (example)

{
  "transaction": {
    "reference": "{{remittance_transaction_ref}}",
    "amount": 1000,
    "currency": "KES",
    "description": "QA Tests",
    "service_code": "PESALINK_REM",
    "timestamp": "2025-09-15T12:45:30.123Z"
  },
  "originator": {
    "msisdn": "256722111999",
    "channel": "USSD",
    "country": "KEN",
    "service_provider": "TELCOM-UK",
    "name": "John Sender",
    "dob": "1965-01-01",
    "nationality": "UK",
    "id_type": "National ID",
    "id_number": "PSA010101"
  },
  "recipient": {
    "reference": "Test",
    "account": "9382947489",
    "name": "Ralph",
    "destination_code": "0002"
  },
  "callback_url": "https://webhook",
  "meta": {
    "note": "QA Test",
    "agent_id": "Test"
  }
}
Notes
  • transaction.timestamp for remittance uses YYYY-MM-DD HH:mm:ss (no timezone suffix).
  • KYC fields are required per corridor. Provide full name, DOB, nationality, and ID details.

​
Acceptance response (immediate)

The acceptance response uses the same envelope as payouts. See Initiate remittance API.

​
Webhook (final outcome)

We POST to your callback_url when the remittance completes. See Webhook payload.

​
Status checks (optional)

If a webhook is delayed or missing, query status using Check remittance status or Status checks.

​
Common issues

  • Signature mismatch: ensure the string-to-sign matches the payload exactly. See Signature generation.
  • Wrong token: use a remittance-scoped Bearer token.
  • Timestamp format: remittance uses YYYY-MM-DD HH:mm:ss.