Merchant Documentation

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 manual

Customer payment flow

A practical explanation of wallet connect, approval, confirmed subscription state, and conditional future renewals.

Open manual

Webhook events

How to process RecurCrypto events in your backend and keep your product, billing, and user access status synchronized.

Open manual

What merchants usually want to understand first

1. What does RecurCrypto replace?

RecurCrypto adds a wallet-native USDC subscription option alongside existing card billing. Customers choosing that option start with a wallet and stablecoin approval; merchants can keep their current checkout.

2. What happens after the first payment?

After a confirmed initial payment and valid recurring authorization, later charges may be attempted under the plan rules. Each renewal still requires sufficient balance, allowance, an active mandate, and confirmed on-chain settlement; a scheduled attempt is not a successful payment.

3. How does the merchant backend stay in sync?

Your backend verifies webhook authenticity and deduplicates events, then reconciles confirmed payment state through the API. Do not grant paid access from an unconfirmed event or a simulated checkout result.

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.