Fern Developer Docs
  • Overview
    • Fern overview
    • Earning revenue with Fern
    • Developer dashboard
    • Help & support
  • Coverage
    • Customer types
    • Restricted customer geographies
  • Fiat currency support
  • Cryptocurrency support
  • Guides
    • Core API concepts
    • Create and verify customers
      • Requirements for Individuals
      • Requirements for Businesses
      • Customer statuses
      • Country codes
    • Create Fern wallets
    • First-party onramps
    • First-party offramps
    • Webhooks
      • Events
      • Sample Payloads
      • Verification
      • Retries
  • API reference
    • Customers
    • Payment accounts
    • Quotes
    • Transactions
      • Additional details
  • Advanced
    • Slippage and price impact
    • Rate limits
Powered by GitBook
On this page
Export as PDF
  1. Guides
  2. Webhooks

Retries

Fern automatically retries webhook deliveries if your server does not respond with a 2xx HTTP status code.

Retry Policy

Each webhook event will be attempted up to 4 times total (1 initial + 3 retries) using an exponential backoff strategy:

Attempt

Delay Before Retry

1st

Immediate (no delay)

2nd

5 seconds

3rd

30 seconds

4th

1 minute

If all attempts fail (i.e., your endpoint continues to return a non-2xx response or times out), the webhook will be marked as undelivered and no further attempts will be made.

We recommend that your webhook handlers are idempotent and respond quickly (within 5 seconds). To ensure reliability, log incoming webhook ids (from the payload id ) and avoid side effects on duplicate deliveries.

Last updated 8 days ago