Customer payment flow
This is the simplest way to explain the RecurCrypto experience to a merchant team: the customer connects a wallet, approves explicit subscription terms, and later renewals may run only while authorization remains valid.
Customer opens checkout
The customer lands on the merchant checkout page or a direct RecurCrypto payment link for a specific plan.
Wallet connection
The customer connects a compatible wallet and sees the plan information, amount, and billing cadence.
First approval and setup
The customer approves the required token usage and confirms the subscription creation flow.
Subscription confirmation
The merchant verifies the confirmed payment and subscription state before granting paid access. A wallet prompt, pending transaction or simulation is not proof of settlement.
Authorized renewals
Later charges require an active mandate, sufficient balance and allowance, and successful confirmation. Cancellation or revoked consent must prevent further attempts.
Status changes are sent to the merchant
When something important happens, the merchant backend can receive webhook events and update its own records.
Why this matters for the merchant
The merchant should not think of RecurCrypto as a one-time crypto payment only. The key value is the subscription relationship that supports recurring billing.
The first checkout experience is where trust, clarity, and activation happen. That page should clearly explain plan name, billing cadence, customer benefits, and what happens after payment.
From a support perspective, the merchant should also know that later renewals can happen without repeating the whole onboarding journey, which reduces friction for returning billing cycles.