Two counter observations can both mislead a payment enquiry
The Aptos account reference distinguishes sequenced transactions from orderless transactions. The latter use nonce-based replay protection instead of advancing the account’s sequence counter. An integration that only watches that counter can therefore miss activity. Do not apply an old sequence-number-only diagnostic to an operation without first establishing its transaction model.
The same reference explains that a committed sequenced transaction can execute or abort. Counting committed transactions is not a check that a particular transfer produced the intended recipient credit. For an APT to BTC purchase, the relevant question is what happened to the actual APT payment, not whether some activity advanced the sender’s counter.
Start with the payment hash supplied by the sender
- Preserve the original transaction reference
Copy the hash and original explorer link from the trusted sending record. Keep the network and exchange instruction alongside it. A screenshot of an account counter is useful context for an integration problem, but it should not replace the payment reference.
- Look up the specific transaction and result
AIP-123 documents lookup by transaction hash for orderless activity as well. Once a record is found, inspect its execution result and the intended APT movement. A transaction being present on-chain and its requested transfer succeeding are separate observations.
- Compare the actual payment with the instruction
Verify recipient and amount rather than selecting an arbitrary successful account transaction. If the input-side payment is established, move to the exchange record and Bitcoin payout. If it is not, report the exact unresolved state instead of interpreting the counter as proof either way.
A history endpoint can have a narrower scope than the account
The documented account-transactions endpoint returns committed sequence-number transactions and explicitly excludes orderless transactions. An empty result from that particular view is therefore not a universal statement that the account sent nothing. The AIP explains that clients relying on sequence progress need different handling for orderless payments.
This does not establish that your wallet uses orderless transactions. Ask the application responsible which model applies, or inspect the specific transaction record. The purpose of the distinction is to avoid a false diagnosis, not to prescribe a change to wallet settings or transaction construction when investigating money already sent.
What the observed record can actually establish
| Observation | Supported conclusion | Unsupported conclusion |
|---|---|---|
| Counter unchanged | No change in that observed counter | No orderless transaction committed |
| Counter increased | Sequenced account activity advanced it | The required recipient was paid successfully |
| Narrow account history empty | No records returned within that view and query | No payment of any supported model exists |
| Specific transaction and successful transfer identified | Evidence for that particular APT movement | Bitcoin payout already received |
Before authorizing another APT payment
- Resolve the original attempt first
- Keep pending, committed, successful and aborted observations distinct. Do not repeat funding solely because a counter-based script failed to notice it. If a lookup remains unclear, provide the original hash and exact response to the responsible wallet or exchange support.
- Keep replay protection out of payment support instructions
- You do not need to choose new sequence numbers or nonces to describe an existing transfer. Preserve its record and explain the observation. Creating a replacement transaction is a separate financial action, not a harmless way to test whether an account-history screen updates.
Aptos payment verification questions
- Does an unchanged sequence counter prove no Aptos transaction committed?
- No. Orderless transactions do not advance that counter. Establish the actual payment by its reference.
- Does a higher counter prove the required APT payment succeeded?
- No. A committed sequenced transaction can abort, and other activity can advance the counter.
- Does every account-history endpoint include orderless activity?
- No. The documented sequenced account-transactions endpoint excludes it. Check the specific view and transaction hash.
- Does this article require changing the wallet’s transaction model?
- No. It concerns interpreting existing records, not selecting replay protection or sending a replacement.
Official Aptos references
- Aptos account counter and committed transaction outcomes
- AIP-123: orderless transactions and hash lookup
- Aptos account history endpoint: sequenced scope
Reviewed: