> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polygon.technology/llms.txt
> Use this file to discover all available pages before exploring further.

# What is the Open Money Stack?

> One open stack for global money movement: fiat access, wallets, compliance, routing, and settlement in one vertically integrated, open platform.

The Open Money Stack is Polygon's open, end-to-end infrastructure for global money movement. It connects fiat access, wallets, compliance, routing, and settlement into one integration, designed to plug into existing systems and move money in seconds.

<Note>
  Need regulated rails, custodial infrastructure, compliance services, or a managed chain deployment? [Contact Polygon](https://info.polygon.technology/get-early-access).
</Note>

## The problem with fragmented stacks

Money should move reliably, at low cost. That requires predictable settlement without surprise deductions or delays.

Most institutions building stablecoin payment flows today take the same path: choose a compliance vendor, a wallet provider, a bridge, an off-ramp, and a chain. When they have what they like, they stitch these solutions together. Each integration requires independent maintenance.

In practice, this works, right up to the moment that volume grows or something goes wrong.

Then teams must debug an outage that lives somewhere between three vendors and a dozen systems.

## A different architecture

The Open Money Stack is **open and vertically integrated**: every layer is built to hand off cleanly to the next, with no lock-in.

And it's composable. If an institution only wants to use one aspect of the Open Money Stack, say Polygon Chain for settlement or just the wallet infrastructure, they can pick and choose.

**Use all of it, or only the components you need.**

## Settlement at the bottom of the stack

Most payments orchestration companies don't own the infrastructure they route on. They aggregate across vendors they don't control, adding margin at every layer. When settlement breaks, they call their vendor.

Polygon owns the settlement layer. The OMS is built on Polygon Chain: not as a dependency, but as infrastructure Polygon operates.

**\$54B in stablecoin transfer volume**, **159M unique wallet addresses**, **6.4B total transactions**, and an average transaction cost of **\$0.002**, with live integrations by Revolut, Stripe, Flutterwave, and more.

The economics compound at scale: costs improve as volume grows, rather than degrading through intermediary margin stacking.

## Unrolling the stack

<CardGroup cols={2}>
  <Card title="Wallet Infrastructure" icon="wallet" href="/wallets/embedded-wallets">
    1-click wallet creation with zero-config auth, passkeys, Smart Sessions, and enterprise-grade security. Custodial and non-custodial options both supported.
  </Card>

  <Card title="On-/Off- and Cash Ramps" icon="building-columns" href="/stablecoins-payments/onramps">
    Licensed fiat on- and off-ramps covering bank transfer, debit card, and cash at 50,000+ retail locations. KYC, AML, and compliance built in.
  </Card>

  <Card title="Cross-Chain Interop" icon="arrow-right-arrow-left" href="/trails/index">
    1-click transactions on any chain with any token. Deep unified liquidity across every connected network, with routing and bridging handled automatically.
  </Card>

  <Card title="Blockchain Rails" icon="server" href="/blockchain-rails/index">
    Polygon Chain for public settlement and Polygon Chain Development Kit (CDK) for dedicated rollup rails with 20,000+ TPS, compliance controls, and native Agglayer connectivity.
  </Card>

  <Card title="Stablecoin Orchestration" icon="coins" href="/stablecoins-payments/stablecoins">
    Enterprise payments infrastructure for stablecoins and tokenized deposits. Native USDC with no wrapping, no bridges, and no hidden deductions.
  </Card>

  <Card title="Agentic Payments" icon="robot" href="/payment-services/agentic-payments/x402/intro">
    x402 for pay-per-use APIs. ERC-8004 for onchain agent identity. Infrastructure for autonomous agent commerce without human approval at every step.
  </Card>
</CardGroup>

## Why integration changes the economics

Historically, each of these layers existed independently:

* Fiat access from one vendor
* Wallet infrastructure from another
* A bridge from a third
* Settlement from whichever chain you prefer

Every seam adds operational surface area. The Open Money Stack reduces that surface area.

With the full OMS, a complete payment flow looks like this:

1. **Funds enter** through regulated fiat rails
2. **They settle** into a smart contract wallet instantly
3. **Orchestration** routes across borders and networks as needed
4. **Polygon finalizes** the transfer in under two seconds
5. **The recipient off-ramps** into local currency through compliant infrastructure

Integration does not eliminate flexibility. Institutions can still extend, customize, and interoperate. They can pick and choose what they need. But they are not required to assemble foundational plumbing themselves.

**Integrate once. Customize as desired. Move money end-to-end, globally, 24/7.**

## Who it's for

* **Payment platforms and fintechs**: replace the patchwork of wallets, ramps, compliance, routing, and settlement vendors with one open stack at better economics
* **Fintechs and neobanks**: add stablecoin payment rails with embedded wallets, compliant onramps, and instant settlement in one integration
* **Enterprise payments teams**: reduce cross-border costs, unlock 24/7 settlement, and expand globally without assembling per-corridor bank relationships
* **Banks and financial institutions**: layer stablecoin settlement onto existing infrastructure without rebuilding core systems
* **Enterprises and marketplaces**: automate global payouts with programmable, auditable money flows and pay out counterparties anywhere instantly

## Next steps

<CardGroup cols={2}>
  <Card title="Explore use cases" href="/oms/use-cases">
    See how financial institutions are using the Open Money Stack.
  </Card>

  <Card title="Start building" href="/oms/quickstart">
    Pick a use case and follow a guided path into the docs.
  </Card>
</CardGroup>
