Describe the observation before calling it a payment
| Observed record | What to inspect | What it cannot establish alone |
|---|---|---|
| Transaction hash in a wallet | Its network and actual execution result | Successful LINK delivery to the exchange |
| Failed execution status | The outcome attached to this exact attempt | A funded exchange order |
| Successful execution status | The matching LINK transfer, destination and amount | That every operation you intended was performed |
| Bitcoin payout reference | The output leg associated with the exchange | The identity of an unrelated earlier Ethereum attempt |
Execution status and the token payment are separate checks
Ethereum EIP-658 defines a receipt status indicating whether the top-level execution succeeded or failed. If the relevant attempt failed, do not describe it as a successful LINK deposit merely because the hash exists in a wallet history. Preserve that result as evidence when asking why the exchange still awaits payment.
For an attempt that succeeded, inspect the actual token movement rather than stopping at the success label. Identify the LINK contract for the selected network using Chainlinkโs official contract directory, then compare the transfer recipient and amount with the deposit instruction. The directory identifies the token; it does not supply your exchange receiving address.
Build a short trace without repeating a payment blindly
- Start from the exchange deposit instruction
Record which input asset and network were selected and which recipient was assigned. Keep that record linked to the order reference. Do not substitute a contract address copied from token documentation for the receiving details supplied by the exchange.
- Locate the exact outgoing attempt
Use the wallet reference for the operation you meant to send. Check that the explorer is on the corresponding Ethereum network and that the record belongs to this attempt. A different transaction made around the same time is not a substitute just because its status is successful.
- State the confirmed result precisely
Write whether the attempt failed, remains unresolved, or contains the expected LINK movement. If you cannot identify the movement, keep that as an open question. Do not fill the gap with a claim that the service has lost a successful payment.
What to include when the observations do not agree
A useful support note separates the order reference, the input transaction reference, the observed execution result and the intended token transfer. Add the relevant network and the discrepancy you found. Support can then inspect the right leg instead of comparing a Bitcoin payout screen with an unrelated Ethereum action.
If another attempt becomes necessary, first check the current order instructions and applicable limits with the service. Do not assume an old quote or deposit instruction remains usable indefinitely, and do not send again just to see whether the status changes. This page gives no gas-setting prescription or promised payout time. Keep account credentials and wallet recovery material outside the evidence you share.
Questions about a LINK funding attempt
- Is a transaction hash proof that my LINK deposit succeeded?
- It identifies an attempt. Check its execution outcome and the actual relevant token movement before describing the exchange as funded.
- Should I send LINK to the contract in the Chainlink directory?
- That directory identifies token contracts, not your order recipient. Use the current receiving instruction issued for the intended exchange.
- Does a successful execution label prove the correct deposit amount?
- Inspect the expected LINK transfer, recipient and amount as well. A status label does not establish every detail of the payment you intended.
Token and execution references
Reviewed: