Receipts

Every send returns a receipt. The receipt tells you which rail ran and how far the send has progressed. Neither "submitted" nor "pending" means confirmed.

Rail

rail is "native-gas" or "sponsored" on both chains. It is the only field that tells you which path actually ran. If your app promises fee-in-token, check it rather than assuming your configuration took effect.

EVM receipt

type Receipt = {
  id: string;          // txHash (native-gas) or userOpHash (sponsored)
  rail: "native-gas" | "sponsored";
  status: "pending" | "submitted" | "confirmed" | "failed";
  txHash?: Hex;
  chainId: number;
  error?: string;
};

Native-gas: id is a transaction hash; status starts at "submitted" (broadcast, not mined).
Sponsored: id is a userOpHash, an intent id, not a transaction hash; status is "pending" until the bundler reports a receipt.

Confirming

To advance a receipt’s status, poll the send engine’s status method, or the provider’s wallet_getCallsStatus. Only "confirmed" means the transaction is on chain. See Sponsor EVM sends.

Get started

Concepts

Guides

Reference

Rail

EVM receipt

Confirming

​Rail

​EVM receipt

​Confirming

Rail

EVM receipt

Confirming