Built for institutions
Two-person control by default. Everything on the record.
Governance is not a module we sell separately. It is the default path through every screen — and the first thing a risk team will want to check.
Dual control
By default, a material change waits for a second person — across about fifty kinds of change. The approval screen says what agreeing will actually do.
On the record
Every change is kept with what it was before, what it became, and who agreed to it.
Inside your walls
For card programmes, Kayan is installed inside the bank beside the card system it already runs. Cardholder data never leaves its network.
One deployment each
Each institution runs its own deployment. Your data never sits beside another institution’s.
Try it
One change. Two people.
Change a limit as one person, approve it as another, and watch the record keep both names.
Fuel bucket · card •••• 4417
Nothing is waiting for Omar yet. Submit a change as Rana first.
- No changes recorded yet.
Simulation. Names and amounts are examples.
Deployment
How Kayan sits beside what you already run.
Kayan does not replace a card management system and never stands in for the bank. Only the cards you enrol are checked against Kayan’s rules; every other card carries on exactly as it does today. Kayan answers VALID or INVALID with a coded reason; the card system makes the final authorisation and reports the outcome back.
- The bank owns the money, the licence and the customer
- Kayan owns the rules and the allowances; the bank stores none of them
- A figure the bank has not reported is shown as unreported, never as zero
- An operation that never came back is recorded as unknown — never as a success
Your brand, not ours.
The portals, the app, the in-app card, statements and emails carry the institution’s name and colours. A check fails the build if ours ever appears.
Try an institution’s colours
Security posture
What is true today, stated plainly.
We would rather tell you where we stand than have you find it in due diligence.
- AccessRole-based permissions per portal, checked on the server for every request — never only by hiding a menu.
- SessionsSigned, short-lived sessions with idle and absolute timeouts; a revoked session is refused on the next request.
- Second factorA one-time code on sign-in for every portal user, with lockout after repeated failures.
- Cardholder dataKayan never stores a card number. Cards are referenced by opaque tokens issued by the card system.
- IsolationOne deployment per institution; company data is separated on the server and tested across companies.
- EvidenceMore than a hundred automated test suites and browser acceptance for every change, in both languages, at three widths.
Questions
What institutions ask us first.
Something else on your mind? Write to info@kayan.global and a founder will answer.
Is Kayan a bank?
No. Kayan is technology that institutions run. The bank or programme owner holds the money, the licence and the relationship; Kayan holds the rules about how that money may be used.
Which solutions are live today?
Expense management and cash disbursement are live. Card and wallet disbursement is in final preparation — register your interest and we will share timing with you directly.
Does Kayan replace our card management system?
No, it works beside it. Only the cards you enrol are checked against Kayan’s rules; every other card carries on exactly as it does today.
Where does our data live?
Each institution runs its own deployment. For card programmes, Kayan is installed inside the bank, so cardholder data never leaves its network.
What happens when a payment is refused?
It is refused with a coded reason, and the person sees that reason in plain Arabic or English — what was wrong, and what to do next.
Can one card hold several budgets?
Yes. Spending buckets let one card carry many budgets, each with its own merchants, money and refill — on prepaid and on credit cards.
Which languages are supported?
English and Arabic, with the layout fully mirrored for right-to-left, across every portal and the mobile app.
How does a programme start?
With a thirty-minute walkthrough on a live programme. The launch then runs in stages agreed with your technology team, each with one thing it must prove before the next begins.
How is Kayan priced?
Per programme: a setup fee, a recurring platform fee and a usage component tied to active instruments or funds processed. We will price your programme specifically once we understand it.
See a live programme in thirty minutes.
We will onboard an organisation in front of you, set its rules and put a payment through — approved at one merchant, declined at the next, with the reason recorded both times.