From submission to a committed block
A transaction is final once the block covering its execution receipt is committed. Before that it passes through two earlier stages, and pax_sequencerReceipt reports which one it has reached.
Transaction progress on one network
- Submitted to Receipted: kernel executes
- Receipted to Committed: validators commit
| Rung | Required evidence | Application decision |
|---|---|---|
submitted | Transaction hash and nonce without a receipt | Track the existing submission. |
receipted | Signed execution receipt and consistent decoded fields | Inspect success or failure and the recorded effects. |
committed | Receipt covered by a committed block | Treat the verified outcome as final. |
| Parameter | Type | Notes |
|---|---|---|
txHashrequired | string | Pattern ^0x[0-9a-fA-F]{64}$ |
Documented in Agent-to-Agent Payments › Discover the agent card, Activities › Submitting and recovering, Agent runtime › Submission and receipt recovery, Local Protocol Emulator › What the emulator provides, Local Protocol Emulator › Read merged-network receipts, Finality & Commitment › Receipt commitment rungs
Recovery
When you do not know the outcome
Track the transaction you already sent and obtain its evidence before taking another economic action. A new transaction can repeat the intended payment.
Keep what you signed
Retain the signed transaction, its hash and its nonce.
Read the receipt
Call
pax_sequencerReceiptwith that transaction hash.Verify the signature
Check the signed receipt against the governed receipt keys from
px_getReceiptKeys.Check the covering block
Treat the outcome as final only once a committed block covers the receipt.
Release a paid resource only after checking the receipt against the expected payer, recipient, asset, amount and execution result, together with the block commitment your application requires. See payment release policies.
Ask next