Before signing

Validate the complete executable payload against the user request and independently configured signing trust. Check the wallet account, chain, token amounts, recipient, deadlines, and contract addresses. An indicative preview is not executable. Use the quote’s disclosed slippage allocation. An explicit slippageBps: 0 means zero tolerance. Omitted or null tolerance uses deployment policy.

Before retrying

Distinguish a deferred request from an unknown execution outcome. Follow submission recovery for EIN0052, EIN0053, and lost responses. Preserve the original identifiers after a wallet broadcast.

Before displaying completion

Distinguish upstream reports from chain observations. Top-level filled in upstream status is a reported fill indicator. Top-level filled in the on-chain fill view requires matching fills for every verified output. Origin settlement and destination delivery are separate events.

Before offering a refund

Read the effective refund deadline from the escrow. An extension can move that deadline beyond the signed expires value. Check that the order remains deposited before constructing a refund.

Deployment interfaces

The direct Infinity Hub service and the public gateway have different authentication and endpoint policies. Confirm gateway support before enabling same-chain reporting endpoints. Use the OpenAPI document served by the selected endpoint. For non-prepared signed quotes, the executable template remains in the quoting Infinity Hub process for 30 seconds. Route submission to that same replica. Prepared quotes store their templates in the shared event store and permit submission through another replica. Wallet-paid registration templates also persist across replicas and process restarts. These storage rules do not extend quote or order deadlines. SDK import paths identify separate client packages. The integration SDK and Infinity Hub’s JavaScript and TypeScript clients are not interchangeable packages. See SDK installation.