Skip to main content

Header

Understanding the 7-Day Buyer Protection & Timelines

The BDX 7-Day Buyer Protection Program is designed to provide full financial safety when purchasing digital goods, game items, software keys, accounts, or top-up services on Bangladesh Digital Exchange (BDX.market).

Unlike instant physical marketplaces where products are physically handed over, digital items can sometimes carry hidden defects, region locks, or delayed revocation issues. BDX protection guarantees that seller payouts are delayed until you have adequate time to test and verify your purchase.

1. How the 7-Day Protection Window Works​

When a seller fulfills your digital order, they click Submit Delivery within the BDX order system and attach relevant delivery notes or proof. At that exact timestamp (delivered_at), the BDX engine initiates the 7-day buyer protection countdown window (protection_deadline).

During this 7-day protection period:

  • Escrow Hold Active: Your payment remains held in the safe BDX escrow pool. It is not credited to the seller's withdrawable wallet balance.
  • Verification Window: You have 168 full hours (7 days) to log into the account, redeem the key, verify in-game balances, check regional compatibility, or monitor subscription longevity.
  • Immediate Buyer Actions: At any point during these 7 days, you can choose to either Confirm Delivery (releasing funds early) or Open a Dispute (freezing funds indefinitely until reviewed).

2. Order Lifecycle & Status Progression​

Every order on BDX moves through a deterministic sequence of state transitions managed by BdxOrderState. Below is the complete timeline mapping from checkout to final completion:

[ pending_payment ] ──( Payment Upload / Verification )──> [ paid / awaiting_delivery ]
                                                                       │
                                                            ( Seller Delivers )
                                                                       â–¼
[ completed ] <──( 7 Days Elapsed / Auto-Complete )─────── [ delivered / awaiting_confirmation ]
      ▲                                                                │
      │                                                     ( Buyer Opens Dispute )
      │                                                                ▼
( Confirm Order )                                           [ disputed / payout_held ]

Stage Summary​

  1. pending_payment / awaiting_delivery: The buyer pays BDX first. The seller is notified to process the digital delivery.
  2. delivered / awaiting_confirmation: Delivery is submitted by the seller. The 7-day protection timer begins counting down.
  3. completed: The buyer clicks Confirm Delivery OR 7 days pass without any dispute being filed. The order status becomes terminal (completed), and funds transition to payable in the seller's wallet.
  4. disputed: The buyer opens a dispute during the 7-day window. The timer pauses, status locks to disputed, and funds stay on held.

3. Scheduled Automated Crons: Escalation & Auto-Closure​

BDX runs automated background service jobs (php artisan schedule:list) to monitor protection windows and enforce resolution deadlines strictly without human delay.

1. bdx:orders:auto-complete (Runs Daily at 02:00 UTC)​

  • Function: Scans all active orders where delivery status is delivered and delivered_at is older than 7 days (168 hours).
  • Rule: If no dispute has been opened by the buyer, the system automatically transitions the order to status = 'completed', updates payout status to payable, and releases funds to the seller.
  • Important Note: Once an order auto-completes, it enters a terminal state. Late disputes cannot be filed after auto-completion.

2. bdx:disputes:escalate (Runs Hourly)​

  • Function: Checks all open disputes where the seller response deadline (response_deadline) has expired (24 hours after dispute creation).
  • Rule: If the seller has not submitted an official response or evidence on the dispute within 24 hours, the cron flags the dispute status as seller_response_due and generates an urgent admin alert (dispute.seller_overdue). Admin can then resolve the dispute in favor of the buyer automatically.

3. bdx:disputes:auto-close-stale (Runs Daily at 07:00 UTC)​

  • Function: Cleans up abandoned or inactive disputes where seller responded and no further activity or appeal occurred within statutory limits.

4. Key Deadlines Summary Table​

Event / ActionDuration / DeadlineTrigger PointOutcome if Ignored
Buyer Protection Window7 Days (168 Hours)Seller clicks "Submit Delivery"Order auto-completes; funds released to seller.
Seller Dispute Response24 HoursBuyer opens a disputeDispute escalates to seller_response_due; buyer default refund eligible.
Dispute Appeal Deadline3 Days (72 Hours)Admin issues a dispute verdictVerdict becomes final and non-appealable.
Refund Method Link Expiry7 DaysBuyer wins dispute (Email signed link)Link expires; buyer must contact support for a new signed URL.

5. Best Practices for Buyers During the 7-Day Window​

To ensure maximum safety and avoid accidental loss of protection, buyers should follow these essential rules:

  • Test Immediately: Do not wait until Day 6 to test your product code or account details. Verify credentials as soon as you receive the delivery notification.
  • Do Not Confirm Prematurely: Only click Confirm Delivery if you have thoroughly tested the item and are 100% satisfied. Confirming delivery terminates your protection immediately and releases the money to the seller.
  • Keep Communication On-Platform: Always use the BDX order chat for all conversations, instructions, and screenshot uploads.
  • Monitor Notifications: Ensure your BDX account notifications and email address are active so you receive real-time updates if a seller replies to your dispute or submits redelivery.
Last updated on