Sequence

• Name: Sequence
• URL: https://sequence.xyz/
• Category: wallet, payments, and indexed-data control plane
• Tags: ethereum-ecosystem
• Summary: Sequence is a broad wallet, checkout, and data stack. The wallet brand is not the main analytical point. The leverage is in payment routing, sponsorship defaults, merchant packaging, and indexer coverage. The named operator boundary around OMS packaging, wallet infrastructure sales, Trails routing distribution, and the newly Polygon-shaped commercialization path now deserves its own read in polygon-labs.
• What it does:
  • Provides smart-wallet products for developers and ecosystems, including ecosystem-hosted wallet deployments and embedded-wallet integrations
  • Offers cross-chain payment tooling through Trails plus adjacent commerce products such as Shop, Marketplace, and Checkout SDK flows
  • Exposes a production read layer through its Indexer, covering balances, transfers, NFTs, prices, contract events, subscriptions, and webhooks across EVM chains
  • Publishes broad API and SDK surfaces across web, Node.js, Go, Unity, Unreal, indexer, analytics, builder, and CLI tooling
  • Sells into gaming, stablecoin, DeFi, and ecosystem distribution rather than one narrow wallet niche
• Key claims:
  • The homepage describes Sequence as the stack for crypto wallets, one-click cross-chain payments, and real-time web3 data
  • Wallet docs describe a complete non-custodial smart-wallet experience and distinguish ecosystem-hosted wallet deployments from older embedded-wallet patterns
  • Payments docs recommend Trails for cross-chain payments from any wallet and token, including the routing needed before destination-chain execution
  • Indexer docs position the product as a production read layer with low-latency cross-chain balances, transfers, pricing data, subscriptions, webhooks, and a stated 99.99% uptime target
  • The docs index and GitHub organization show a much broader surface than a simple wallet SDK
• Whitepaper: No whitepaper or litepaper was found during this pass. The strongest primary materials were the official site, docs home, wallet/payment/indexer docs, docs index, and GitHub organization; see ../whitepapers/sequence-primary-sources-2026-04-25.md.
• Sources:
  • https://sequence.xyz/
  • https://docs.sequence.xyz/
  • https://docs.sequence.xyz/llms.txt
  • https://docs.sequence.xyz/solutions/wallets/developers/overview
  • https://docs.sequence.xyz/solutions/payments/overview
  • https://docs.sequence.xyz/solutions/indexer/overview
  • https://github.com/0xsequence

Internal linkages

• Company / operator boundary for OMS packaging, Polygon-branded wallet infrastructure sales, and the broader routing-plus-settlement commercialization path: polygon-labs.
• Keep the note on the broad control-plane cuts: alchemy, coinbase-developer-platform, and safe.

Protocol / company boundary

• Keep this note on the Sequence product surface: smart-wallet provisioning, checkout and merchant packaging, Trails-style cross-chain routing, sponsorship defaults, and indexer/data coverage.
• Use polygon-labs when the sharper question is who is now trying to package Sequence into a one-stop wallets + routing + settlement + ramps operator shell through Polygon’s Open Money Stack story.
• That split matters because what does Sequence expose to developers and users? and which company is increasingly turning that surface into part of a larger payments stack? are related but not identical questions.

Control surface

• The wallet contracts and checkout-triggered transfers still land on external chains, but that is not the main cut.

• The leverage sits in Sequence’s service layer: wallet provisioning, payment routing, sponsorship defaults, indexer coverage, analytics, and merchant-facing checkout packaging.

• The company shell above that surface now matters more than before because Sequence is being marketed as part of Polygon’s broader OMS packaging rather than as a fully standalone wallet/data vendor.

• Treat Sequence as a broad wallet-and-data control plane, not as a neutral wallet shell.

• Last reviewed: 2026-08-10 UTC