Skip to main content

Header

Payment Operations & Troubleshooting Guide

This operational manual covers diagnostic routines, error resolution procedures, payment reconciliation strategies, administrative controls, and refund handling for BDX.market payment operations.

1. Payment Webhook Debugging & Verification​

When external gateway transactions fail to settle automatically, administrators inspect system logs and execute manual re-verification routines.

Webhook Event Flow​

All external payment gateways invoke central payment verification endpoints:

POST /payments/webhook/{provider}
  ├─ Provider Route Security (only authorized providers accepted)
  ├─ Payment Gateway Manager processes webhook payload
  ├─ Cryptographic Signature & Verification Check
  ├─ Verify Order Total Match
  └─ Apply Result & Update Order Status

Gateway Re-Verification Actions​

If a webhook fails due to temporary network failure or timeout, administrators can trigger server-to-server gateway re-verification without asking the buyer to re-submit payment:

  1. Locate the pending payment reference in the administrative payment dashboard.
  2. Initiate a manual gateway verification check for the transaction.
  3. Upon successful verification, order escrow is activated and the buyer is notified instantly.

2. Common Payment Scenarios & Resolutions​

A. Payment Amount Mismatch​

  • Scenario: The buyer altered the transaction amount during external gateway checkout, or a payment fee was miscalculated.
  • Resolution: Compare the payment transaction record with the order total. If underpaid, the transaction is rejected and refunded or flagged for top-up. If overpaid, the balance is adjusted manually by support staff.

B. Verification Signature Errors​

  • Scenario: API credential mismatch or corrupted payload decryption key.
  • Resolution: Verify provider credentials in your payment settings. Ensure server proxy settings do not strip custom security headers.

3. Dispute Resolution & Refund SOP​

When a buyer opens a dispute or requests an order cancellation, escrow funds are handled according to BDX buyer protection policies.

[Dispute Filed by Buyer within 7 Days]
                 |
                 v
   Seller Given 24-Hour Notice to Respond
                 |
                 +---> Seller Resolves / Delivers Replacement -> Buyer Closes Dispute
                 |
                 +---> Seller Fails to Respond OR Item Proven Invalid
                          |
                          v
                 Admin Reviews Evidence in Support Dashboard
                          |
                          v
                 Execute Refund to Buyer BDX Wallet Balance

Refund Execution Standard​

Refunds process directly back to the buyer's internal BDX Wallet balance, regardless of whether the original payment method was bKash, Nagad, Rocket, Bank Transfer, or BDX Wallet. This provides immediate buyer liquidity, 0% cash-out/processing fee loss for the buyer, and instant availability for future purchases across the marketplace.

4. System Reconciliation & Health Audits​

To ensure ledger integrity across buyer balances, seller payout holds, and marketplace commission metrics, automated verification checks run regularly:

  • Pending Payment Verification: Inspect manual payment proof submissions requiring staff review.
  • Order Auto-Completion: Automatically completes orders delivered over 7 days ago without open disputes and releases funds into seller clearing balances.
  • Dispute Escalation Checks: Identifies disputes where sellers failed to respond within 24 hours and flags them for administrative review and refund.
Last updated on