Baraka Pay DOCS

← Back to docs

Cash deposits

Money that arrives at a bank counter, tied back to the client who sent it.

Baraka Pay owns the account and the reference

Ask for instructions on behalf of your client and you are told where to send them and which reference to write on the slip. When the money lands, Baraka Pay resolves that reference back to the client and raises cash_deposit.confirmed — and you credit your client on that webhook, exactly as you would for a redeemed voucher.

As with vouchers, nothing here posts to a ledger or moves a balance. It is an authorisation to credit, once.

The reference is stable on purpose

Asking twice for the same client returns the same code. A payer who has lost their slip needs the reference they already gave the bank, not a second one that splits their history in two.

Cash never credits on the strength of a claim

A client saying they paid is not money. Recognition is a separate, audited act against the bank's own record — today a member of staff matching a statement line by hand, tomorrow a bank notification calling the same service with its own external reference. Nothing downstream of recognition changes when that happens.

POST /v1/cash-deposits/instructions where to send a payer, and the reference GET /v1/cash-deposits what has been registered POST /v1/cash-deposits/recognitions record money the bank actually received