Cash disbursement

What if every payout knew who it was for?

A cash disbursement platform for organisations that pay many people — every payment approved by a second person, collected in cash with ID, and on the record.

Live today with an insurance company in liquidation in Jordan

Where we are today

Most organisations pay people from a spreadsheet. That is usually where the control stops.

A list of names, an email to the exchange house, and a phone that never stops ringing. It works for ten people. It stops working long before a thousand.

  1. March payments — v1.xlsxMonday
  2. March payments — v2.xlsxTuesday
  3. March payments — FINAL (2).xlsxWednesday
Three versions. One month’s payments.

A day in the life

A payment day, the way it usually goes.

  1. The list goes to the exchange house by email.

    The third version this week. Two ID numbers were wrong in the last one.

  2. A beneficiary calls to ask if the money is ready.

    Nobody can say for sure. The list is at the exchange house now.

  3. A teller pays a payment that was stopped yesterday.

    The email that stopped it is still unread.

0 payments anyone at head office can see as they happen — until the exchange house sends its own list back, and the two lists are matched by hand.

A list says who to pay. It never says who was paid.

So the list goes out, the phone keeps ringing, and whether each person has actually been paid is answered weeks later — by hand, from somebody else’s records.

The idea

One person, one entitlement — and every payment taken from it.

One person, checked and approved once, with one entitlement. Every payment is taken from it as it is created, so no payment can ever be more than what is left.

  1. 01
    The person

    Checked and approved once by a checker, with what they are owed in total. The platform keeps the balance itself — not a spreadsheet somebody updates.

  2. 02
    The payment

    Once, in rounds, or every month — the pattern is yours. Set the amount or the percentage and the dates once, apply them to the whole list, and the payments are ready for approval in about a minute. Each has its own date to collect from and its own expiry.

  3. 03
    Approval

    Someone prepares, someone else approves — never the same person. A rejected payment goes back to its maker with the reason written down, and your policy sets how many approvers there are and from what amount a second one must agree.

  4. 04
    The message

    At 10:00 on the payment date, the beneficiary — or the lawyer who collects for them — receives a text in Arabic with a 10-digit transaction number. That number and their ID card are all they bring to the counter. A message that fails is tried again the next morning.

  5. 05
    At the counter

    The teller enters the transaction number and the platform checks the payment at that moment. The name and national number are matched to the ID card, the signed receipt is uploaded, and the payment is released — it can never be paid a second time.

  6. 06
    The record

    Who prepared each payment, who approved it, which teller paid it and when — with changes kept as they were, before and after. Owed, approved, paid and still waiting, per person, exported to Excel when the auditor asks.

When plans change

Head office decides. The counter knows at once.

Every one of these is checked when the teller enters the number — not in a report afterwards.

  1. 01

    Pause

    Takes effect at once. The counter refuses the payment until someone resumes it.

  2. 02

    Cancel

    One person asks, with a reason; another confirms. The amount goes back to what the person is owed.

  3. 03

    Not before its day

    A payment can only be collected from its payment date onwards.

  4. 04

    Not after it expires

    After the expiry day, the counter turns it away.

  5. 05

    On hold under review

    While a person’s details are being changed, their payments wait: no payout, no message, no file.

  6. 06

    The last word

    A teller cannot pay what the platform refuses. That is the difference between an instruction and a control.

Try the counter

Take one payment to the counter.

Set what head office has done and the day Layla comes in, then enter her number — and see what the teller would see.

At head office

She comes to the counter on

Transaction no.4817209356
JOD 1,200.000to Layla Haddad

Payment date · 3 JuneExpires · 30 June

    Choose what head office has done and the day she comes in, then enter the number.

    A simulation. Layla Haddad and her payment are examples; the checks are the ones described on this page.

    Live today

    An insurance company in liquidation in Jordan pays its beneficiaries through Kayan.

    Paid in cash through a licensed exchange house — approved by a second person, announced by text, collected with ID.

    • JOD 10Mto be paid out
    • 6,000beneficiaries
    • 5–6payment rounds
    • 25–30Kindividual payouts
    • 52+branches to collect from

    The figures describe the whole programme, which is paid out over several rounds.

    1. 01Approve

      Checked, then approved by a second person.

    2. 02Notify

      Each person is told by text on the payment day.

    3. 03Collect

      At the exchange house’s branches, with ID.

    4. 04Record

      Paid and still to pay, per beneficiary.

    Who it is for

    Not only liquidations. Anyone who pays people in cash.

    The same platform — people, entitlements, approvals, the counter and the record — fits any organisation with money to hand to many people: once, in rounds, or every month.

    Insurance companies

    One-off claim settlements and compensation for people without a bank account — for any running insurer.

    Liquidation committees

    Paying policyholders and creditors what they are owed, in rounds, as funds come in.

    Government programmes

    Monthly cash assistance, subsidies and compensation schemes, with every payout on the record.

    Aid organisations

    One-off grants or regular cash assistance, collected in person with ID.

    Employers

    Bonuses, end-of-service payments and monthly wages for workers without bank accounts.

    Any cash payout

    Wherever people must be paid in cash — the right amount, on the right day, and each payment only once.

    Each new organisation gets its own set-up: its name in the text message, its approval policy and its exchange house’s file format.

    How it fits together

    Four parties. One record.

    Prepared and approved at your office, announced by the platform, paid at the counter — and recorded in one place.

    1. Makers and checkers

      Your organisation

      • People and entitlements
      • Payments on any schedule
      • Approvals, your cycle
      • Pause and cancel
      • Record and exports
    2. The platform

      Kayan

      • Balances it keeps itself
      • Dates and holds
      • Texts at 10:00
      • The nightly payment file
      • One record
    3. Tellers at the branches

      Exchange house

      • Find by number
      • Check the ID card
      • Upload the receipt
      • Pay, or see why not
      • Its own tellers
    4. The person being paid

      Beneficiary

      • A text on the day
      • Any branch
      • The number and an ID
      • Cash at the counter
      • Or their lawyer

    The exchange house gets a teller screen and a nightly file of what is ready to be paid.

    What it is for

    What changes from the very first payment.

    What changes for your team from the very first payment day.

    • Two people, every payment

      Nothing leaves on one person’s say-so, and the approval cycle follows your own policy.

    • A whole list in a minute

      From one screen, for as many people as you need — once, in rounds or monthly.

    • Never early, late or twice

      Dates and holds are checked at the counter, every single time.

    • Fewer calls to answer

      People are told by text when their money is ready, and where to collect it.

    • Every dinar accounted for

      Owed, approved, paid and still waiting — per person, at any moment.

    • An answer for the auditor

      Approvals, payouts and changes on the record — who did what, and when.

    Everything else

    What else comes in the box.

    Your approval cycle, your policy

    Who prepares, who approves, and from what amount a second approver must agree.

    Excel in, Excel out

    People and payments loaded from a template; any list exported.

    Arabic and English names

    Both kept for every person, and the text message goes out in Arabic.

    A code at every sign-in

    A one-time code by email, on top of the password.

    Locked after five tries

    Five wrong passwords or codes lock the account for 30 minutes.

    Roles that hold

    Makers, checkers and admins — enforced by the platform, not only by the screen.

    A queue for every checker

    What is waiting for them, for how long, and what expires soon.

    Exact to the fils

    Every amount kept to three decimals, as the dinar needs.

    Two organisations, kept apart

    The exchange house runs its own tellers. Your staff and theirs never share an account.

    Getting there

    How we start.

    Each stage proves one thing before the next begins. Dates are agreed with your team, not promised in advance.

    1. One

      Set up your programme

      Your people and their entitlements, loaded and approved. Your approval cycle and your exchange house, set up.

      Proves: the figures match your own records.

    2. Two

      A first payment day

      The first payments prepared, approved, announced by text and paid at the counter.

      Proves: people are told, they collect, and every payout is on the record.

    3. Three

      The whole programme

      Every payment after that — once, in rounds or every month — run by your own team.

      Proves: it runs without us in the room.

    Half an hour, on a real payout.

    Let us prepare a list of payments in front of you, approve it with a second person, and take one payment to the counter — refused the day before it is due, paid on the day, with the record written as it happens.

    Book a live walkthrough