The old way
Each bill can require another prompt, another decision, and another chance for the payment to stop.
Collect stablecoin subscriptions with one customer approval
Give your product a familiar way to collect stablecoin subscriptions, memberships, and bills. A customer sets the payment terms once. Their wallet applies the limits every time a payment is due.
Recurring stablecoin payments, without recurring signatures
Repeated signing turns a routine payment into a recurring chore. A customer-approved payment rule gives your product a clear way to collect on schedule, within terms they chose.
The Polygon OMS way
Your product can request the payment. The wallet allows it only when it matches the amount, scope, and time period the customer accepted.
25.00 USDCThe customer sets the terms
before money moves
Give people a plain-language payment agreement. Your product gets a workable recurring payment flow. The wallet gets the instructions it needs to enforce the agreement.
Set a limit
Define the maximum amount a payment can use.
Spending limit
25 USDC0Maximum
25 USDC0MaximumWhat it can pay
Keep payments limited to the subscription the customer agreed to.
Merchants
Ringside Global
Ringside GlobalOther merchants
When it can pay
Choose when payments can happen and when the approval ends.
April 2026
SMTWTFS
567891011
12131415161718
19202122232425
↻ Monthly · on the 15th
Stop it anytime
Let the customer revoke the rule when they no longer want it active.
Customer permissionRule activeFuture requests can be checked.
The wallet enforces the rule
Your backend can request a recurring payment without holding a blank check. The wallet checks every request against the customer’s rule onchain. If it falls outside the agreed limits, it cannot proceed.
Recurring payment permission
Ringside Global · Fight streaming membership
● Rule active
Maximum per payment
25 USDCSpending limit
Receiver
Ringside GlobalThis subscription only
Frequency
Monthly
✓ Approved permissionRevoke permission
Payment request
Ringside Global
25 USDC
Recurring · Monthly
OMS Wallets checks onchain
- ✓ Within spending limit
- ✓ Approved receiver
- ✓ Within billing period
Approved
The request matches the rule.
25 USDC is within the customer’s limit.
Payment proceeds
What happens when the next payment is due
Your product requests the payment. The wallet checks it against the customer’s approved terms, so they don’t have to return and sign again.
Step 01Your product
Your product
requests payment
Automatic recurring payment
APR15
25 USDC · monthly
✓ Billing date reached
↻ Payment request sent automatically
Step 02
The wallet checks the terms
Checking approved terms
✓ Amount within your limit
✓ Approved receiver
✓ Timing matches your rule
✓ Request matches the ruleStep 03
The payment proceeds
Payment completed
25 USDC sent
To Ringside Global
Within the approved terms
✓ Subscription paidStep 04
Your product tracks the result
Payment history
Ringside Global · 25 USDC / month
May✓ Paid
June✓ Paid
July✓ Paid
Built for your next recurring payment
From software plans to AI usage bills, collect recurring payments within the terms your customer approves.
AI inference and API services
Collect recurring usage invoices within an approved spending limit.
Cloud and compute
Charge for GPU access, hosting, storage, and infrastructure.
Software subscriptions
Collect monthly payments for SaaS products and developer tools.
Content and community memberships
Renew streaming, creator, newsletter, and community memberships.
Marketplace service fees
Collect recurring seller subscriptions and platform access fees.
Business retainers
Collect scheduled payments for ongoing professional services.
Your billing logic. Our SDKs.
Collect customer approval with OMS Wallet SDKs. Use the TypeScript SDK to request payments from your existing billing flow, with approved limits enforced onchain.
Explore the docsTerminal
// 01 Set up your backend
registerCredential
// 02 Request approval in your app
inspectRemoteCredential
authorizeRemoteAccess
// 03 Run payments from your backend
getSession
prepareTransaction
executeTransaction
getTransactionStatusFAQ
Frequently asked questions
01
Recurring payments use OMS Wallets with Smart Sessions, which currently support EVM wallets and customer-approved ERC-20 transfers. The payment permission specifies the network and token your product will use. Talk to our team to confirm the stablecoins and networks available for your integration.
02
Yes. Your billing system calculates each payment, so amounts can vary with usage—for example, inference costs or API calls. Each request must stay within the customer’s approved permission and remaining allowance. If a charge requires a higher limit, the customer must approve the change.
03
The payment cannot proceed under that permission. The wallet enforces the approved limits onchain, and your backend cannot override them. Your product can ask the customer to approve an updated limit before submitting a new request.
04
The payment cannot complete without enough of the required token in the wallet. Your product handles the next step: asking the customer to add funds, retrying later, or applying your usual billing policy. Before retrying, your backend should check the transaction’s status to avoid submitting a duplicate payment.
05
The customer’s approval creates a permission enforced onchain by the wallet’s Sessions Module. Each payment must stay within the approved token, recipient, spending allowance, and expiry. The wallet rejects requests outside those terms, and your backend cannot expand the permission without the customer’s approval. Learn how Smart Sessions work.
If you don't see your question answered here, reach out to our support team, we're always happy to help.
contact us