Paying With Crypto on ZulHub: What You Need to Know
You do not need to connect a wallet. You do need to get the network right.
Paying for a trade on ZulHub does not require connecting a wallet, installing anything, or signing a transaction in a browser. You send a normal transfer from wherever you already hold funds — an exchange account or a wallet app — and the platform verifies it on-chain.
This guide covers what to check before you send, and what happens afterwards.
What ZulHub never asks for
ZulHub does not ask for, receive or store private keys, seed phrases, recovery phrases or wallet passwords. There is no legitimate reason for any platform to request them, and no feature on ZulHub requires them.
If anything claiming to be ZulHub asks you for a recovery phrase, it is not ZulHub. Stop and report it.
Saved addresses in your account settings are public addresses only. Saving one does not prove you control it, and the platform says so plainly rather than implying otherwise.
Before you send: four checks
The trade page shows four things. Check every one against what you are about to do.
Network. This is the check people skip and the one that loses money. USDT on TRON and USDT on BNB Smart Chain are different tokens on different networks that happen to share a name. Sending on the wrong network means the funds do not arrive at the destination the platform is watching, and recovery is usually not possible.
Token. Only the exact configured token counts as payment for the trade. A different token arriving at the destination is recorded as an anomaly and does not fund the trade.
Destination address. Compare it against the trade page. The destination is fixed for the life of the trade and does not change. If you receive a different address through a message, an email or any other channel, it is an attempt to redirect your payment.
Amount. Send the exact amount shown. A small shortfall inside the platform tolerance is accepted, which covers exchange withdrawal fees shaving a few units off the transfer. A larger shortfall does not fund the trade.
After you send
You do not need to tell the platform you paid. There is deliberately no button that does that, because a claim of payment is not evidence of payment.
ZulHub queries the blockchain and checks the transaction independently: that it exists, that it did not revert, that it reached the right destination, that it was the right token on the right network, that the amount matches, and that it has enough confirmations for that network. Only when all of those hold does the trade become funded.
Confirmation times vary by network. The trade page shows the current confirmation count against the number required, so you can see progress rather than guessing.
When something goes wrong
Wrong network. The platform cannot see the transfer, because it is not on the chain being watched. Contact support with the transaction hash. Whether recovery is possible depends entirely on the networks involved and is often not.
Wrong token. The platform records what it observed and tells you the transfer did not fund the trade. Do not send more until this is resolved.
Underpaid. The trade stays unfunded and the shortfall is shown. Sending the difference is usually the simplest resolution.
Overpaid. The trade funds normally and the surplus is surfaced so it can be returned deliberately rather than quietly kept.
Paid after the deadline. A late payment does not silently vanish. It moves the trade into a reconciliation state so a human can look at it, rather than being ignored because a timer expired.
Why amounts are handled the way they are
Token amounts on ZulHub are stored and compared as exact integers in the token base units, and read as arbitrary-precision integers in code. Floating-point arithmetic is never used for anything that settles.
This is not pedantry. A token with eighteen decimal places produces values that a standard floating-point number cannot represent exactly, and a rounding error in a payment comparison is a real financial bug. Doing the arithmetic in integers is the only way to be sure the amount compared is the amount sent.
What is not automated yet
On-chain escrow — where a release moves funds automatically under a 2-of-3 arrangement between buyer, seller and arbitrator — requires a deployed and audited contract on each network. That is not in place yet, and ZulHub does not pretend otherwise.
Payment verification is fully real and automatic today. Settlement is currently performed by an authorised operator against a recorded arbitration decision, with the full audit trail attached. The networks page shows the exact readiness of each chain and what is blocking automatic settlement on it.