A Solana transaction signature identifies a submitted transaction, but the merchant still needs successful chain evidence. Coinvay’s native SOL verifier requests finalized transaction data and checks for the exact system transfer expected by the quote. Its simple confirmation label should not be interpreted as instant acceptance.
Understand what the verifier reads
Solana transactions contain instructions, and a successful native SOL payment must include the expected transfer to the recipient for the quoted lamport quantity. A transfer of an SPL token is a different instruction path and does not satisfy a native SOL quote.
For example, a conference attendee can pay a SOL invoice and provide the signature from their wallet. The organizer should not release the ticket solely because the signature looks well-formed; the transaction must be available in the required state and contain the correct payment.
Distinguish pending, failed and expired
A node may not yet return finalized data for a recently submitted signature. That can justify a waiting state rather than a rejection. A transaction with an execution error is a different case. Solana also uses blockhash-related transaction expiration, which is separate from a merchant invoice’s quote expiry.
These distinctions matter when a customer retries. Creating another transaction without checking the first can lead to duplicate transfers. Support should collect the actual signature and inspect its state before advising another payment. A browser timeout does not reliably establish whether the chain received the transaction.
Design the order integration around verified state
Keep the buyer informed that the payment is being checked. Preserve the invoice reference, selected network and signature in support records. In automated delivery, a server-side verified invoice or signed event should control fulfillment.
Coinvay’s current Solana acceptance is native SOL only. A finalized USDC transfer on Solana remains the wrong asset for that route. Broad statements such as accepts Solana payments should be accompanied by the concrete asset list so customers do not assume unsupported token transfers will be reconciled.
Practical checklist
- Collect the actual Solana transaction signature.
- Distinguish missing finalized data from an execution failure.
- Check native SOL instructions and exact lamports before fulfillment.
Common questions
Does the one-confirmation label mean the first observed signature is paid?+
No. The current verifier requests finalized data and validates the transfer. The UI’s compact count should not override those implemented checks.
If a wallet reports a timeout, should the customer resend immediately?+
First inspect the original signature and receiving state. A timeout can be an observation problem, and a second transfer could duplicate a payment that already succeeded.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.