Skip to main content

Webhooks Overview

Webhooks are how Nopan pushes real-time notifications about events in your payment flows.
They allow you to respond to state changes that do not originate from your system - for example, when a shopper finalizes Strong Customer Authentication (SCA), or when a payment is captured asynchronously.

With webhooks you can:

  • Keep your systems in sync with Nopan.
  • React quickly to important events (e.g. trigger fulfillment once a payment is captured).
  • Reduce the need to poll for payment status.
info

Webhooks are delivered as HTTPS POST requests containing a signed JSON payload. Your endpoint must return a 2xx response status to acknowledge receipt.

Quick start​

1. Setting up webhooks

How to expose your endpoint, configure events, and handle retries.

Read setup guide →

2. Event types

See the full catalog of payment events Nopan can deliver.

Browse events →

Key Concepts​

  • Configurable delivery: You choose which event types you want to receive in the Customer Portal.
  • Retries: Nopan retries failed deliveries up to 10 times within 24 hours.
  • Security: Every webhook includes an HMAC signature header. You should always verify it to ensure authenticity.
  • Separation of concerns: Return 202 immediately, then process business logic asynchronously (e.g. via queue/worker).

Delivery Flow​

When to use webhooks​

Webhooks are essential when:

  • You need to know when a payment reaches a terminal state (captured, canceled, expired)
  • You want to react to shopper actions (authorization, cancellation)
  • You prefer push over polling to keep systems synchronized.