Payment account RIB certificate: your RIB, exports, receipts and incoming transfers

The ChariPay payment account RIB certificate is a PDF you download from the portal or through the API, showing the RIB in your company's name. Its first job is simple: letting a customer, especially a business customer, pay you by bank transfer into this account. Around it, the account produces other documents your accountant will use: the CSV export and the reference of every movement, the reference of each payout on your bank statement, and receipts for bills you pay. This guide explains where to find each one, what it contains and what it is for, without promising anything beyond what the account actually produces.

The payment account RIB, in your company's name

ChariPay is a Moroccan payment platform, a PSP operated by Chari Money, a payment institution licensed by Bank Al-Maghrib. The account that receives your collections is a real payment account, held by Chari Money, opened in your company's name, with a RIB in that name and a PDF certificate to download from the portal or through the API. It receives your collections and incoming transfers, and serves your payment operations.

Two clarifications prevent misunderstandings. ChariPay is not a bank: your payment account is held by Chari Money. It complements your bank; it does not replace it: your bank account remains the destination of your payouts. So the payment account RIB is a second RIB, the one for the account where your customers pay you, alongside your bank's.

What the account is not, and how it compares with a bank account, is covered in the guide to the payment account in Morocco. Here, we stick to the documents.

Downloading the payment account RIB certificate

Two routes lead to the certificate.

1. 1From the portal. The PDF certificate can be downloaded from the merchant portal, available in French and English. It is the simplest route when you need to send it to a customer.
2. 2Through the API. If your back office needs to display the RIB or attach the certificate to an invoice, two calls are enough: GET /v1/wallet/account returns the account details, and GET /v1/wallet/account/rib-document returns the certificate as a PDF. There is a single base URL — https://api-psp.charipay.ma — and the key selects the environment.

# Account details (RIB) — JSON
curl -X GET 'https://api-psp.charipay.ma/v1/wallet/account' \
  -H 'X-CHARI-PAY-API-KEY: chari_sk_test_...'

# RIB certificate — PDF
curl -X GET 'https://api-psp.charipay.ma/v1/wallet/account/rib-document' \
  -H 'X-CHARI-PAY-API-KEY: chari_sk_test_...' \
  -o attestation-rib.pdf

Both calls are in the Wallet module of the API docs, along with reading the balance (GET /v1/wallet). If the account's wallet is not active, these calls return 422 WALLET_NOT_ACTIVE; a chari_sk_live_… key receives 403 PRODUCTION_ACCESS_NOT_ENABLED until production is enabled. The key stays on the server: never in the browser, a mobile app, a git repository or a screenshot.

As for how a third party will use the certificate, we assume nothing: ask your customer, or the organization concerned, which document they expect.

You can explore the portal and call the Wallet module with a test key, with no approval to wait for: 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. A payment with the test card 4918 9141 0719 5005 (CVV 123, any future expiry date, 3-D Secure code 555) then lets you explore the export, with no real money. Your business verification (KYB) runs in parallel and only gates the move to production.

Receiving a bank transfer into your payment account

The payment account is not only for collecting by card or in cash at an agency: it receives your collections and incoming transfers. Sharing your RIB with a customer lets them pay you by bank transfer, into the same account as your other collections.

Two situations where this helps:

• A business customer who pays by transfer. Their accounting department registers you as a supplier with your RIB: send them the certificate, ideally with your first invoice.
• A supplier refunding you an overpayment or a credit note.

One precaution is essential: your RIB circulates, so make sure your customer actually received it from you. A RIB change announced by a simple message is a well-known fraud technique; tell your customers you never change your details without confirming them in person or by phone.

For an invoice you want paid online, by card, rather than by transfer, a payment link is more direct: the method is covered in the guide to getting invoices paid online.

The reference of every movement and the CSV export

The RIB identifies the account; the export says what happened in it. Every account movement carries the reference of the sale, refund or payout that explains it; the portal separates amount paid, fees and net, and the CSV export keeps those references — from the portal or with GET /v1/transactions/export.csv (up to 10,000 rows; beyond that, split by period with from/to). Timestamps are in UTC; Morocco is UTC+1: your reconciliation tool must convert.

What your accountant does with it:

The calls are described in the Transactions module of the API docs. The daily method — what to reconcile, in what order, which gaps to expect — is in the guide to reconciling your collections.

The payout reference on your bank statement

On the other side, on your bank statement, the document that matters is the payout reference. The payout to your bank is a separate operation: automatic every night once a settlement account is configured, or by transfer on demand, for the amount and at the time you choose. Each payout carries a reference that appears on your bank statement.

That reference links the two documents: the line on your bank statement and the payout movement in the payment account export. One point is worth knowing in advance: in the export, each refund is a separate movement linked to the original transaction; it can reduce the next payout without a separate line on the bank statement. If a payout surprises you, the explanation is in the export, not on the statement.

Receipts: paid bills and customers

Two kinds of receipts complete the file.

• Receipts for the bills you pay from the account. When you pay a bill with the listed billers, the amount is debited from your available balance, with no extra fee, and the receipt is sent by SMS. File it with the matching bill.
• Your customers' receipts. "Transaction tracking and customer receipts" is part of what is included at no extra cost.

For bills paid from the account, the full flow — biller, reference, unpaid bills, codes — is described in the guide to paying bills from your payment account.

The audit log, the record no one can rewrite

Behind your documents, the platform keeps its own record: the audit log. The audit log is cryptographically chained: history cannot be rewritten. Sensitive actions — payouts, adjustments, account freezes — also require a distinct requester and approver.

What this means for your file:

• A history that is not edited after the fact: an entry in the log cannot be rewritten.
• A record kept by the platform: we describe neither viewing nor exporting this log from the portal here.
• Roles that limit actions upstream: portal roles separate viewing from acting, and the owner or an authorized manager triggers outgoing operations.

For a given period, the reference document remains the export, with its references: that is what you hand to your accountant, together with the payout references and the receipts.

The account's document file, in one list

For your manager and your accountant, here is the complete file, and where to find each document:

• The RIB certificate (PDF): from the portal or with GET /v1/wallet/account/rib-document; to send to customers who pay you by transfer.
• The account details: from the portal or with GET /v1/wallet/account.
• The CSV export and its references: from the portal or with GET /v1/transactions/export.csv, up to 10,000 rows per export, timestamps in UTC.
• The reference of each payout: on your bank statement, and the same one in the export.
• Receipts for paid bills: by SMS, to file with each bill.

On top of these comes the chained audit log, kept by the platform: history cannot be rewritten.

To decide with your accountant, before the first collection, how these documents enter your books, follow the accounting checklist for collections.

Frequently asked questions

Does my ChariPay payment account have a RIB?

Yes. The payment account is held by Chari Money, a payment institution licensed by Bank Al-Maghrib, and opened in your company's name, with a RIB in that name and a PDF certificate. ChariPay is not a bank: this RIB belongs to your payment account, which complements your bank without replacing it, and which receives your collections and incoming transfers. It also lets your business customers pay you by bank transfer.

Where can I download the payment account RIB certificate?

From the merchant portal, or through the API with GET /v1/wallet/account/rib-document, which returns the certificate as a PDF; GET /v1/wallet/account returns the account details. Both calls use the base URL https://api-psp.charipay.ma and the X-CHARI-PAY-API-KEY header, with a key kept on the server. The Wallet module of the API docs describes them. Your back office can also attach the certificate to your invoices if it needs to.

Is the RIB in the company's name or the owner's name?

In the company's name. The payment account is opened in your company's name, with a RIB in that name and a PDF certificate. Your business is also verified (KYB) — identity documents and trade register — before going live. Your business customers therefore pay the company, not an individual, and register it as a supplier under its name: send them the certificate yourself, for example with your first invoice.

Can a customer pay me by bank transfer to this RIB?

Yes. The payment account receives your collections and incoming transfers: a business customer can register you as a supplier with this RIB and pay you by transfer, into the same account as your other collections. Send the PDF certificate yourself, and tell your customers you never change your details without confirming them in person or by phone. If the customer prefers to pay by card, send them a payment link.

How do I find a ChariPay payout on my bank statement?

By its reference. Every payout to your bank — automatic every night or by on-demand transfer — carries a reference that appears on your bank statement, and the same reference is in the payment account export. A refund can reduce the next payout without a separate line on the statement; in the export, it remains a separate movement. Always match by reference, not by amount alone.

Is the CSV export of transactions limited?

Yes: one CSV export covers up to 10,000 rows. Beyond that, split by period with the from and to parameters, from the portal or with GET /v1/transactions/export.csv. Each row keeps the reference of the sale, refund or payout that explains it, and the portal separates amount paid, fees and net.

Why don't the times in the export match Moroccan time?

Because timestamps are in UTC, while Morocco is UTC+1: your reconciliation tool must convert. A payment made shortly after midnight, Moroccan time, shows up on the previous day in the export. Convert before you total a day; otherwise, sales on either side of midnight move to the wrong day in your books.

Next step

Start in test mode to explore the portal, the export and the Wallet module with a test key. Then prepare your KYB documents — identity and trade register — for the move to production. The guide to the payment account in Morocco presents the account as a whole.