Give two vendors the same swap to demonstrate. A user chooses a token pair, inspects the amount they should receive, and approves the transaction. Then interrupt the flow. A quote can go stale while the wallet is open. A submission can time out after the transaction has reached the network. Those moments reveal who owns the work hidden in a proposal's “swap integration” line.
Name the supported mints, the quote provider, the user's slippage setting, and who submits the signed transaction. For a Jupiter integration, specify whether the team uses a provider-built order or assembles the transaction itself. The distinction affects which party can investigate a failed submission. Builderz Jupiter swap integration guide
Test a stale quote before signing
For this exercise, give the app a quote at noon and set a product rule that a quote is fresh for 20 seconds. At 12:00:22 the user returns to the app to confirm. The expected outcome is a refreshed quote with the revised output and a fresh opportunity to approve. This sample freshness window is a product decision. The transaction's blockhash has its own validity limit.
Run the test with a replacement quote that offers fewer tokens. Ask the person watching the demo to point to the new minimum output before approving. If they can only see the old amount, the demo has uncovered a specific change to price into the quote.
Test an ambiguous submission
Delay the submit response after the signed transaction leaves the app. The user refreshes and presses the swap button again. What does the interface know? It may have a signature and no confirmation yet. A timeout alone tells the team too little to construct a replacement transaction.
Ask the vendor to show where it stores the signature, how it looks up the original transaction, and what appears after a reload. Then repeat with an expired blockhash and a transaction known never to have landed. The first case should keep the original swap visible while its outcome is unresolved. The second should give the user a way to request another quote. Solana transaction confirmation and retry guide
Send support the same swap
Give a second team member a sample ticket: “I approved the swap, closed my browser, and my balance looks unchanged.” Hand them a reference they can search. From that reference they should be able to find the quote or order ID, token pair, expected output, submission time, and signature if one exists. Ask them to explain the displayed status using that record. Keep credentials and signed transaction payloads out of the ticket.
Use the three demonstrations as line items in the proposal. Each needs an owner, an observable pass condition, and a place to look when it fails. If one bid assumes the provider handles pending swaps, ask who will answer that sample ticket when the provider is unavailable. Solana DeFi development at Builderz



