Developers 路 RecurCrypto

Developer hub for recurring crypto payments

Start with the documented Polygon/USDC integration: merchant API reference, quickstart, webhook guidance, and server-side API keys. V5 multichain remains an offline prototype, not a live payment option.

API reference

Endpoints, auth model, OpenAPI JSON, and response shape for plans, checkouts, subscriptions, and events.

Open API docs

Quickstart

Create a merchant API key, request a plan, wait for provisioning, then obtain a checkout URL. No API response alone proves settlement.

Read quickstart

Webhook docs

Event names, payload examples, signature model, and practical guidance for syncing product access.

Read webhooks

Dashboard API tools

Generate or rotate your merchant API key directly from the dashboard and copy implementation details.

Open dashboard API

Recommended integration sequence

Start with a Polygon/USDC plan and wait for provisioning before sharing checkout. A submitted wallet transaction or a webhook delivery is not proof of final settlement. Verify the subscription and chain evidence before granting access. Keep API keys server-side and make webhook handling idempotent to avoid duplicate access. Renewal terms and cancellation must remain visible to the payer.

USDC subscription billing: current fees and network scope

During prelaunch the effective platform fee is Free 0%. A future 1% per operationis inactive and requires explicit activation and new informed consent; no retroactive charges or fixed fee. Network gas is separate. Polygon/USDC is the existing integration focus; Polygon, Base and Arbitrum USDC in V5 are offline simulations, not production payment rails. No hidden swaps or bridges are performed.

For a stablecoin recurring billing API, begin with the USDC quickstart, check the actual API contract, and readsettlement and reorganization guidance. Customers must be able to see renewal terms and cancel their subscriptions without understanding blockchain networks.

What developers can do

Create plans programmatically; a PROVISIONING response is not an on-chain confirmation. Obtain checkout URLs only after verifying the plan state.
Read subscriptions and events with on-chain identifiers; grant access only after independently verified settlement.
Connect webhook delivery to your backend so product access stays aligned with chain activity.
Use dashboard API tooling to create, rotate, and revoke merchant API keys without leaving the product.