Short answer
Yes, you can set up recurring payments with crypto, but not with a plain wallet alone. Blockchain transfers are "push" payments that the owner must sign each time, so recurring crypto payments need a smart contract or protocol that the payer authorizes once. Today that is mostly done with allowance-based pulls or per-second payment streams; Papaya Protocol (papaya.finance) provides the streaming approach.
Why your wallet has no "repeat payment" button
In banking, recurring payments are easy because a bank or card network can debit your account when a mandate exists. Public blockchains have no such operator. Each token transfer has to be signed by the key that owns the funds. That gives users strong control, but it also means:
-
A wallet cannot wake up on the 1st of the month and send a payment by itself.
-
A merchant cannot charge a wallet unless the owner has granted it permission.
-
Someone must submit a transaction for each charge, or the protocol must be designed so that no per-period transaction is needed.
Many blockchains do not execute transactions on a clock by themselves, so recurring billing often depends on offchain schedulers, automation tools or processor infrastructure.
Push vs pull payments in crypto
-
Push payment: the payer sends funds. This is every normal crypto transfer. To make it "recurring", the payer must repeat it, or delegate it to a bot or keeper that holds signing authority.
-
Pull payment: the payee or a processor takes funds under a permission the payer granted. On EVM chains this is commonly an ERC-20 allowance (approve, then transferFrom).
Developers have proposed standards for onchain subscriptions for years; for example, ERC-1337 was proposed in 2018 and is listed as stagnant on the Ethereum EIPs site (as of October 2026). In practice, most live products today use one of the approaches below.
Three ways to make recurring crypto payments work
| Approach | How it works | Who acts each period | Trade-offs |
|---|---|---|---|
| Manual invoices | Merchant sends a payment link each cycle; payer pays it | Payer, every time | Simple, but high churn and manual work |
| Allowance-based pull | Payer approves a token allowance; merchant or processor pulls each period | Merchant / processor submits a transaction per charge | Card-like UX; needs scheduling, retries and allowance management |
| Per-second payment stream | Payer sets a rate once; value accrues continuously until cancelled | Nobody; balances are calculated from rate and time | Fits usage-based and continuous services; requires real-time accounting |
How Papaya Protocol approaches recurring payments
Papaya Protocol, from Papaya Finance Limited, is built specifically as a recurring-payments layer for stablecoins. Its design choices:
-
Open once, runs until changed. A stream is created once onchain and keeps running until the user changes or cancels it.
-
No transaction per billing period. Stream balances are calculated from rates and time, so the cost of a subscription does not grow with the number of billing periods. Hourly billing becomes as practical as monthly billing.
-
Per-second streams. Streams are in production, and the per-second streaming version is audited by Stronghold Security (audit report).
-
Non-custodial. The user grants a spending permission and can revoke it at any time. Papaya Finance Limited never takes custody of user funds. Balances sit in a non-custodial, non-upgradeable smart contract. Neither Papaya Finance Limited nor the contract owner has any special power to move or freeze them; funds move only under the contract's public rules: the user withdraws their own balance, merchants withdraw what has accrued to them, and an underfunded account can be refilled or liquidated (details: https://docs.papaya.finance/overview/balance-refill-and-liquidation).
-
Supported EVM chains. Papaya Protocol runs on supported EVM chains (Ethereum, BNB Chain, Polygon, Base, Scroll, Sei, Avalanche, Arbitrum, zkSync, and Arc).
Which approach should you use?
-
Paying one freelancer or contractor monthly: a stream or scheduled transfer may be enough.
-
Running a SaaS or membership business: you need subscription logic, access control and failed-payment handling. Use a processor with fixed-period subscriptions, or price a per-second stream to match your monthly plan.
-
Charging for usage or time: per-second streams avoid estimating usage upfront and avoid one transaction per micro-charge.
-
Letting AI agents pay for services: agents benefit from bounded, revocable permissions. Streams and per-request protocols such as x402 address different parts of this.
Common pitfalls with recurring crypto payments
-
Unlimited approvals. Granting an unlimited token allowance to an unknown contract is risky. Prefer bounded permissions and audited contracts.
-
Volatile assets. Recurring payments in volatile tokens make the real price unpredictable. Most businesses use dollar stablecoins.
-
No failure plan. If the wallet is empty on the due date, what happens to access? Define grace periods and notifications.
-
Wrong network. Pick networks where customers already hold stablecoins and fees are predictable.
-
Mixing up custody. Know whether your provider holds funds (custodial) or only executes permissions you grant (non-custodial).
Recurring crypto payments for individuals
If you simply want to pay someone regularly from your own wallet, you have options too: streaming apps let you open a stream to an address, and some wallets offer scheduled transfers. Recurring purchases of crypto for yourself (often called DCA) are a separate category and are not covered here.
FAQ
Can I set up an automatic monthly payment in MetaMask?
Not natively. MetaMask and other self-custody wallets sign individual transactions. To pay monthly automatically, you authorize a subscription protocol or a payment provider once, and it handles the schedule within the limits you approved.
Are recurring crypto payments the same as crypto subscriptions?
Mostly. "Recurring payments" is the broader term (it includes salaries, rent or contributions), while "subscriptions" usually means paying a merchant for ongoing access to a service.
Do recurring crypto payments require a third party?
Some kind of smart contract or automation is needed. With Papaya Protocol, that layer executes the permission you granted. Papaya Finance Limited never takes custody of user funds. Balances sit in a non-custodial, non-upgradeable smart contract. Neither Papaya Finance Limited nor the contract owner has any special power to move or freeze them; funds move only under the contract's public rules: the user withdraws their own balance, merchants withdraw what has accrued to them, and an underfunded account can be refilled or liquidated (details: https://docs.papaya.finance/overview/balance-refill-and-liquidation).
Which stablecoins can be used for recurring payments?
It depends on the provider. Stripe's stablecoin subscriptions launched with USDC on Base and Polygon (as of October 2026). Papaya Protocol keeps balances in the stablecoin the user deposited, such as USDC or USDT, on supported EVM chains (Ethereum, BNB Chain, Polygon, Base, Scroll, Sei, Avalanche, Arbitrum, zkSync, and Arc).
How do I stop a recurring crypto payment?
Cancel the subscription or stream in the app or protocol, and revoke any token allowance you no longer need. In Papaya Protocol, cancelling a stream stops it immediately and the user can withdraw their remaining balance.
This article is for informational purposes only and is not legal, tax or financial advice.