Skip to main content
All articles
Guide12 min read

Pay suppliers from collections: a Moroccan merchant's cash-flow cycle

Pay suppliers from collections: transfers to any Moroccan RIB, bills and top-ups from your balance, a buffer, the nightly payout and clear team approvals.

To pay suppliers from collections is to use the money your customers have just paid you without waiting for it to go through your bank first. In a ChariPay payment account, the amount of a successful payment is available instantly: the same day, you can send a transfer to a supplier's RIB, pay the shop's electricity bill or top up your team's phone lines through the API. This guide walks through the full cycle — collect, pay, keep a buffer, let the nightly payout go — how to organize your suppliers and your approvals, and what record each outgoing payment leaves for your accountant.

Pay suppliers from collections: the full cycle

A merchant's cash flow comes down to five steps that repeat every day:

  1. 1Collect. Your customers pay by card, with 3-D Secure, through a payment link or the hosted checkout, or in cash at an agency of the Chari network, starting from a single-use link.
  2. 2Have it available. As soon as a payment succeeds — a card authenticated with 3-D Secure or a reference paid in cash at an agency — the amount is available in your ChariPay payment account and usable right away: transfers, bills, top-ups.
  3. 3Pay. From the portal, a transfer to a supplier's RIB or a bill with the listed billers; through the API, telecom top-ups.
  4. 4Keep a buffer. Do not commit the whole available balance during the day: a margin for refunds and the unexpected, because the account has neither overdraft nor credit.
  5. 5Pay out. The automatic nightly payout to your bank, once a settlement account is configured, or an on-demand transfer.

ChariPay is a Moroccan payment platform, a PSP operated by Chari Money, a payment institution licensed by Bank Al-Maghrib. ChariPay is not a bank: your payment account is held by Chari Money. It complements your bank; it does not replace it: the payment account keeps the money from your sales moving, while the bank keeps what belongs to credit and savings. The guide to the payment account in Morocco covers the account itself — a RIB in your company's name, the certificate, payouts.

What collected money can pay from the account

To pay from the balance of your collections, the portal and the API offer three kinds of outgoing payment. They do not use the same channel and do not leave the same record.

Outgoing paymentWhereApprovalRecord
Transfer to a supplierPortal, to any Moroccan RIB; fixed fee shown before you confirmSix-digit one-time code emailed to the validation addresses, required for every transfer; number of approvers set by you"In progress" or "Rejected" status, reference text, merchant_transfer.completed / merchant_transfer.failed events
Phone, water, electricity bill, vehicle taxPortal, with the listed billers, no extra feeTwo codesReceipt sent by SMS; bill_payment.pending, bill_payment.succeeded, bill_payment.failed events
Telecom line top-upAPI, from the same balanceCall authenticated with your API keyResult by signed webhook: topup.succeeded / topup.failed

For transfers, from the portal, you send transfers to any Moroccan RIB: the fixed transfer fee is shown before you confirm, the amount is debited immediately and the beneficiary receives it within 24 business hours; an executed transfer cannot be canceled. The step-by-step walkthrough is in the guide to transfers from your payment account.

For bills, you choose the biller, enter the reference, select the unpaid bills found, then confirm with two codes; the amount is debited from your available balance, with no extra fee, and the receipt is sent by SMS. The details are in the guide to paying bills from your payment account.

You can explore the portal before committing a single real dirham: Start in test mode. Three fields — name, work email, company — then an activation link received by email to choose your password, then the portal, where you create your own test key after re-authenticating; the full key is shown only once. Pay with the test card 4918 9141 0719 5005 (CVV 123, any future expiry date, 3-D Secure code 555); in the sandbox, any six-digit code is accepted to approve a transfer. No real money moves and no real bank transfer goes out; your business verification (KYB) runs in parallel and only gates the move to production.

Keep a buffer: no overdraft, no credit

The payment account has neither overdraft nor credit: an outgoing operation that exceeds the available balance is blocked. That is a protection — you cannot spend more than your available balance — and also a management constraint: a supplier transfer you planned to send in the morning does not go out if the balance does not cover it.

Three reasons to keep some margin available rather than committing everything during the day:

  • Refunds draw on the same balance. Refunds are free; the amount is deducted from your available balance, and if the balance is not enough, the operation is blocked rather than creating an overdraft.
  • Due dates pile up. Several suppliers paid on the same day, an electricity bill, a few top-ups: add them up before you approve, not after.
  • Collections do not arrive on a fixed schedule. A quiet day, a customer who takes a while to pay their reference at an agency: the margin absorbs those gaps.

The buffer is a management decision, not an account setting. We do not describe here what the nightly payout leaves in the payment account: before a large outgoing payment, the available balance shown in the portal is what counts.

High season, low season: two cash-flow rhythms

Take a clothing shop that sells online and in store. Before Eid or at back-to-school time, sales pick up and restocking cannot wait. The money collected during the day — by card or in cash at an agency — is available instantly in the payment account: it pays the wholesaler by transfer the same day, without waiting for it to go through the bank. The supplier receives the transfer within 24 business hours, and the goods get back on the shelves sooner.

In low season, the rhythm reverses. Sales are more spread out, suppliers are paid on their due dates, and the automatic nightly payout does most of the work: it leaves every night for your bank account, with no action on your part. The on-demand transfer remains available at any time, for the amount and at the time you choose, when a bank due date is coming up.

In both cases, the question is not "when does the money arrive?" but "where should I pay from?" For the three clocks — credit to the account, nightly payout, on-demand transfer — see the guide to payout timing.

Setting up your suppliers as beneficiaries

The day a supplier has to be paid is not the day to register them. Prepare the list ahead of time:

  1. 1Register each supplier with their Moroccan RIB, checked against a document issued by their bank, never against a forwarded message. A RIB change announced by a simple message is a warning sign: confirm it by phone with someone you know.
  2. 2Give them a readable alias — "Fabric wholesaler," "Label printer" — so you can find them without rereading their details.
  3. 3Mark your regular suppliers as favorites: up to five favorite beneficiaries.
  4. 4Add a new supplier as soon as their first invoice arrives, not on the due date: a security delay applies after adding a new beneficiary.
  5. 5Fill in the transfer reference every time — 60 characters at most — with the supplier's invoice number: that is what your accountant will look for.

Each beneficiary then keeps its own transfer history: it is the first place to look when a supplier tells you they have not been paid.

Getting outgoing payments approved

Paying fast does not mean paying without control. Portal roles separate viewing from acting: owner, manager, cashier, accountant. The accountant reads everything without triggering anything, the cashier collects without seeing the balance or transfers, the owner or an authorized manager triggers outgoing operations.

Each type of outgoing payment adds its own approval:

  • Transfer: every transfer sent from the portal is validated by a six-digit one-time code, emailed to each validation address designated in Settings → Security — up to five addresses, each belonging to a team member authorized to make transfers; you set the number of approvers required. Until an address is configured, no transfer can be sent. With several approvers required, the outgoing payment no longer rests on a single person.
  • Bill: approval takes two codes.
  • Sensitive actions: payouts, adjustments and account freezes require a distinct requester and approver, and re-authentication is required before every sensitive action.

A simple setup for a mid-sized business: the business owner keeps the owner role, an authorized manager prepares supplier payments, a second approver validates transfers by code, and the accountant views without triggering anything. Typical setups and onboarding a new team member are covered in the guide to portal roles and access.

The accounting record of every outgoing payment

Every outgoing payment leaves a record your accountant can reconcile without calling you:

Outgoing paymentWhat you seeWhat your system receives, if you integrate webhooks
Transfer"In progress" = debited; "Rejected" = not debited; reference text and history per beneficiarymerchant_transfer.completed or merchant_transfer.failed
BillReceipt by SMS; movement debited from the balancebill_payment.pending, bill_payment.succeeded or bill_payment.failed
Top-upMovement debited from the balancetopup.succeeded or topup.failed

In the export, every account movement carries the reference of the sale, refund or payout that explains it, and the CSV export keeps those references. The audit log is cryptographically chained: history cannot be rewritten.

Two habits are enough: a supplier invoice number in every transfer reference, and the SMS receipt of every bill filed with the supporting document. To organize the bookkeeping with your accountant before the first payment, follow the accounting checklist for collections.

When to pay out to your bank rather than pay from the account

The payment account complements your bank; it does not replace it. Some payments keep leaving from your bank account: the ones debited from it automatically, the payments your partners expect from your bank, whatever you prefer to centralize there. Those are funded by the payout to your bank: automatic every night once a settlement account is configured, or by transfer on demand, for the amount and at the time you choose.

The practical rule:

  • Pay from the payment account whatever can be paid from it: suppliers by transfer, bills with the listed billers, top-ups through the API. The money is already there.
  • Let the nightly payout fund your bank.
  • Trigger an on-demand transfer when a bank due date is coming up, counting in business hours, and reread the RIB, the amount and the fee shown before you confirm: an executed transfer cannot be canceled.

For 50 MAD, order a ChariPay card linked to your payment account and pay with the money you collect.

Frequently asked questions

Can I pay a supplier with money collected the same day?

Yes. As soon as a payment succeeds, by card or in cash at an agency, the amount is available in your payment account and usable right away. From the portal, you send a transfer to the supplier's Moroccan RIB: your balance is debited immediately and the supplier receives the money within 24 business hours. If it is a new beneficiary, a security delay applies after adding them.

Which banks can a supplier transfer go to?

Any Moroccan RIB: the transfer leaves from the portal to your supplier's bank account, whichever bank they use in Morocco. The fixed transfer fee is shown before you confirm, and the beneficiary receives the money within 24 business hours. Register your regular suppliers in advance, with an alias, and up to five of them as favorites.

What happens if the balance is not enough to pay a supplier?

The payment is blocked. The payment account has neither overdraft nor credit: an outgoing operation that exceeds the available balance does not go out. You can wait for the next collections, or pay part of the amount now and the rest later. To avoid the situation, keep a margin available, especially for refunds, which are deducted from the same balance.

Can several people approve a supplier payment?

Yes. Every transfer sent from the portal is validated by a six-digit one-time code, emailed to the validation addresses designated in Settings → Security, and you set the number of approvers required. The transfer only goes out once approval is complete. With at least two approvers required, and portal roles upstream, you keep any one person from moving money out of the account alone.

Can I cancel a supplier transfer sent by mistake?

No: an executed transfer cannot be canceled. Your balance is debited as soon as you confirm: that is what the "In progress" status means; a "Rejected" transfer, for its part, is not debited. Reread the RIB, the amount and the reference before you approve. If you make a mistake, contact the supplier, quoting the transfer reference and date, to arrange the return of the funds.

Can I pay the shop's electricity or phone bill from the account?

Yes. From the portal, you pay phone, water, electricity, vehicle tax and other bills with the listed billers: you choose the biller, enter the reference, select the unpaid bills found and confirm with two codes. The amount is debited from your available balance, with no extra fee, and the receipt is sent by SMS. For a question about a bill, the billers' helpline answers on 115.

Can my team's telecom top-ups come out of the same balance?

Yes, through the API: you top up telecom lines from the same balance as your collections, and the result reaches you by signed webhook, with the topup.succeeded or topup.failed events. Top-ups therefore require an integration, built by your technical team with your API key, which stays on the server side, never in the browser or a mobile app.

Next step

Start in test mode to open the portal the way your team will use it: beneficiaries, validation addresses, a transfer approved by code, with no real money. Use it to write down your regular suppliers and your approvers, then prepare the move to production. The guide to transfers from your payment account details every screen of a transfer.

Written by ChariPay team.

Read next

Ready to try it yourself?

Create your account and take test-mode payments today: it is free, with no approval to wait for. A question? Our team supports merchants and developers alike.

  • Free, no commitment
  • Test mode from sign-up
  • No approval to wait for