CIB / Edahabia (Slick-Pay)

DZBuild integrates Slick-Pay to accept CIB and Edahabia card payments. This integration is used so you, the merchant, can pay DZBuild — for your subscription, AI credits, paid addons and domains — directly from your card.

For customer-facing storefront payments, see Cash on Delivery (physical stores) and, on Digital-theme stores, the Payment Gateway addon's receipt-upload methods.

For paying DZBuild without a card, see Manual receipts — a BaridiMob transfer to DZBuild's RIP plus a receipt upload.

What it covers

The Slick-Pay integration is wired into four flows on /dashboard/subscribe and related pages:

• Plan upgrades and renewals — Pro / Unlimited / Enterprise, for 1, 3, 6 or 12 months.
• AI-credit packs (/dashboard/ai-credits).
• Paid addons — the Digital theme's Payment Gateway and Secure Storage addons.
• Domain purchases (/dashboard/domains), whose payment references are prefixed DOM-.

When you click Pay with CIB / EDAHABIA in any of these flows, DZBuild creates a Slick-Pay invoice and redirects you to Slick-Pay's hosted page. After 3-D Secure, you're redirected back to DZBuild and the platform records the payment.

What you see

1. Open /dashboard/subscribe (or /dashboard/ai-credits / the addon page).
2. Pick the plan / pack / addon and the duration if applicable.
3. Click the Slick-Pay payment option (CIB / Edahabia).
4. You're redirected to Slick-Pay's secure page.
5. Enter your card details + 3-D Secure code.
6. You're sent back to DZBuild and your purchase activates as soon as the platform confirms the payment.

An interrupted payment can still be picked up, and the return link is what makes that reliable. The link that brings you back from Slick-Pay carries your payment reference in its address, so following it works in any tab and on any device: the subscribe page reads the reference, re-checks the payment and shows you the outcome. If you no longer have that link, reopening /dashboard/subscribe within 30 minutes in the same browser tab does the same job, because the tab remembers the reference for that long. Lose both and the payment sits pending until someone looks at it, so contact support with your reference rather than paying a second time. The global-card rail below behaves the same way.

Paying with a global card

DZBuild accepts global cards. The same checkout sheet carries a second card rail — Visa / Mastercard / PayPal / Apple Pay, accepted from anywhere in the world. Use it when you don't hold a CIB or Edahabia card with online payments enabled, or when you'd rather pay in dollars.

• It opens a secure in-page payment overlay instead of redirecting you to a hosted page.
• It is billed in US dollars, and the exact USD amount appears on the checkout before you confirm. A currency-conversion fee applies on the way from dinars to dollars, so the figure is a little above a straight conversion of the dinar price.
• It creates an auto-renewing subscription: each cycle renews automatically and stacks onto your plan expiry. Manage or cancel it with the Manage subscription button that appears on /dashboard/subscribe once you have a card subscription — it opens the subscription portal.
• Your plan activates as soon as the card payment is confirmed, normally within seconds; if the confirmation is delayed, reloading the subscribe page re-checks it.
• The global-card rail covers plan subscriptions, paid addons and domain purchases. AI-credit packs are bought on the CIB / Edahabia rail only.

It renews on its own

Unlike a Slick-Pay or BaridiMob payment, a global-card checkout is a recurring subscription, not a one-off. Cancel it from the subscription portal if you do not want it to renew.

Discount codes

The checkout sheet has a coupon field above the payment methods. Enter your code and apply it before paying — the discounted price is what the payment rail charges.

• Percentage codes are honoured on all three rails: Slick-Pay, the global-card rail and the BaridiMob receipt rail.
• Flat-amount codes work on the global-card rail only.
• The price is always recomputed server-side, so a code edited in the browser will not stick.

Payment confirmation

Confirmation is automatic and there is nothing for you to configure or connect. It happens two ways. When you come back from the payment page, DZBuild asks Slick-Pay for the invoice again and activates only if Slick-Pay reports it paid. Slick-Pay also sends DZBuild a signed notification of the result, and a notification whose signature checks out activates the purchase on its own, which is what saves the payments where you closed the tab before the redirect.

Refunds

• Local payments are final. A CIB or Edahabia payment, like a BaridiMob receipt, is not refundable once the plan is credited. Choose the plan and the duration before paying, not after.
• Global-card payments can be refunded within 14 days of the charge. Contact support with your payment reference inside that window; past it, the local rule applies.

Common issues

Symptom	Cause	What to do
Redirected back without confirmation	3-D Secure timed out or you closed the tab	Follow the return link again if you still have it, from any device. Otherwise reload /dashboard/subscribe within 30 minutes in the tab you started in. If it stays pending, contact support with your reference.
"Payment failed" on Slick-Pay's page	Most often the bank could not be reached, the payment was cancelled on the bank's page, the CVV was wrong, or the balance was short	Check the CVV and the balance, then retry. If the failure repeats with "cannot contact bank", it is the bank's side: wait a few minutes, try another card, or pay on the global-card rail.
Payment succeeded but plan didn't activate	Confirmation delayed	Wait a minute then refresh — the page re-checks the payment and reconciles it.
"A payment is already being processed" after double-clicking Pay	A duplicate-payment guard blocks a second checkout for 30 seconds	Not an error. Wait, and use the checkout that already opened.

Frequently asked

Q: Can I sell to my own customers via Slick-Pay through DZBuild? A: Not via DZBuild's own Slick-Pay integration today. The integration is wired for merchant-to-DZBuild payments. Your customers pay via COD, or — on Digital-theme stores with the paid Payment Gateway addon — by uploading a transfer receipt at checkout.

Q: Are my card details stored? A: No. DZBuild never sees your card number — Slick-Pay's hosted page handles it. DZBuild only stores a payment reference and the success/failure status.

Q: Which cards work, and why did mine fail? A: This rail takes Algerian CIB and Edahabia cards, and no global cards. When a payment fails, the reason is usually one of four: the bank could not be reached, you cancelled on the bank's page, the CVV was wrong, or there was not enough on the card. Fix the one that applies and retry; if the bank stays unreachable, use the other rail on the same checkout sheet, Visa / Mastercard / PayPal / Apple Pay, billed in US dollars and set up as an auto-renewing subscription.

Q: I bought Enterprise with extra staff seats by card — why is my seat limit unchanged? A: Neither card rail raises your staff-seat limit automatically. Contact support after paying so the extra seats are applied. Paying by BaridiMob receipt does apply them, because our team sets the seat limit when it approves your receipt.