Payments

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.

DZBuild takes no commission on your sales. You pay for your plan and nothing else; whatever the courier or your bank charges is between you and them.

Card rails are for merchants paying DZBuild, not for customer checkouts

Merchant payments to DZBuild run on two card rails: SlickPay (CIB / Edahabia) and global cards (Visa / Mastercard / PayPal / Apple Pay, billed in USD). SlickPay covers all four purchases — plan subscriptions, AI credits, paid addons and domain purchases; the global-card rail covers plan subscriptions, paid addons and domains (AI-credit packs are bought on the local rail only). 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:

payment_method	When
cod	Cash on Delivery — the default, and the fallback for anything else on a physical order.
free_digital	A free digital product (lead magnet, free download). Checkout has no payment step at all.
digital_payment	Manual-receipt checkout on a Digital-theme store.

The storefront never offers a fourth option, and if some other value reaches the server from a storefront order it is stored as cod (or as free_digital when the delivery is digital). Orders created through the public API are stricter: an unrecognised payment_method is rejected with an error rather than quietly corrected, so send one of the three values exactly.

There is no card checkout for your customers

Your customers cannot pay you by card on your storefront. Not CIB, not Edahabia, not a global card, on any theme.

Both card rails in DZBuild live on your dashboard and sell DZBuild products: plans, AI credits, paid addons and domains. Neither can be pointed at your own checkout, and there is no setting anywhere that plugs a payment account of yours into your storefront. A customer who wants to pay before delivery transfers the money outside the platform and uploads the receipt, which is the Digital-theme flow described below.

Card checkout for buyers is planned. No date has been announced, so build your store around COD and receipts for now.

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. The courier pays you directly, on its own schedule. DZBuild is not part of that payout, so the cadence is the one in your contract with that courier.

How the customer experiences COD

1. Customer fills the order form (name, phone, wilaya, city, items).
2. Submits — order arrives in your dashboard as pending.
3. 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 a global Visa / Mastercard / PayPal card in USD. 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

1. The merchant configures one or more payment methods at /dashboard/digital/payment.
2. At checkout, the customer picks a method, transfers the money outside the platform, and uploads a screenshot of the receipt.
3. The order arrives with payment_method = digital_payment, an order status of pending, and a separate payment_status that also starts pending.
4. You verify the receipt manually and set payment_status to paid. Nothing is auto-verified.

Nobody checks that transfer for you. The money moves outside DZBuild, the screenshot is only proof, and the order sits at pending until you open it and mark it paid. Make reviewing that queue a daily habit: a customer who has paid and is waiting for a download will chase you, and DZBuild support cannot see or approve a receipt that was uploaded to your store.

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 cancelled or returned.

Stock consequence: moving an order to cancelled or returned returns its items to stock whenever they had been deducted. By default stock is deducted at confirmation, not at order placement, so cancelling an order that is still pending changes nothing, because nothing was reserved. A store set to deduct on receipt (Orders page, display settings gear, Stock deduction) gets the items back on cancellation even from pending.

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 the global-card rail 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, and the global-card rail handles Visa / Mastercard / PayPal / Apple Pay in USD. 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

• Orders — once a payment lands (or a COD order is placed), this is where you act on it.
• Customers — manage repeat buyers and ban bad actors.
• Captcha Protection addon
• Limit Orders Per IP addon