Motion 5Book a demo

Products

Transfers

Customers send money to any bank account in Nigeria from WhatsApp, confirmed with their PIN. Your own rails move the money: Motion 5 never holds it. This API and the webhooks show you every transfer made in WhatsApp.

How customers send money

  1. 1

    Who

    The customer taps Send money and picks someone they've paid before, or types an account number and bank in one message, like 0123456789 GTBank. Wallet numbers written as phone numbers (0803…) work too. If the bank isn't clear, they choose it from a list.

  2. 2

    Name enquiry

    Your system looks up the account. The customer sees the account holder's name before they say how much.

  3. 3

    How much

    They reply with an amount (5000, 5,000, ₦5k). It's checked against your limits and their balance, and they see the fee before anything moves.

  4. 4

    PIN, every time

    They tap Confirm and enter their PIN in a WhatsApp form. The PIN is asked for every transfer, even if they entered it a minute ago for their balance, and it only confirms the transfer it was asked for.

  5. 5

    The money moves

    Motion 5 asks your system to make the transfer and sends the customer a receipt with your reference. You get transfer.succeeded or transfer.failed.

Built to move money safely

  • Exactly once. Motion 5 records each transfer before asking your system, and gives your system that transfer's ID as an idempotency key. A repeated tap, a retried message or a resent PIN form never sends twice.
  • Never a guess. If your system says the transfer is pending, or doesn't answer, Motion 5 asks again for about 40 minutes and tells the customer the outcome.
  • The PIN binds the transfer. The confirmation and the PIN form carry the same draft, so a PIN entered for one transfer can't approve another.
  • Audited. Every confirmation, success and failure is in your audit log.

Limits

Each customer can send up to ₦100,000 per transfer and ₦500,000 per day (Lagos time) from WhatsApp, counting transfers that are pending or done. Your limits replace these; tell us yours when you go live. The smallest transfer is ₦100. Your own system can still refuse a transfer for its own reasons (tiered KYC limits, say), and the customer sees the reason.

Outcomes

successful
The money left the customer's account. They get a receipt with your reference.
pending
Your system accepted it but doesn't know yet. The customer is told it's processing, and gets the outcome when Motion 5 hears it.
failed
Nothing was taken (or it was all returned). The customer sees the reason your system gave.
GET/v1/transfers
Transfers made in WhatsApp, newest first. Needs a live key: test keys get 403 live_key_required.

Query

status
stringoptional
all (default), pending, successful or failed.
limit
integeroptional
1 to 200. Default 50.
Response
{
  "object": "list",
  "data": [
    {
      "object": "transfer",
      "id": "trf_01JD4C2K8N5P7Q9R1S3T5V7W9X",
      "status": "successful",
      "amount": 500000,
      "fee": 1000,
      "currency": "NGN",
      "narration": "WhatsApp transfer",
      "recipient": {
        "bank_code": "058",
        "bank_name": "GTBank",
        "account_number": "0123456789",
        "account_name": "TUNDE ADEYEMI"
      },
      "account": {
        "reference": "ACC-0012345678",
        "number": "••••5678"
      },
      "customer": {
        "id": "cus_01JD3V0QH5M7X8Z9A1B2C3D4E5",
        "name": "Ada Okon",
        "phone": "+2348031234567",
        "wa_id": "2348031234567"
      },
      "bank_reference": "NIP0000132611161042001234",
      "failure_reason": null,
      "created_at": "2026-11-16T10:42:03.118Z",
      "completed_at": "2026-11-16T10:42:04.902Z"
    }
  ]
}
GET/v1/transfers/{id}
One transfer, by its ID (trf_…). That's also the idempotency key your system received, so you can match the two.
Response
{
  "object": "transfer",
  "id": "trf_01JD4C2K8N5P7Q9R1S3T5V7W9X",
  "status": "successful",
  "amount": 500000,
  "fee": 1000,
  "currency": "NGN",
  "narration": "WhatsApp transfer",
  "recipient": {
    "bank_code": "058",
    "bank_name": "GTBank",
    "account_number": "0123456789",
    "account_name": "TUNDE ADEYEMI"
  },
  "account": {
    "reference": "ACC-0012345678",
    "number": "••••5678"
  },
  "customer": {
    "id": "cus_01JD3V0QH5M7X8Z9A1B2C3D4E5",
    "name": "Ada Okon",
    "phone": "+2348031234567",
    "wa_id": "2348031234567"
  },
  "bank_reference": "NIP0000132611161042001234",
  "failure_reason": null,
  "created_at": "2026-11-16T10:42:03.118Z",
  "completed_at": "2026-11-16T10:42:04.902Z"
}

The transfer object

id
string
Starts with trf_. The idempotency key your system was given.
status
string
pending, successful or failed. See outcomes.
amount, fee
integer
In kobo. The fee is what your system quoted, shown to the customer before they confirmed.
recipient
object
bank_code (CBN code, or self for an account with you), bank_name, account_number, and account_name from name enquiry.
account
object
The customer's account: your reference for it, and the masked number.
customer
object
id is the conversation ID.
bank_reference
string or null
Your system's reference for the transfer, once it has one.
failure_reason
string or null
Why it failed, as the customer was told.
created_at, completed_at
time
completed_at is set when it succeeds or fails.

Your core banking connection

When we connect Motion 5 to your system, transfers need four things from it:

Name enquiry
An account number and bank in, the account holder's name out (or not found).
Fee
What you charge for a given amount and destination.
Transfer
Move the money, idempotent on the key we send: the same key never moves money twice, and a repeat returns the first result.
Status
The outcome of an earlier transfer, by that key: successful, pending or failed.

Your rails, your rules

Motion 5 doesn't replace your transfer checks: fraud screening, KYC tier limits and NIP all stay in your system. If it refuses a transfer, the customer sees your reason.

Events

transfer.succeeded
A transfer from WhatsApp went through. data.transfer is the transfer.
transfer.failed
A transfer from WhatsApp didn't go through.

See Webhooks to set up an endpoint and check signatures.