• France
status page
Demo shops
assistance
FAQContact support
Search
Categories
Tags
Europe (English)
France
Spain
Europe (English)
India
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
SDD mandates by REST API
Snippets
Payment methods
Plugins
Marketplace
Guides
Merchant Back Office
Back Office Expert
Functional guides

Defining the webhook address

A webhook implies that you provide the API with an address for receiving information.

As mentioned earlier, webhooks are defined by object type. You can therefore define as many access points as there are objects to track.

These access points must be able to receive and process POST calls with the Content-Type: application/json header, and the following content:

{"<event_type>":"<uuid>"}

For example:

{"order":"dd5e4c4c-2c07-4af8-ae30-15f4c6d5b5e5"}

Currently, the objects concerned are:
  • order
  • token
  • registrations
  • refund

Each time a webhook is created or modified, a notification test is performed with an empty request body to which your server must respond with a 200 status (see chapter Registering, modifying or deleting a webhook).

To increase your process security, you can check that the webhook originates from the IP range 194.50.38.0/24.

Jobs
Legal
GDPR
25.18-1.11