Skip to main content

Header

Withdrawal Requests & Seller Eligibility

BDX.market enforces verification policies, trust qualifications, and administrative workflows to safeguard financial operations. Sellers must fulfill explicit eligibility requirements before withdrawing available earnings.

This document outlines the step-by-step submission lifecycle, eligibility checks, verification rules, error handling behavior, and administrative processing actions for seller payouts.

1. Prerequisites & Seller Eligibility​

Before a seller can submit a payout request, the system executes five mandatory verification checks:

 Payout Request Submission Flow
 ├── 1. Store Ownership Verification
 ├── 2. Identity & Account Verification
 ├── 3. Minimum Completed Orders Trust Requirement (1 completed order)
 ├── 4. Minimum Withdrawal Amount Requirement (500 BDT)
 └── 5. Net Available Balance & Open Dispute Reserve Check

Check 1: Store Ownership Authorization​

The authenticated user must be the verified owner of the seller profile. Delegated store managers without full financial administration permissions are blocked from submitting payout requests.

Check 2: Identity & Account Verification​

The seller profile must complete required identity verification steps before payouts are unlocked. This prevents unauthorized account drains and maintains compliance with digital commerce guidelines.

Check 3: Completed Orders Requirement​

To prevent abuse from new unverified seller accounts, BDX requires sellers to complete at least one successful marketplace order before initiating a payout request.

Check 4: Minimum Payout Threshold (500 BDT)​

Minimum withdrawal threshold is 500 BDT. Requests below 500 BDT are rejected automatically with a clear notice.

Check 5: Net Available Balance & Dispute Collateral​

The requested withdrawal amount must not exceed your available balance minus any active dispute reservations:

Max Allowed Payout = Available Balance - Open Dispute Reservations

2. Payout Request Statuses​

A withdrawal request progresses through discrete statuses:

                  ┌──────────────┐
                  │  requested   │
                  └──────┬───────┘
                         │
             ┌───────────┴───────────┐
             ▼                       ▼
      ┌──────────────┐       ┌──────────────┐
      │   approved   │       │   rejected   │
      └──────┬───────┘       └──────────────┘
             │
             ▼
      ┌──────────────┐
      │     paid     │
      └──────────────┘
StatusDescriptionBalance Impact
requestedInitial state upon submission by seller. Awaits administrative review.Deducted from spendable balance while under review.
approvedIntermediate state set by admin prior to disbursement batch execution.Held for payout processing batch.
paidFinal completed state. Dispatched via chosen MFS or bank channel.Marked as fully processed; ledger updated.
rejectedDeclined by administration (e.g., invalid account number, policy issue).Deduction removed; funds return to available balance.

3. Step-by-Step Submission Lifecycle​

Step 1: User Request​

The seller selects a payout method (bkash, nagad, rocket, bank), inputs the account number and optional label, specifies the BDT amount (minimum 500 BDT), and submits the form on the Seller Dashboard.

Step 2: Verification & Processing​

The system locks balance records, verifies available funds against active disputes, and logs the withdrawal request into the payout processing queue.

Step 3: Notifications​

  • Seller Notification: An in-app alert and email confirm receipt: "Your ৳[amount] payout request is with BDX admin for processing. You will hear back within 1–2 business days."
  • Admin Alert: An alert is dispatched to platform compliance staff to queue the withdrawal for batch execution.

4. Administrative Processing & Mark-Paid Execution​

Platform administrators manage payout requests during the twice-weekly payout cycles (Mondays and Thursdays).

When an administrator completes the money transfer via MFS or bank transfer:

  1. The request status is updated to Paid.
  2. Order payout statuses are updated to released.
  3. The seller receives an automated email and in-app notification confirming transfer completion.

5. Handling Rejected Payouts​

If a payout request contains invalid financial details (such as an incorrect MFS number or full recipient wallet):

  1. Rejection Notice: Support staff mark the request as rejected and append an explanatory note (e.g. "bKash personal wallet limit reached").
  2. Funds Restored: Rejecting a request immediately unlocks the funds, returning them to the seller's spendable balance.
  3. Notification: An alert informs the seller to update payment details and re-apply.

Summary Troubleshooting Checklist for Sellers​

Issue / Error MessageRoot CauseSolution
"Minimum payout request is 500 BDT."Requested amount is under the 500 BDT threshold.Increase withdrawal request amount to at least 500 BDT.
"You need at least 1 completed order(s)..."Account has 0 completed sales.Complete at least one marketplace order successfully.
"Only X BDT is ready to withdraw. Y BDT is still clearing."Funds are held in post-completion safety clearing.Wait until the clearing countdown timer on dashboard reaches zero.
"Cannot payout: you have open disputes..."Balance is reserved as collateral for an active buyer dispute.Resolve open dispute with buyer or wait for admin arbitration.
"Too Many Requests"Rapid submission limit reached.Wait 60 seconds before submitting another request.
Last updated on