> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shakesco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recurring Crypto Payments

> Enable subscription payments on Ethereum with self-custody - solving the push-vs-pull problem

<span style={{display:"none"}}>For the complete documentation index, see [llms.txt](/llms.txt).</span>

## The Subscription Economy Meets Crypto

Crypto has unlocked global value transfer - anyone, anywhere can receive payments. But there's a critical gap: **recurring payments**.

<CardGroup cols={2}>
  <Card title="Traditional Finance" icon="building-columns">
    Stripe and PayPal process **>1% of world GDP** through subscriptions
  </Card>

  <Card title="Crypto Today" icon="bitcoin">
    Only push payments - no native subscription infrastructure
  </Card>
</CardGroup>

[Source: Stripe crosses \$1 trillion in payments](https://finance.yahoo.com/news/stripe-crosses-1-trillion-total-154015081.html)

***

## The Technical Challenge

### Why Crypto Subscriptions Are Hard

<Accordion title="Bitcoin: No smart contract capabilities">
  Bitcoin's scripting language isn't Turing-complete - it can't execute recurring payment logic on-chain.

  **Only solution:** Give your private key to a custodial service

  **Problem:** That's just rebuilding Stripe with extra steps.
</Accordion>

<Accordion title="Ethereum: The push payment problem">
  **Traditional payments:** Pull-based (merchant pulls funds)\
  **Crypto payments:** Push-based (user must initiate)

  **The dilemma:** Who triggers recurring payments if users must approve each one? If we automate it, doesn't that require custody? If we make it custodial, aren't we just recreating centralized finance?
</Accordion>

***

## The Ideal Solution Requirements

<Steps>
  <Step title="Self-custody">
    Users maintain control of their funds at all times
  </Step>

  <Step title="Censorship-resistant">
    No central authority can block transactions
  </Step>

  <Step title="Permissionless">Anyone can build or use it</Step>
  <Step title="Decentralized">No single point of failure or control</Step>
  <Step title="Secure">Smart contracts handle payments safely</Step>
</Steps>

**The answer:** Account Abstraction (ERC-4337)

***

## How Account Abstraction Solves It

<Tabs>
  <Tab title="The Problem">
    **Traditional wallets (EOAs):**

    * User must manually approve every transaction
    * Can't automate recurring payments
    * Push-only model

    **For subscriptions, you need:**

    * Automated execution at intervals
    * User maintains control
    * No custodial service
  </Tab>

  <Tab title="The Solution">
    **Smart wallets (Account Abstraction):**

    * Pre-approve subscription parameters
    * Smart contract enforces limits
    * Automated execution by network
    * User keeps custody

    **How it works:**

    1. User approves subscription (amount, frequency, merchant)
    2. Smart contract stores approval
    3. Network executes payments on schedule
    4. User can cancel anytime
  </Tab>

  <Tab title="The Benefits">
    ✅ **Self-custody** - Keys never leave user's control\
    ✅ **Automated** - Payments execute without manual approval\
    ✅ **Secure** - Smart contracts enforce limits\
    ✅ **Transparent** - All logic on-chain and auditable\
    ✅ **Flexible** - Easy cancellation and modification\
    ✅ **Permissionless** - Anyone can integrate
  </Tab>
</Tabs>

***

## Real-World Applications

<CardGroup cols={3}>
  <Card title="SaaS Subscriptions" icon="laptop-code">
    Monthly software payments in stablecoins
  </Card>

  <Card title="Content Memberships" icon="newspaper">
    Creators receive recurring support
  </Card>

  <Card title="Utility Bills" icon="bolt">
    Automated payments for services
  </Card>

  <Card title="Streaming Services" icon="video">
    Netflix-style subscription model
  </Card>

  <Card title="Payroll" icon="building">
    Automated team payments
  </Card>

  <Card title="DeFi Strategies" icon="chart-line">
    Recurring DCA purchases
  </Card>
</CardGroup>

***

## Industry Validation

<Card title="Visa's Auto-Payments Proposal" icon="credit-card" href="https://usa.visa.com/solutions/crypto/auto-payments-for-self-custodial-wallets.html">
  Major payment networks are recognizing the need for crypto subscription
  infrastructure
</Card>

***

## Ready to Build?

<Steps>
  <Step title="Test the system">
    Try recurring payments for free before going live
  </Step>

  <Step title="Integrate into your app">
    Add subscription payments to your product
  </Step>

  <Step title="Start accepting recurring revenue">
    Launch your subscription business on Ethereum
  </Step>
</Steps>

***

## Get Started

<CardGroup cols={2}>
  <Card title="Try Demo" icon="flask" href="/auto-payments/checkout">
    Test recurring payments with our sandbox
  </Card>

  <Card title="Integration Guide" icon="code" href="/api-reference/auto-payments/request">
    Add subscriptions to your application
  </Card>
</CardGroup>

***

## Learn More

<AccordionGroup>
  <Accordion title="What is Account Abstraction (ERC-4337)?">
    Account Abstraction transforms Ethereum accounts into programmable smart contracts, enabling features like:

    * Automated transactions
    * Gasless transactions
    * Social recovery
    * Session keys
    * Batch operations

    [Read EIP-4337 →](https://eips.ethereum.org/EIPS/eip-4337)
  </Accordion>

  <Accordion title="Is this secure?">
    Yes. Security features include: - User sets spending limits - Payments limited
    to approved merchants - Frequency restrictions enforced on-chain - User can
    cancel anytime
  </Accordion>

  <Accordion title="How is this different from giving access to my funds?">
    **Traditional approach (bad):** Service holds your private key\
    **Account Abstraction (good):** You control keys, smart contract enforces rules

    You never give up custody - you just pre-approve specific actions within strict parameters.
  </Accordion>
</AccordionGroup>