Skip to main content

Manual receipts

Pay for your DZBuild plan by BaridiMob transfer and upload the proof — verified and activated by our team, usually in under an hour.

Written by Support

Manual receipts are how merchants pay DZBuild without using a payment card. You transfer the price via BaridiMob, upload the receipt in your dashboard, and our team verifies it and activates your plan — usually in under an hour.

Manual receipts appear in two different places:

  1. Merchant → DZBuild — paying for your own plan by BaridiMob transfer. That is what this page describes.

  2. Customer → merchant, on Digital-theme stores only: with the paid Payment Gateway addon you define your own CCP / BaridiMob / RedotPay / custom accounts at /dashboard/digital/payment, and customers upload a transfer receipt at checkout for you to review before you confirm the order. Each method can carry an extra-fee percentage that is added server-side to the customer's total. Physical stores have no receipt checkout — they use Cash on Delivery.

Manual receipts cover plan upgrades and renewals only (Pro / Unlimited / Enterprise) at /dashboard/subscribe. AI credits, paid addons and domains can no longer be bought with a receipt — since 21 July 2026 those are instant-card-only (CIB / Edahabia via Slick-Pay, or Visa / Mastercard / PayPal / Apple Pay via Paddle); a receipt request for them is rejected outright.

When to use it

  • You don't have a CIB / Edahabia card with online payments enabled, and you don't want to use the international-card rail.

  • Your card was declined and you want to pay another way.

  • You prefer keeping a paper trail outside the card rails.

How it works

  1. Pick the plan and duration.

  2. Open the BaridiMob payment method on the sheet. It is the only manual option — there is no CCP tab and no generic bank-transfer option. The panel shows DZBuild's RIP (00799999002871122994) with a copy button; the amount to send is the total in the order summary above it.

  3. Send the money from your BaridiMob app.

  4. Capture the receipt that confirms the transfer.

  5. Come back to the page and upload the receipt.

  6. Submit. Your request goes into the queue with status pending.

  7. Our team verifies the transfer against the destination account and activates your plan — usually in under an hour (up to 24 hours at the outside, overnight or at weekends). The BaridiMob tile itself promises approval in under an hour.

Plan requests appear in the payment-history table at the bottom of /dashboard/subscribe. It loads a moment after the page and then pages 10 rows at a time. A rejected request shows our team's reason as a note on its row.

What to put on the receipt

The receipt should clearly show:

  • The destination account / RIP you transferred to.

  • The amount sent — it must match the amount on the page exactly.

  • The transfer date.

  • A reference / transaction ID if your provider shows one.

Accepted formats: JPG, PNG, GIF, WEBP or PDF, up to 10 MB, one file per request. Renaming a file does not help — the type is detected from the file's actual contents, and anything that is not a real image or PDF is rejected on upload.

If any of these are missing, our team may ask for a fresh receipt before activating.

Discount codes

A percentage discount code entered in the coupon field on the checkout sheet is honoured on the BaridiMob rail too. Apply it before reading the amount to transfer: the server recomputes the expected price, so a receipt for the undiscounted figure will not match.

How long you get

A receipt-paid subscription is credited as duration × 30 days (so 12 months = 360 days), while a card payment adds calendar months. Either way the time stacks on top of an unexpired plan, and switching to a different plan mid-term converts your remaining days by price ratio instead of discarding them.

Common reasons a request gets rejected

Reason

Fix

Amount doesn't match

Send the remainder and upload the receipt that shows the total, or contact support with both transaction references — a request holds exactly one receipt file, so two partial screenshots cannot be combined.

Wrong destination account

The transfer didn't reach us — go back to BaridiMob and re-issue it to the RIP shown on the page.

Receipt unreadable / cropped

Re-upload a full, sharp capture. Photos of the screen are fine if legible.

No transaction reference visible

Re-upload a capture from your BaridiMob history that shows the transaction together with its reference.

After submitting, you cannot submit another manual request for the same store for 30 minutes (the cooldown applies while an earlier request is still pending or rejected), and no more than 3 requests in any 5-minute window. If you need to correct a receipt sooner, contact support instead of resubmitting.

You are emailed when a request is approved. You are not notified when one is rejected — the reason appears only as a note on the rejected row in the payment history, so check /dashboard/subscribe yourself if activation hasn't arrived. Your money isn't lost — it's still in your BaridiMob account until you re-submit a clean receipt.

Frequently asked

Q: How long does activation take? A: Usually in under an hour; up to 24 hours at night or on weekends.

Q: Can I split a payment across two transfers? A: Not in one request — a request holds exactly one receipt file. Send the full amount in a single transfer whose receipt shows the exact price. If you have already sent a partial amount, send the remainder and upload the receipt showing the total, or contact support with both transaction references. Remember the limits: one manual request per store every 30 minutes, and at most 3 requests in any 5-minute window.

Q: Where do I see whether my receipt was approved? A: In the payment-history table at the bottom of /dashboard/subscribe — it loads a moment after the page, pages 10 rows at a time, and shows each request's status (pending, completed, rejected) and timestamps.

Q: Is there a fee on manual receipts? A: DZBuild charges no extra fee. BaridiMob may charge its own transfer fee on your side.

Did this answer your question?