This page covers how customers pay you on your storefront. The default in Algeria is Cash on Delivery (COD) — the customer pays cash when the courier delivers. Digital stores can also accept manual-receipt payments (CCP, BaridiMob, RedotPay, custom methods) where the customer uploads a transfer screenshot you verify.
ℹ️ Info — Card rails are for merchants paying DZBuild, not for customer checkouts
Merchant payments to DZBuild run on two card rails: SlickPay (CIB / Edahabia) and Paddle (Visa / Mastercard / PayPal / Apple Pay). Both cover the same four purchases: plan subscriptions, AI credits, paid addons, and domain purchases. Neither is wired into your storefront checkout. The supported customer methods are COD, manual-receipt, and free_digital.
The three customer payment methods
Whatever the storefront sends, the server stores one of exactly three values on the order:
| When |
| Cash on Delivery — the default, and the fallback for anything else on a physical order. |
| A free digital product (lead magnet, free download). Checkout has no payment step at all. |
| Manual-receipt checkout on a Digital-theme store. |
Any other value is coerced server-side to cod (or to free_digital when the delivery type is digital).
Cash on Delivery (COD)
Default and most-used payment method in Algeria. No payment provider is involved at checkout — the customer enters their phone, address and wilaya, and pays cash to the courier on delivery.
Conversion-friendly. COD is the trust standard in Algerian commerce.
There is no COD toggle. On every theme except Digital, COD is the only customer payment method the checkout accepts — there is nothing to turn off. The choice only exists on Digital-theme stores, where you can offer manual-receipt methods instead; doing that for physical goods aimed at Algerian buyers typically costs a large share of conversions.
No transaction fees from any payment provider.
Cash flow timing. You receive the money when the courier remits it (typically a few days to a couple of weeks depending on the courier).
How the customer experiences COD
Customer fills the order form (name, phone, wilaya, city, items).
Submits — order arrives in your dashboard as
pending.You confirm by phone, the courier delivers, the customer pays cash.
This is the path most Algerian merchants live on, and on every theme except digital, COD is the only built-in customer payment method.
Manual-receipt payments (Digital Theme only)
Manual-receipt checkout is a paid addon — Payment Gateway, 500 DZD/month — configured at /dashboard/digital/payment. It is mostly used for non-physical products (courses, e-books, digital downloads) where COD doesn't make sense.
Until the addon is active, that page shows only the purchase card and no methods can be saved.
It is bought with a card: CIB / Edahabia via SlickPay, or Visa / Mastercard / PayPal via Paddle. Paying for it by uploading a CCP or BaridiMob receipt was discontinued in July 2026 and is no longer offered.
The page redirects to your dashboard home if your store theme is not Digital.
Built-in receipt-based methods include:
CCP (Algeria postal account)
BaridiMob (Algerian mobile transfer)
RedotPay (USDT / TRC20 wallet)
Custom methods you define yourself (BankAccount IBAN, etc.)
How a manual-receipt payment works
The merchant configures one or more payment methods at
/dashboard/digital/payment.At checkout, the customer picks a method, transfers the money outside the platform, and uploads a screenshot of the receipt.
The order arrives with
payment_method = digital_payment, an order status ofpending, and a separatepayment_statusthat also starts pending.You verify the receipt manually and set
payment_statusto paid. Nothing is auto-verified.
Where to find the receipt
Digital orders do appear in your normal Orders list, but the receipt image is not rendered there. Open Dashboard → Digital → Orders (/dashboard/digital/orders) and click the order to see it.
Verification is a separate field from the order status: you flip payment_status from the digital order's detail page, and confirming the order marks it paid automatically.
Receipt images are private: the dashboard shows them through a temporary link that expires after an hour, so the image URL can't be shared, bookmarked or hotlinked.
Configuration page
Go to Dashboard → Digital → Payment (/dashboard/digital/payment). You can configure up to 10 methods per store, each with:
Name
Type — Custom, RedotPay, CCP or BaridiMob
Account-holder name
Payment details and instructions
Currency — DZD, USD or EUR, with a conversion rate for the non-DZD ones
Receipt required — yes / no
Enabled / disabled
Logo — custom methods only; CCP, BaridiMob and RedotPay ship with built-in logos
Extra fee, expressed as a percentage
The extra fee is calculated server-side as that percentage of the subtotal after discount, added to the order total, and stored on the order as payment_fee.
The customer sees the enabled methods on the digital-theme checkout page.
Digital checkout collects contact channels, not an address
Because there is no delivery, the digital checkout asks for contact channels instead of a postal address: Telegram, Instagram, WhatsApp, plus up to three custom fields. Configure them — and mark which are required — at Dashboard → Digital → Checkout fields (/dashboard/digital/checkout-fields).
Refunds
DZBuild does not automate refunds. Handle them per-method:
COD — just cancel the order; no money has been taken.
Manual receipt — refund the customer through the original transfer channel (CCP / BaridiMob / etc.), then mark the DZBuild order as
cancelledorreturned.
Stock consequence: moving an order to cancelled or returned returns its items to stock — but only if the order had already been confirmed. Stock is deducted at confirmation, not at order placement, so cancelling an order that is still pending changes nothing, because nothing was reserved.
Frequently asked
Q: I want to filter out fake orders by requiring prepayment. A: For physical-product stores there is no prepayment option today — most merchants combat fake orders with the Captcha Protection and Limit Orders Per IP addons, plus phone-confirmation in Advanced Orders.
Q: Can I accept BaridiMob / CCP transfers? A: Yes, but only on Digital Theme stores via the manual-receipt flow described above. On other themes, customers transfer to your account out-of-band and you mark the order as paid manually.
Q: When are SlickPay and Paddle involved? A: Only when you (the merchant) pay DZBuild — to subscribe to a plan, top up AI credits, activate a paid addon, or buy a domain. SlickPay handles CIB / Edahabia, Paddle handles Visa / Mastercard / PayPal / Apple Pay. Both checkouts are created on your dashboard, never on your storefront, and there is no setting to plug your own merchant account into customer checkouts.
Q: A customer paid via BaridiMob but my dashboard order is still pending. A: That's expected. Manual-receipt orders start with order status pending and payment_status pending, and stay that way until you open the order under Dashboard → Digital → Orders, check the screenshot, and mark it paid. There is no auto-verification.
Tips
Keep COD on Algerian-targeted stores. On non-Digital themes you couldn't remove it if you wanted to; on a Digital-theme store selling physical goods, replacing COD with manual-receipt only typically costs a large share of your conversions.
For digital products, lean on manual-receipt — Algerian customers are familiar with CCP and BaridiMob and trust them as long as your account info is clear.
Show the receipt-account info clearly in your storefront's payment instructions. The fewer questions the customer has to ask, the higher the success rate.
Verify receipts within 24 hours — the customer expects the digital download (or fulfilment) to start once they've sent the proof.
Use Captcha Protection to stop bot-generated COD orders before they reach your phone-confirmation queue.
What's next