Moving money across borders still runs on a patchwork of bank rails. Capital gets locked, settlement takes days, and every fintech ends up rebuilding the same plumbing.

HIFI is a payments API that lets teams move, convert, and route money across stablecoins and bank rails. Since January 2025 it has routed more than $227M through Polygon's Open Money Stack across 6M+ transactions, covering payroll conversions, supplier payments, treasury flows, and neobank money movement.

The reason HIFI picked Polygon Chain as a core routing network: throughput that holds up under real volume, years in production as a battle-tested default, and a payments-first design from day one. The end user sees something as simple as Venmo or a paycheck. The chain does the work underneath.

More than 1,000 developers and businesses now build on HIFI's APIs, and CEO Zach Walsh expects the stablecoin market to grow from roughly $300B today to $3 to $5T within five years.

Full case study: https://polygon.technology/oms-customer-stories/hifi

Heads up for anyone building on or using Polygon Chain: the free, Polygon-operated public RPC endpoints are being shut down. The two affected endpoints are https://polygon-rpc.com/ (Mainnet) and https://rpc-amoy.polygon.technology (Amoy testnet). After the deprecation dates, they stop responding entirely.

Dates:

• Amoy testnet: July 17 (this Thursday)
• Mainnet: July 31

If your app, wallet, script, or service is hardcoded to either of those URLs, you need to swap it out before then. The fix is usually just updating a single config value. Polygon maintains a full list of alternatives at https://docs.polygon.technology/pos/reference/rpc-endpoints, including free public options (dRPC, Tenderly, Allnodes, Nodies, 1RPC, and others) and paid providers if you need higher rate limits or SLAs.

The Amoy deadline is in 3 days, so if you're doing any testnet work, prioritize that one first. Questions or migration issues can go to https://support.polygon.technology.

Full announcement: https://forum.polygon.technology/t/deprecation-of-polygons-public-rpc-endpoints-mainnet-amoy/22014

Are we agglaying over there ???

PYUSD used to reach Polygon the way most stablecoins reach a new chain: bridged in, wrapped, one step removed from the issuer. That changes today. PYUSD now settles natively on Polygon Chain, the same network already moving more than $2.5 billion in stablecoin volume every day. Native issuance means no bridge risk, no wrapped token, and a direct line between Paxos's reserves and every PYUSD transaction that settles onchain.

The integration goes deeper than settlement. PYUSD now sits inside the Polygon Open Money Stack, so an app can take PYUSD in, move it across borders, and cash it out through a single integration instead of stitching together separate ramps, wallets, and settlement providers. That includes apps inside the PayPal ecosystem and apps outside it, anywhere PYUSD is accepted.

* PYUSD issues natively on Polygon Chain, no bridging or wrapped tokens
* Built into the Polygon Open Money Stack for onramp, cross-border movement, and offramp in one integration
* Works for apps inside and outside the PayPal ecosystem
* Polygon Chain settles more than $2.5 billion in stablecoin volume every day

For fintechs and platforms already building payment flows on PYUSD, this removes a step: settlement infrastructure and stablecoin issuance now live on the same rail instead of two separate ones to reconcile. It's another regulated stablecoin choosing Polygon Chain as its settlement layer, on top of the volume already moving through the Open Money Stack.

As is well known, Polymarket is leaving Polygon, likely before the end of the year. Polymarket is by far the chain's largest protocol and has been something of a flagship for Polygon. How significantly will this impact Polygon's usage and TVL, and can the network recover from this departure through promising new projects like blackSwanFinance.xyz? Without unique new protocols, Polygon risks becoming just another sidechain.

Over the past year, we've been focused on one goal: making Polygon the best place to build and scale payments.

Across six network upgrades (Bhilai, Heimdall v2, Rio, the 110M capacity raise, Lisovo, and Giugliano), we've improved throughput, reduced costs, strengthened finality, and increased network capacity.

Today, Polygon supports:

• Up to 5,000 payments per second
• 1.5-second block times with near-instant finality (no reorgs after Rio)
• ~$0.002 average transaction fees
• A 160M gas limit (up from 30M a year ago)

The infrastructure is already powering real-world payments and finance. Stripe now supports USDC payments on Polygon for merchants in 150+ countries, while Polymarket, BlackRock's BUIDL, Franklin Templeton's BENJI, and Apollo's tokenized fund all settle on Polygon Chain.

This is the foundation for the Polygon Open Money Stack (currently in technical preview), bringing together the chain, wallets, on-ramps, and off-ramps needed to build global payment applications.

Read the full post: https://polygon.technology/blog/polygon-chain-now-supports-5000-payments-per-second-hitting-the-speed-of-a-card-network-at-a-fraction-of-the-cost

Polygon's wallet infrastructure is live as part of the Open Money Stack, and it's designed to be the plumbing every OMS transaction flows through. The model is straightforward: you choose custodial (licensed partner holds keys, KYC and the money transmitter license are absorbed for you) or non-custodial (users control their own keys). Either way the API is the same.

Why wallets are central: fiat comes in and lands in one, payouts pull from one, transfers move between them. Once you're integrated, adding ramps, cross-chain routing, or yield becomes an additive step rather than a new integration. Idle balances can earn yield automatically, and the whole thing is white-labeled so your users never see Polygon, just your product.

Security-wise: keys are generated and stored in AWS Nitro secure enclaves, never exposed to Polygon, your software, or your team. Audited at every release and battle-tested in production since 2021. Docs and early access: https://polygon.technology/wallets

Uquid just integrated Polygon's Open Money Stack, and the practical upshot is pretty clean: you can now pay with whatever token you already hold, on whatever EVM chain you're on, across their full catalog of 178M+ products (digital goods, physical goods, gift cards, mobile top-ups, bill payments, NFTs) in 200+ countries. One signature. Done.

The way it works under the hood is the interesting part. The Open Money Stack handles the swap and bridge routing in the background. You don't need to pre-swap to the "right" token or manually bridge to whichever chain Uquid settles on. It just composes those steps into a single routed transaction. Fully self-custodial throughout too: no intermediary takes custody mid-flow, and the destination is enforced by the contracts. Uquid has actually been on Polygon since 2022, but the old integration was manual. This replaces it with fully automated cross-chain routing.

Context on the rails: this is the same Open Money Stack that Cash App (58M MAUs) runs stablecoin sends on, that Mastercard uses for 24/7 settlement, and that Revolut has processed $1.3B+ through. Uquid is the first consumer commerce platform at this scale to drop it directly behind a shopping cart. Full post: https://polygon.technology/blog/uquid-integrates-polygons-open-money-stack-for-1-click-crypto-checkout-across-178m-products

Polygon Chain now handles up to 5,000 payments per second after raising the block gas limit to 160M at 1.5-second blocks. That puts it in the same throughput tier as Visa's average daily load, at roughly $0.002 per transaction instead of the ~2-3% card rails charge.

This is the latest in a year-long upgrade sequence: Bhilai last July got to 1,000 TPS, Rio rebuilt block production to eliminate reorgs (so every confirmed block is final), Giugliano earlier this year added predictable fees, and now the 160M gas raise gets to 5K. The team calls it the "Gigagas" roadmap and this is clearly not the last step. What's worth noting is how fees have stayed stable through all of this. Bigger blocks mean it takes a lot more volume before congestion kicks in, and the fee mechanism adjusts gradually rather than spiking. For stablecoin payroll, remittances, or B2B settlement, that means you can actually model unit economics at scale without the floor dropping out.

Stripe global USDC payments, Polymarket, BlackRock BUIDL, Franklin Templeton BENJI, and Apollo's tokenized fund are all already live on Polygon. More headroom for all of them now. Full post: https://polygon.technology/blog/polygon-chain-now-supports-5000-payments-per-second-hitting-the-speed-of-a-card-network-at-a-fraction-of-the-cost

See the list here!

Hey, I’m a dev currently working on a DeFi protocol on Polygon. To get to know the network better, I’d be interested to know—aside from Polymarket—what the biggest dApps/DeFi protocols on Polygon are. Thanks!

Mastercard just announced Agent Pay for Machines (AP4M), and Polygon is listed as a launch partner alongside Coinbase, Stripe, Cloudflare, OKX, Solana Foundation, Ripple, Adyen, and about 25 others. The premise: AI agents are going to start transacting with each other continuously and at very small values, and today's payment rails weren't built for that. Mastercard is building the credentialing and settlement layer to support it, with multi-rail settlement across cards, accounts, and stablecoins.

The reason Polygon fits here is pretty clear from the quote they got from Aishwary Gupta (global head of business at Polygon): the Open Money Stack is positioned as infrastructure for exactly this kind of programmable, agent-driven commerce. The stablecoin settlement angle is a natural overlap with what Mastercard needs, since micro-transactions at machine speed work a lot better on low-fee programmable rails than on traditional card networks.

What's interesting about the partner list is how many crypto-native companies are in there alongside legacy payment processors: Coinbase, OKX, Ripple, Rain, Tempo, MoonPay, Anchorage Digital, and Polygon. That's a pretty significant shift from Mastercard doing one-off crypto experiments to building an open framework explicitly designed for stablecoin settlement. Worth keeping an eye on as AP4M rolls out.

Full announcement: https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html

Polygon just opened early access to Open Money Stack (OMS), and the technical preview is live today. The short version: it's a single API that handles the full money movement loop. Cash in via 48 US states, converts to USDC or USDT on Polygon chain, moves to wallets or external addresses in seconds, and comes back out as fiat through ACH, Fedwire, or RTP. The whole flow is one integration.

The payroll example in the post gives you a good sense of what this actually enables. A US company wires $50K via ACH, triggers 200 contractor payouts in a single API call, and each payment settles to a custodial wallet in seconds at fractions of a cent. On legacy rails that's 1-3 business days. On OMS it's done before you close the tab. The integration itself took days, not months.

What's live now: cash and bank ramps for business, custodial wallets (USDC/USDT on Polygon), stablecoin transfers, external wallet routing, webhooks, RBAC, and SSO. A management dashboard is also up. Coming soon: embedded wallets, individual bank off-ramps, swaps, cross-chain bridges, and self-serve signup. Early access is limited right now but there's a form to apply. Full post here: https://polygon.technology/blog/polygon-open-money-stack-enters-technical-preview

Starting today, there are 10 Easter eggs hidden across the Trillions landing page at trillions.polygon.technology/explore.

Each one is a unique code concealed inside an object on the page. Find it yourself (no hints, that's the point), follow the redemption link, and claim your prize. Each prize is a Polygon swag box, contents include things like a hoodie, t-shirt, and other branded gear, around $100 value each.

A few things worth knowing:

• 10 prizes, 10 codes, one per person
• Each code is single-use: the first person to redeem it wins
• Promotion runs until June 30, 2026 at midnight EST, or until all 10 are claimed, whichever comes first
• No purchase necessary. Open to participants worldwide (18+, some jurisdictions excluded)

Full official rules: polygon.technology/easter-egg-official-rules

Good luck.

We are seeing Bennu route more real transaction activity through Polygon as users interact with stablecoins, self-custody, swaps, and payment rails.

What stands out is not only the low fees. It is that Polygon makes small financial actions feel practical: moving stablecoins, funding wallets, routing payments, and building flows where the chain is infrastructure instead of the product.

For consumer and business finance, that is the part that matters. Users do not wake up wanting an L2. They want money to move, receipts to make sense, and the app to feel reliable. Polygon is one of the rails where that starts to work in practice.

For years, institutions looking at blockchain have been stuck on the same trade-off: run a closed permissioned network and lose onchain liquidity, or stay on a public chain and expose every transaction. Banks, asset managers, and payments companies have basically been waiting for someone to solve this before they touch the space at scale.

Polygon CDK just shipped the resolution. The new validium config keeps raw transaction data inside infrastructure the institution owns. Ethereum only receives a cryptographic commitment and a zero-knowledge proof, enough to verify the chain is operating correctly without seeing the transactions. The prover is Succinct's SP1 Hypercube, already in production on Katana, so this isn't a research demo.

Privacy is treated as a spectrum, not a single setting. CDK now offers five composable levels you can stack without migrating: role-based access and SSO, validium-based confidential chains, TEE-sealed compute, FHE-encrypted tokens, and client-side ZK shielded user transactions. Counterparties see only what they participate in, auditors get scoped reads, regulators get selective disclosure, operators keep full visibility.

The piece that keeps this from being a walled garden: every CDK chain ships connected to Agglayer. A private chain still settles cross-chain into Ethereum, every connected L1 and L2, and non-EVM networks like Miden. A regional bank can launch private stablecoin rails and its clients can still tap the full Open Money Stack for ramps, wallets, and global liquidity. The chain is private. The economy around it isn't.

The first regulated banks, stablecoin issuers, and asset managers building on it are already in motion. Curious what people who've shipped on permissioned chains think: does this look like a real answer to the "privacy vs liquidity" problem, or is there still a piece missing?

Hey r/0xPolygon

I've been building ByteCartridge over the last several months and recently went live on Polygon mainnet. Before pushing it more broadly, I want honest feedback from this community since you're the people who actually use Polygon dApps.

What it is

A data marketplace where buyers can cryptographically verify a dataset before paying. The smart contract uses a novel verification mechanism that catches sellers trying to ship corrupted or fake data — works from your very first transaction. No tokens, no governance votes, no validator networks. Just cryptography and math.

The deployment

Live at bytecartridge.com

Contract: 0x7389920fb3Eca7c96E5A1AbbEeCd42014711e9C5 (verified on Polygonscan and Sourcify)

Settles in USDC, 2% protocol fee

MIT-licensed, source on GitHub

What I'm hoping to learn

1. Does the use case resonate? If you've ever wanted to buy a dataset (training data for a model, historical price data for a bot, scraped data for analysis), would something like this fit your workflow? Or is it solving a problem nobody actually has?

2. First impression of the UX — try connecting a wallet, browse the listings, run an audit. What's confusing, broken, or missing?

3. Pricing intuition — current listing is $1-2 USDC. Does that feel right for a "test it out" pricing? Too low to take seriously? Too high for the data being sold?

4. Honest skepticism — what would make you NOT use this? Better to hear it now than discover it later.

5. What kinds of data would you actually want to buy? I'm thinking through what to add to the marketplace next.

Why I'm asking here specifically

Polygon's user base is exactly the audience this is built for — people who already have wallets, already have USDC, already understand on-chain mechanics. Generic crypto Twitter feedback is noise. Polygon-specific feedback from people who actually transact on this chain is signal.

Try it, break it, tell me where it falls short.

Happy to walk anyone through it personally if helpful, or just discuss in comments. Genuinely want this to be useful, and that means hearing what's wrong before it scales.

A lot of us wanted to leave the traditional financial system because it is slow, fragmented, permissioned, and too easy for intermediaries to freeze or surveil everything.

But then the first version of onchain finance created a different problem: every normal transfer exposes the sender, receiver, and amount to the public internet. That is not how serious payments work. Payroll, vendor payments, treasury movements, internal company flows, and personal financial activity cannot all be public by default.

That is why Polygon's private payments with Hinkal feel important to me. It is not just another wallet feature. It is the missing layer between open settlement and real financial confidentiality.

The ideal version of crypto payments was never “everything should be visible to everyone forever.” It was: faster settlement, self-custody, lower cost, fewer gatekeepers, and privacy that works like normal financial privacy without giving up cryptographic verification.

If ZK proofs can verify a valid transfer while keeping sender, receiver, and amount private, that changes the whole enterprise payments conversation. It makes stablecoin rails look less like a public spreadsheet and more like usable financial infrastructure.

This is the kind of thing Polygon should be known for.

Some standout numbers from the report. Network fees did $11.7M in Q1, up 419.8% QoQ and the highest quarterly figure on record. Chain GDP (total app revenue) hit $51.1M, up 50.3%. Payments-focused apps moved $5.80B in transfer volume, up 51.4%, with Tazapay alone responsible for $2.5B of that (a 22x quarterly jump). Stablecoin supply on Polygon grew to $3.55B, with USDC up 35.9% to $1.82B. Polygon is now #1 globally by active USDC addresses.

Polymarket is the elephant in the room. Average daily open interest hit a new ATH of $463M (+32.4% QoQ), and $16.2M in app revenue made it the largest single revenue contributor on the chain. ICE put another $600M into Polymarket in late March, bringing its total commitment to roughly $2B. Worth flagging: Polymarket's relayer and proxy-wallet model abstracts gas from end users, which is a big part of why daily active addresses dropped 37.8% even while transactions rose 52.1%. Raw address counts are getting harder to read as a user-demand proxy.

A few other things worth chewing on. There's a clear divergence inside payments: transfer volume up 51% but crypto card volume down 47.9% to $143M. There's a regional split too: LatAm non-USD stablecoin volume down 45.5%, APAC up 187% (Australian dollar stablecoins alone did almost $900M). App RCR fell 75% to 3.45x, which Messari reads as activity shifting toward high-velocity, lower-margin flows like trading and payments. On the infra side, Polygon doubled the gas limit to 120M and pushed peak throughput past 2,800 TPS through a series of headroom upgrades and the Lisovo hardfork, which also added a $1M gas subsidy for agentic payments. POL itself was down 8.7% on the quarter while the broader crypto market was down 22.7%.

Full report: https://messari.io/report/state-of-polygon-q1-2026

Polygon's wallet just turned on a "Privately Send" option for USDC and USDT. When you use it, the transfer routes through a shielded pool, and zero-knowledge proofs verify the math without publishing the sender, the receiver, or the amount onchain. It's built in collaboration with Hinkal, the shielded-pool privacy protocol that handles the cryptography.

The interesting bit isn't that privacy is possible on a public chain (people have been building shielded pools for years). What's new is that a major payments-focused L2 has shipped private transfers in the default wallet, with KYT (Know Your Transaction) screening baked into the flow before execution. Privacy from competitors and counterparties, but not from regulators. The protocol is non-custodial too: funds never sit with Hinkal or any third party during a transfer.

Why it matters: confidentiality has been the single biggest blocker for treasury teams, fintechs, and payments operations actually moving stablecoin volume onchain. Banks settle slowly and charge a lot, but they don't broadcast every counterparty and amount to the world. This closes that gap without giving up the speed and cost of onchain settlement. Live today on wallet.polygon.technology for USDC and USDT.

Full post: https://polygon.technology/blog/private-payments-are-live-on-polygon