Merchant manuals for RecurCrypto
This documentation area explains what RecurCrypto is, how a merchant gets started, what the customer payment flow looks like, and which webhook events your backend should expect. It is written to help teams integrate faster and explain the system to non-technical stakeholders.
Getting started
What a merchant needs before going live, how to create a plan, where to get the checkout link, and what to validate first.
Open manualCustomer payment flow
A practical explanation of what your customer sees: wallet connect, first approval, subscription creation, and automatic future renewals.
Open manualWebhook events
How to process RecurCrypto events in your backend and keep your product, billing, and user access status synchronized.
Open manualWhat merchants usually want to understand first
1. What does RecurCrypto replace?
RecurCrypto replaces card-first recurring billing flows for merchants who want a wallet-native stablecoin option. Instead of asking the customer for card details, the flow starts with a wallet and stablecoin approval.
2. What happens after the first payment?
After the initial approval and subscription setup, later charges can happen automatically according to the plan rules, which is the core value of recurring stablecoin payments.
3. How does the merchant backend stay in sync?
Your backend listens for webhook events such as creation, charge success, charge failure, or cancellation and updates your own user access, billing state, and notifications.
4. Who is this manual area for?
Founders, developers, product teams, operations teams, and merchants who need a clear explanation of how RecurCrypto fits inside a SaaS, community, AI tool, membership, or digital product.