Polygon Open Money Stack: Payments, Revenue and POL

Analysis date and evidence cutoff: November 5, 2026.

Polygon Open Money Stack, or OMS, combines accounts, wallets, fiat access, conversion and transaction routing for businesses moving money. Its commercial economics depend on customer contracts, provider costs and the capital needed to deliver payments. Its connection to POL depends on where transactions execute and how eligible network revenue is distributed.

Public evidence supports the product architecture and several possible revenue sources. It does not establish OMS's current paid volume, revenue, profit or acquisition payback. The financial scenarios below are explicitly hypothetical.

What The Stack Contains

OMS packages several functions behind a common product experience. A business can use individual layers or combine them into a payment flow; adopting OMS does not require using every component. Polygon's September 9 product explanation describes the integrated architecture.

Sequence contributes smart-wallet infrastructure, permissions and authentication. Trails contributes orchestration that can combine swaps, bridges and execution. These products also serve applications outside the complete OMS package. Their integration into Polygon's payments offering is described in Polygon's Sequence wallet explanation.

The Technology Operator And Financial Providers

The OMS terms, version 1.3, dated August 3, 2026, name Polygon Labs Services (Delaware) Inc. as the technology operator. They distinguish it from the regulated providers handling financial services.

The document identifies Coinme, Inc., Erebor Bank, N.A. and Cross River Bank as providers for applicable services. Cross River's role is described through its banking relationship with Coinme. The terms give providers their own onboarding relationships, obligations and discretion over services. Naming a bank in this document does not establish that every OMS customer has access to all of its products.

The PDF also contains historical licensing information. It should not substitute for a current state-by-state or route-specific availability check. The acquisitions and Coinme's operating obligations are covered separately in Polygon, Coinme and Sequence acquisitions.

How An OMS Payment Moves

A customer is an identity record with permission to use particular instruments and services. A wallet or registered bank account is a source or destination. A transaction is the commercial money movement; its transfers describe the individual movements across banking or blockchain rails.

For an ordinary quoted payment, the flow is:

1. Establish the customer's identity, permitted services and payment instruments.
2. Obtain a quote for the amount sent or the amount the recipient should receive.
3. Accept the quote and initiate the transaction.
4. Follow its transfers and status until delivery, failure or an action requiring attention.

A single transaction can therefore involve multiple transfers. A blockchain hash, bank reference and internal transaction record describe different parts of the same payment. Adding them together would overstate commercial volume. The transaction documentation explains this distinction and the status model.

Deposits Can Start The Flow Automatically

A virtual account gives a customer bank deposit instructions. When money arrives, OMS can create a transaction automatically, convert it for a crypto destination, forward it to a bank destination or credit a USD balance. These flows are priced on arrival rather than through an earlier locked quote. A walletFiat destination can receive an internal book transfer, with no mandatory blockchain leg in that option. See the virtual-account guide.

For pooled custody, the omnibus guide describes named user wallets, attribution of deposits and transfers into a business-controlled omnibus wallet. Sweeps are initiated by the integration or by deposit forwarding. A customer ledger entry, a sweep and a final payout are not interchangeable measures of activity.

Fees: OMS, Developer And Gas

The quote documentation separates three known fee categories:

The documentation's $100-to-$99.42 example illustrates the response format. Its $0.35 OMS fee is not a published 35-basis-point tariff. Quotes normally have a short validity window, with 30 seconds given as the default.

Gas sponsorship can move the cost to OMS without showing a gas fee in the customer's fee array. An absent line item does not establish zero execution cost. Section 5.2 of the OMS terms also distinguishes Polygon's charges from regulated-provider and banking charges.

Pricing Evidence Does Not Establish A Universal Rate

The public material reviewed did not provide a complete OMS rate card, enterprise minimum, setup charge or bank/provider revenue-share schedule.

A July 30 commercial explanation describes at-par transfers and monthly invoicing, using $10,000 per month to move $100 million as an illustration. It does not disclose a signed customer agreement, corridor or contractual limits. Polygon's claim of all-in costs below 1% likewise does not specify OMS's retained margin.

Subscription, percentage and per-payment charges may be alternatives or a negotiated combination. They should only be added when the assumed contract explicitly includes each component.

Trails has a separate commercial model. Its pricing documentation describes ordinary integration without setup or monthly integration fees, with transaction-time gas, bridge/liquidity-provider fees and a Trails protocol fee. The Sequence Payments FAQ describes sharing transaction fees with developers. Wallet subscriptions or illustrative Builder tariffs cannot automatically be applied to Trails volume.

Networks, Currencies And Availability

The current currencies-and-rails documentation lists USDC and USDT and these crypto-network identifiers: Polygon, Ethereum, Base, Solana and Tron. Fiat instruments include USD and CAD, with US bank rails, SWIFT, Canadian local delivery, debit cards and cash described for applicable routes.

That catalog is not a promise that every asset works on every network for every account. The enabled route depends on the project, customer permissions, instrument and provider. The authenticated network catalog supplies the applicable configuration.

These are typical times, not a universal SLA. Compliance review and receiving-bank conditions can delay delivery. Fast block finality does not make the entire bank-to-bank money cycle equally fast.

Live Features And Early Access Can Coexist

Polygon's October 29 Solana announcement presents particular capabilities as live. The bank-transfer and virtual-account guides still describe API access as early access, requiring an approved key.

The supportable conclusion is that specified routes or components are offered, while access and configuration remain project-specific. A production feature announcement does not establish unrestricted availability of the entire stack, every corridor or every provider relationship.

Paid OMS Volume Is Not The Entire Polygon Ecosystem

Polygon's payments page identifies different metrics for different businesses:

Partner reach, chain transfer volume, created wallets and completed integrations describe different populations. They cannot be summed into paid OMS volume. Even a correctly measured payment principal is the money moved for customers, not platform revenue.

The January acquisition announcement described a path toward more than $100 million annual revenue. That is a stated objective, not a current revenue result supported by published OMS financial statements.

As a scale check, 1 basis point is 0.01%. At a hypothetical 10-basis-point fee, $1 billion annual volume produces $1 million gross fee revenue before expenses. No conclusion about the actual OMS tariff follows from that arithmetic.

Liquidity And Prefunding Are Part Of The Business

Polygon's published Payments Liquidity Lead role described a commercial team owning OMS profit and loss, a liquidity book, corridor capital allocation, intraday rebalancing, FX hedging and a credit function. The original vacancy has been removed; a preserved copy contains the operating description. A job specification establishes an intended operating model, not the current size or performance of an executed credit book.

The role's example of 32 basis points supported by $1.8 million deployed capital is a hypothetical deal-economics illustration. It is not a published OMS tariff.

The resulting cost categories are broader than blockchain gas:

• bank, ramp, liquidity-provider and aggregator charges;
• cash needed in advance of incoming settlement;
• FX conversion, hedging and rebalancing;
• failed payments, returns, fraud and credit losses;
• engineering, security, compliance, licenses and support;
• acquisition integration and remediation expenses.

Average prefunding is a stock of capital tied up in delivery. Its funding expense is a recurring cost. Regulatory capital, surety bonds and stressed liquidity buffers are additional requirements; they are not replaced by an average operating balance.

A Hypothetical OMS Economics Model

Every operating input in this section is an assumption. This is a hypothetical hybrid subscription-and-percentage contract, not an OMS price quote or forecast.

The 50 subscriptions produce $6 million annual revenue. The percentage fee is added only because this scenario explicitly assumes a hybrid contract. Provider costs and per-payment expenses must cover different costs, with no duplicate allocation of bank, gas or FX expenses.

Payments = annual principal / average payment
Revenue = customers × monthly subscription × 12
        + annual principal × fee in basis points / 10,000

Average prefund = annual principal × prefunded share × days / 365
Annual funding expense = average prefund × cash funding rate

Steady-state cash flow = revenue
  − provider costs − execution costs − expected losses
  − fixed cash operating expenses − funding expense − maintenance capex

The funding rate represents an assumed cash expense. If it instead represents only the required return on the company's own capital, the deduction is an economic capital charge rather than an actual cash payment. The model adds no earnings from customer deposits, stablecoin reserves or other products whose income allocation has not been established.

Results At Different Annual Volumes

Calculated scenarios using the unchanged assumptions above. None is an estimate of observed OMS performance.

Under these assumptions, the steady-state cash-flow break-even volume is approximately $24.38 billion annually. Customers and fixed expenses are held constant to isolate the effect of volume; an actual business may need more customers, staff or infrastructure as it expands.

At $50 billion, the $27.40 million prefund is not deducted as an annual expense. Its assumed annual funding expense is $2.74 million. Creating the balance at the beginning also requires cash: a separate full-year illustration including that initial creation produces approximately −$11.64 million after the $15.76 million operating cash-flow result. The balance should not be treated as both an annual expense and an additional investment in the same calculation.

Payment Size, Pricing And Settlement Change The Result

At $50 billion annual principal, changing only the assumed OMS fee gives:

Reducing the average payment from $5,000 to $50 increases annual payment count from 10 million to one billion. Keeping the assumed $0.05 execution cost then reduces cash flow to −$33.74 million. Dollar volume alone cannot explain the economics of small payments.

Extending prefunding from two to five days increases the average balance to $68.49 million and reduces annual cash flow to $11.65 million. Banking delivery times and liquidity turnover can therefore matter even when blockchain execution is inexpensive.

Acquisition Payback Is A Conditional Calculation

The announced purchase amount was more than $250 million for Coinme and Sequence combined. It is not a disclosed standalone price for either company or a complete cash-payment schedule. The acquisition release does not supply the allocation required for a company-specific return calculation.

Using exactly $250 million as a simplified lower reference, the model's simple recovery period is:

Simple payback = ($250 million reference investment + initial prefund)
               / positive annual steady-state cash flow

This produces 17.6 years at the hypothetical $50 billion volume and 6.6 years at $100 billion. With the same assumptions and a prefund balance that scales with volume, a five-year simple payback requires approximately $128.6 billion annual principal.

These are arithmetic requirements, not predictions of acquisition returns or fair value. They omit the higher undisclosed full price, ramp-up, discounting, taxes, additional regulatory capital, remediation and further integration investment. They also omit terminal value and recovery of prefunding at exit. The cash flows of the entire acquired perimeter, including standalone Coinme and Sequence products, would be needed to assess the combined purchase properly.

How OMS Activity Can Affect POL

There are several distinct paths:

The ordinary network paths are explained in Polygon Chain fees. Receipt of fees, funding a collector, rewards credited to stakers and completed payouts are different accounting events.

What PIP-87 Actually Proposes

PIP-87, dated April 30, 2026, proposes fixed fiat pricing for payment-company blockspace. Its checked primary text is marked Draft.

The proposal would expand rebates for eligible payment relayers, convert programme receipts to stablecoins, and distribute funds through network mechanisms. It describes market purchases of POL for staker distributions and separate purchases for the burn collector. The split would follow the preceding period's priority-fee/base-fee ratio. Audits and public reports of purchases and distributions are part of the proposed process.

This is a programme for particular blockspace payments. It does not assign all OMS subscriptions, Coinme earnings or group profits to POL holders. The reviewed discussion and primary text did not establish an activation date or directly attributable execution receipts. A Draft label alone is not proof that no offchain arrangement can exist; confirmed current buyback cash flow requires separate evidence.

Multi-Chain Revenue Can Have A Different Token Path

The Solana announcement describes bank funding, balances and payouts around settlement on Solana. The fiat book-transfer option described earlier need not add a Polygon transaction. Commercial OMS growth therefore does not imply a fixed percentage increase in Polygon fees or burns.

A corporate POL-purchase scenario would need its own assumptions:

Purchase budget = positive available cash flow × approved allocation
POL purchased = budget / actual average execution price
POL burned = POL purchased × the applicable burn share

Because an allocation of all OMS profits has not been established publicly, this analysis assigns no automatic corporate purchase budget. Any positive allocation is a separate hypothesis. It must not be counted again as PIP-87 revenue, and purchased tokens must not automatically be labeled burned tokens.

What Would Establish Actual Profitability

A reliable business calculation needs paid customer invoices, contractual fees, deduplicated payment principal, payment counts, provider invoices, realised FX and liquidity costs, losses and returns, staffing costs and required capital. Enterprise integrations or large partner volumes do not provide those numbers by themselves.

For POL, the additional requirements are the share of activity executed on Polygon, actual gas, rebates, an applicable allocation policy and attributable purchase/distribution receipts. These are the links between a product announcement, a corporate income statement and a token cash-flow claim.

Related Research

• Polygon corporate structure
• Polygon, Coinme and Sequence acquisitions
• POL white paper
• Polygon Chain fees
• Priority fee distribution