Join Polygon at Money20/20 in Vegas.Request a meeting →

Run stablecoin payouts with rules your team sets

Run stablecoin payouts with rules your team sets

Make payout day a controlled product flow

Prepare an approved run once, then let your product request the payments. The wallet checks every request.

The old way

Lists, reviews, approvals, and exceptions interrupt a repeatable job.

The Polygon OMS way

The wallet permits only payments that match the approved recipients, budget, and window.

Onchain rules keep every payout within the terms you approve

Approved terms live in the wallet’s onchain Sessions Module. After approval, a backend cannot expand recipient scope, increase the budget, or extend the run.

Recipient scope

Approve who the run can pay.

Spend limit

Set the maximum the run can send.

Run window

Set when payouts are allowed.

Off switch

Revoke the active rule.

The wallet enforces the rule onchain

A payout run uses a scoped wallet permission. If a request falls outside the approved action, budget, or window, the wallet rejects it at the contract level. Review the permission model.

Payout permission mock — a 36,000 USDC recurring payout approved against a scoped wallet rule, shown beside a "pay with stablecoins" preview panel

What happens when the next payout run starts?

Your product requests each payout. The wallet checks every request against the approved rule before funds move.

Step 01

A payout request arrives

×

Friday payout run

JUL

15

36,000 USDC · 12 recipients

Backend requests payout run

12 transfers queued

Friday payout run — 36,000 USDC across 12 recipients, 12 transfers queued

Step 02

The wallet checks the rule

×

Rule checks passed

✓ Recipient scope

✓ 36,000 USDC budget

✓ Friday run window

Payouts approved

Rule checks passed — recipient scope, budget, and run window all approved

Step 03

Approved payouts execute

×

Payout run executing

12 recipients

36,000 USDC

USA · Brazil · Mexico

12 transfers submitted

Payout run executing — 12 recipients, 36,000 USDC across USA, Brazil, and Mexico

Step 04

Track each payout

Payout history

Friday contractor cycle

Run opened09:00 UTC
12 transfers✓ Sent
Run closed09:08 UTC
Exceptions0
Payout history — Friday contractor cycle, run opened and closed with 0 exceptions

Built for the payout flows you already run

Contractors, sellers, creators, partners, refunds, and rewards all move within terms your wallet owner approves.

FIELDWORK / People operations

Friday payroll

Contractors · September 18, 2026

$36,000.00

12 contractors ready to pay

ContractorAmount

Ana Ribeiro3,200 USDC
Marcus Lee4,800 USDC
Sofia Ortiz3,200 USDC

....


Example company · Scoped wallet approval

Built for the payout flows you already run

Contractors, sellers, creators, partners, refunds, and rewards all move within terms your wallet owner approves.

Contractor payouts

Pay recurring contractor runs across approved recipients and corridors.

Marketplace seller payouts

Settle seller earnings from a platform treasury within approved run terms.

Creator and affiliate payouts

Pay campaign earnings without approving every transfer.

Partner settlements

Pay approved partners within set amounts and windows.

Customer refunds

Return funds through a controlled payout flow with clear status tracking.

Rewards and disbursements

Send rewards, cashback, or disbursements within a set budget.

Your payout logic. Our SDKs.

Use OMS Wallet SDKs to collect owner approval, then request bounded transfers from your existing payout workflow. Approved grants are enforced onchain.

Explore the docs
FAQ

Frequently asked questions

If you need help mapping your payout workflow to wallet approvals and payout APIs, talk with the Polygon team.

contact us
01
Yes. Your wallet owner approves who can be paid, how much can be sent, and when the permission expires. Your backend can request payouts within those limits, but it cannot expand them. The wallet enforces the approved terms onchain.
02
Yes. Your system keeps control of payout calculations, scheduling, and internal approvals. Integrate the OMS Wallet SDKs to request wallet-owner approval and submit payouts under that permission. OMS provides the wallet-level controls; it does not replace your payout operations workflow.
03
Your application checks each submitted transaction’s status and handles exceptions. For payouts submitted as separate transactions, a later failure does not undo earlier completed payments. Your integration determines whether to pause the run or continue, and should confirm transaction status before retrying.
04
Yes. Your application can stop scheduling new requests, and the wallet owner can revoke the permission to prevent further use. Changing recipients or limits requires the owner to approve updated terms. Stopping a run does not reverse completed payouts.

Build the payout flow your team can run