Sender Profile
Overview

Each remittance needs a complete sender (KYC) profile on the merchant business. Save it once, then reuse it for later transfers. Create and execute fail until readiness is complete.


Check readiness
HTTP MethodGET
Endpoint URL/api/v2/remit/readiness
Base URLhttps://base-url-here.com
DescriptionReturn whether the business sender profile is complete.
curl --location --request GET 'https://base-url-here.com/api/v2/remit/readiness' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>' \
--header 'X-Business-Id: 9'
{
    "success": true,
    "message": "Success",
    "data": {
        "ready": false,
        "missing": [
            "sender.date_of_birth",
            "sender.doc_number"
        ]
    }
}

Save sender profile
HTTP MethodPUT
Endpoint URL/api/v2/remit/sender
Base URLhttps://base-url-here.com
DescriptionCreate or replace the sender profile for this business.
Request Body
FieldTypeDescriptionRequired
other_namesstringSender given names.Yes
surnamestringSender family name.Yes
phonestringSender phone in international format.Yes
nationalitystringISO country of nationality, e.g. KE.Yes
doc_typestringpassport, national_id, or id. Stored as PASSPORT or ID.Yes
doc_numberstringID or passport number.Yes
date_of_birthstringDate of birth, e.g. 1990-01-31.Yes
origin_countrystringISO country the funds originate from, e.g. KE.Yes
curl --location --request PUT 'https://base-url-here.com/api/v2/remit/sender' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--header 'X-Business-Id: 9' \
--data-raw '{
    "other_names": "Jane",
    "surname": "Wanjiku",
    "phone": "254712000000",
    "nationality": "KE",
    "doc_type": "national_id",
    "doc_number": "12345678",
    "date_of_birth": "1990-01-31",
    "origin_country": "KE"
}'
{
    "success": true,
    "message": "Success",
    "data": {
        "ready": true,
        "missing": []
    }
}

Terms of Use & Legal

By using this API, you agree to our Terms of Service and Privacy Policy. Do not share sensitive data or credentials.