Notification Retries

When Ecart Pay sends a notification to your webhook, it expects a successful response from your server (HTTP code 2xx). If it doesn't receive such a response, it will automatically attempt to resend the notification.

Retry Policy

• Total attempts: 5 (1 initial attempt + up to 4 automatic retries)
• Progressive intervals:
  • 1st retry: after 10 seconds
  • 2nd retry: after 15 seconds
  • 3rd retry: after 20 seconds
  • 4th retry: after 25 seconds
  • 5th retry (last): after 30 seconds

⚠️

If after the last attempt a valid response is still not obtained, the webhook will be marked as failed and will not be retried again.

Requirements for a successful response

Your server must return an HTTP status code 2xx (for example, 200 OK, 204 No Content, etc.) for the notification to be considered successfully delivered.

Webhook Notification States

Each webhook delivery attempt can register one of the following states:

Best practices

• Ensure your endpoint is always available and responds in less than 5 seconds.
• Validate security signatures before processing webhook content.
• Respond quickly with a 2xx, even if you need to process the event asynchronously.
• Log received attempts to facilitate debugging.