The old way
Lists, reviews, approvals, and exceptions interrupt a repeatable job.
Run stablecoin payouts with rules your team sets
Set the recipient scope, budget, and run window once. The wallet checks every payout against those terms onchain.
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 Polygon OMS way
The wallet permits only payments that match the approved recipients, budget, and window.
36,000 USDCOnchain 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.
Recipient scope
US contractors ✓
Brazil contractors ✓
Mexico contractors ✓
Canada contractors
UK contractors
US contractors ✓Brazil contractors ✓Mexico contractors ✓Canada contractorsUK contractorsSpend limit
Set the maximum the run can send.
Run budget
36,000 USDC0Maximum / run
36,000 USDC0Maximum / runRun window
Set when payouts are allowed.
April 2026
SMTWTFS
567891011
12131415161718
19202122232425
Fri, Apr 17 · 09:00–17:00 UTC
Off switch
Revoke the active rule.
Payout permissionRule activeRevoke to stop future requests.
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
Your team defines the terms once.
36,000 USDC
Recipients12 approved contractors
Maximum per run36,000 USDC
WhenFriday · 09:00–17:00 UTC
✓ Approved permission · revocable anytime
Only requests that match these terms can proceed.
Wallet checks this request
✓ Recipient approved
✓ Within budget
✓ Within window
✓ Payout proceeds automatically
! Unapproved recipient → rejected
The request stops at the wallet contract.
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 1
A payout request arrives
Friday payout run
JUL15
36,000 USDC · 12 recipients
Backend requests payout run
12 transfers queued
STEP 2
The wallet checks the rule
Rule checks passed
✓ Recipient scope
✓ 36,000 USDC budget
✓ Friday run window
Payouts approvedSTEP 3
Approved payouts execute
Payout run executing
12 recipients
36,000 USDC
USA · Brazil · Mexico
12 transfers submittedSTEP 4
Track each payout
Payout history
Friday contractor cycle
Run opened09:00 UTC
12 transfers✓ Sent
Run closed09:08 UTC
Exceptions0
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 docsINTEGRATION FLOW
BACKEND
01 registerCredential
OWNER APP
02 inspectRemoteCredential
03 authorizeRemoteAccess
BACKEND
04 getSession
05 prepareTransaction
06 executeTransaction
07 getTransactionStatus
Your app owns scheduling and run state.FAQ
Frequently asked questions
If you need help mapping your payout workflow to wallet approvals and payout APIs, talk with the Polygon team.
contact us01
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.