RecurCrypto
Create planCrear plan
Webhooks 路 RecurCrypto API

Webhook documentation for recurring crypto payments

Webhooks keep your backend aligned with subscription lifecycle activity. Use them to update access, internal account state, or support tooling whenever a subscription changes.

API docsConfigure webhook URL

Event types

  • subscription.created
  • subscription.charged
  • subscription.payment_failed
  • subscription.cancel_at_period_end_set
  • subscription.cancelled
  • subscription.ended

Payload example

{
  "id": "evt_001",
  "type": "subscription.charged",
  "createdAt": "2026-04-07T10:00:00Z",
  "data": {
    "subscriptionId": "sub_123",
    "planId": "plan_123",
    "customerExternalId": "user_789",
    "subscriberAddress": "0xabc...",
    "amount": "19.99",
    "currency": "USDC",
    "txHash": "0x...",
    "status": "active",
    "nextPaymentAt": "2026-05-07T10:00:00Z"
  }
}

Implementation notes

  • Use the merchant dashboard settings page to store your webhook URL and secret.
  • Deduplicate by event id and make delivery idempotent in your backend.
  • Treat the chain as contractual truth; use webhook delivery to accelerate UX and internal system updates.
  • Reconciliation should preserve on-chain identifiers like subscription id, plan id, and transaction hash.