Create payment links
Seal what you deliver and where, choose who may join, and get the link to send the sender.
El-B API
From your code to a witnessed payment
Create payment links from your shop, bot or back office. El-B checks both descriptions of the deal before your RIP is shown, and tells your server, in a signed message, the moment the transaction number arrives.
- Free API, same credits as the app
- The sender pays nothing
- Signed webhooks, retried for you
What the API does
Everything a recipient does, from your code
The same payment, the same checks and the same receipt as in the app. Your system just takes care of the routine.
Follow every step
Read any payment you receive: who joined, whether the deal matched, the transaction number.
Signed webhooks
Each event is signed with your secret and tried again if your server does not answer.
Confirm checked transfers
Once you see the transfer in your BaridiMob history, confirm it from your own tools. The receipt is issued at once.
Credits under control
Price an amount before creating a payment, read your balance and every entry of your ledger.
Usage you can see
Requests, errors, response times and webhook deliveries, day by day, on the API page of your account.
Getting started
Live in four steps
No contract and no setup fee: a verified account and a key.
- 1
Verify your account
Upload an official document from your profile. The API is for accounts verified by an official document.
- 2
Generate your key
One key per account, shown once. El-B only keeps a fingerprint of it.
- 3
Create your first payment
One request with the amount and what you deliver. Send the link you get back.
- 4
Listen for the transaction number
A webhook tells you it arrived. Check your BaridiMob history, then confirm.
curl -X POST https://el-b.com/api/v1/payments \
-H "Authorization: Bearer $ELB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"amount_dzd": 45000,
"deliverable": "iPhone 13, 128 GB",
"fulfillment_target": "Bab Ezzouar, Algiers",
"label": "Order #1042"
}'HTTP/1.1 201 Created
{
"data": {
"code": "Kx7pR2mQ9a",
"url": "https://el-b.com/pay/Kx7pR2mQ9a",
"status": "open",
"credit_state": "held"
}
} Use cases
Built for recipients who sell every day
Wherever you agree on a deal, your system can send the witnessed link.
Online shops
Each order gets its own payment link at checkout, with the order number as its label.
Chat bots
Your Messenger, Telegram or WhatsApp bot sends the link and announces each next step itself.
Back offices
Match every transaction number to an order and close the order the moment the transfer is confirmed.
Service providers
Freelancers and agencies send one witnessed link per invoice and start work once the transfer is confirmed.
Privacy by design
What the API never shares
El-B protects your account number and the deal itself. The API follows the same rules as the app.
-
Your RIP stays out
It is never in an API answer or a webhook. The sender sees it in their browser, once both descriptions match.
-
The deal stays sealed
You get the sender's name and whether their account is verified, never their own description of the deal.
-
Keys are fingerprints
Your key is shown once and stored as a fingerprint. Regenerate or pause it at any time.
-
No money in between
El-B never holds money: the sender transfers in BaridiMob, straight to your account.
Is the API free?
Yes. Calls are free. A payment created through the API costs the same credits as one created in the app, and the sender pays nothing.
Who can get an API key?
Accounts verified by an official document, with a RIP. Each account has one key, generated from the API page of the account.
Does El-B receive or hold the money?
No. El-B is a digital witness, not a bank, a wallet or a payment processor. The sender transfers in BaridiMob, directly to your account.
Can my system confirm transfers by itself?
Your system can call the confirmation endpoint, but only you can check your BaridiMob history: confirm a payment only once you see the transfer there. Without an answer, a payment confirms itself after 72 hours.
Is my RIP sent through the API?
No. Your RIP and your identity data are never in API answers or webhooks. The sender sees your RIP only in their browser, once both descriptions of the deal match.
In which language is the documentation?
In English, with examples in cURL, PHP, JavaScript and Python. This page is available in Arabic, French and English.
Your first payment link is one request away
Generate your key from your account, then follow the quickstart.