Begin with the transfer you actually submitted
Open the sending wallet or exchange record for the transfer linked to your Approval Plus request. Note the asset, selected network, amount and submission time before copying anything. Keep the account funding reference in a separate field. An exchange’s internal withdrawal reference or a merchant’s order number is not automatically the public transaction hash; use the label and explorer link supplied for the on-chain transfer.
MetaMask lets you open a transaction in Activity, copy Transaction ID and choose View on block explorer. Use the corresponding documented route in your own sending service rather than guessing another app’s menu. If a transfer is still awaiting submission and no on-chain identifier is available, record that state and ask the sending service about it instead of inventing a hash.
Sources & further reading: [1]
Confirm the network before interpreting a search result
Keep the network selected in your original request beside the network used for the transfer. Open the explorer from a trusted wallet record or the network’s official documentation. Do not choose a similarly named chain because the address begins with the same characters. An empty search result on one explorer does not establish what happened on another network.
Build a small reconciliation note with five fields: account request reference, actual transfer network, complete hash, asset and amount. Leave an unknown value explicitly unknown until you can verify it. Avoid shortening the hash in the support message; a cropped screenshot can look convincing while omitting the identifier needed to locate the record. Read-only inspection of a public record does not require sharing a wallet recovery phrase.
For a mismatch report, label two columns: requested route and observed transfer. Put the account request reference, required asset, network and recipient in the first; put the actual chain, transfer hash, asset, recipient and amount in the second. Mark any field you cannot verify as unknown. Send the comparison through the website support channel without describing a proposed recovery as already completed.
Separate the transaction destination from the token recipient
Ethereum’s explorer documentation distinguishes transaction To, which can identify a contract, from tokens transferred. When reviewing a token payment, find the transfer entry for the intended asset and compare its recipient with the address shown in the account request. Do not assume that the first To field on a contract transaction is the final token recipient.
For an illustrative record, you might see a contract interaction and a separate line moving 50 units of the selected token to the requested address. Compare the entire recipient and the exact asset, not just the token symbol or a familiar address ending. If the transaction contains several transfers, identify the one connected to your request; do not add unrelated token movements into the funding amount.
Read the amount and observation time together
Record the token amount actually shown in the relevant transfer entry, then compare it with the request instructions and the sending service’s receipt. Keep any network fee separate from the token amount received. If a request calls for 50 units and the receipt shows only 49 delivered after a withdrawal deduction, write down that mismatch rather than describing it as an exact payment.
Also note when you checked the status. A screenshot captured while a transfer was pending is an observation at that time, not a permanent description of the record. Reopen the same hash when updating support and report the new status without replacing the original request reference. Do not make a second transfer merely to create a newer screenshot while the first one remains unresolved.
Match the evidence to the account’s verification workflow
Approval Plus receipt verification is handled by the team before account credit. A successful blockchain record is evidence to reconcile, not an automatic account balance update or proof that every request field matched. Check the request’s own status separately. Keep the complete hash, network, token, amount and receiving address together when asking about a payment that has not yet been credited.
The funding window is 15 minutes. If you already paid and the request expires before verification, follow the account’s refund-request form with the original hash and your own refund address on the same network, plus a memo or tag when your receiving service requires one. Submitting that form is a request for review, not proof that a refund was sent or a promise of its arrival time.
Your questions, answered
Does a successful explorer status mean my Approval Plus balance is credited?
No. Read the account request status separately. The team verifies the receipt and matches the transfer to the request before crediting it.
Is the first To address always the person receiving a stablecoin transfer?
Not necessarily for a contract transaction. Inspect the relevant token-transfer entry and compare its recipient with the request address.
What if my exchange shows only a withdrawal reference?
Look for its on-chain transaction hash or explorer link. If the transfer has not been submitted or no hash is provided, keep the internal reference and ask the sending service about that specific record.
Sources & further reading
- MetaMask: find and copy a transaction ID ↗Checked Nov 16, 2026
- Ethereum: transaction and token fields in block explorers ↗Checked Nov 16, 2026
- Approval Plus: account, funding and support help ↗Checked Nov 16, 2026
- Approval Plus: support contacts ↗Checked Nov 16, 2026