Check both the transaction's error result and its commitment status before deciding what happened.
Submission is an observation
A transaction signature identifies a signed Solana transaction, but having that signature does not establish successful on-chain execution. A submission endpoint can acknowledge a request before its eventual outcome is known. Applications should preserve the signature and query the transaction's status rather than turn a successful submission response into a completed-payment message. A connection timeout similarly does not prove that the transaction never reached the network.
Status has more than one dimension
Solana status responses can include a confirmation status and an error field. Processed, confirmed and finalised describe increasingly strong commitment observations; the error field describes execution failure. A transaction can reach a strong commitment state while still having failed its requested operation. Conversely, a null status response means the queried service did not return a matching status in its search scope, not a universal proof that no transaction exists.
A cautious retry example
Imagine a customer submits a payment and the wallet loses connectivity. The customer should first recover the signature and inspect status and account changes through a reliable route. Constructing a fresh payment immediately could produce a second transfer if the first succeeded. For software, an internal payment identifier should connect attempts to one business intent. Reconciliation must distinguish retransmission of an existing signed transaction from a newly signed transaction representing another possible payment.
Investigate the whole lifecycle
Record the selected commitment level, observed error, blockhash validity context and receiving application's credit status. Historical searches may require a different query scope or service capability. If the transaction expired without landing, rebuilding may be appropriate only after that outcome is established. If it succeeded, investigate the recipient or indexer instead. Ask support to reconcile the specific signature and intended transfer; never share a seed phrase. Precise status language prevents a temporary visibility problem from becoming a duplicate payment.
Sources & context
Sources checked 7 October 2026. This is explanatory coverage, not personalised investment advice. Our corrections policy.
PactVerity