Just hit a small bump in the road: make sure the token contract used for pricing the current service is consistent. When testing escrow payments, the buyer side showed a payment failure. Wallet balance looked sufficient, but the task pricing contract pointed to a different USDT, so the on-chain simulation directly flagged insufficient balance. When troubleshooting, don’t start by checking the UI balance. First, compare these 3 things: the token contract required by the task, the token contract for the deposited funds, and the balance read by the payment contract. If these three don’t match, no matter how good the balance looks on paper, the payment won’t go through. Fixing it is simple: either top up the correct USDT contract or swap the deposited assets into the contract required by the task.