Stripe webhook (server-to-server)

Stripe-to-Belga webhook. This is the authoritative trigger for fulfilment. On a payment-success event the Belga backend: 1. runs the registry fulfilment handler for the payment's resourceType using
its resourceId (for press_release: publishes that press release);
2. if the resource action succeeds: sets status: succeeded and triggers Belga's
own invoice through the existing Salesforce middleware (Stripe does NOT send
the invoice; the invoice is sent ONLY when payment AND publish both succeed);
3. if the resource action fails: refunds the payment via Stripe and sets
status: refunded (no invoice). The front-end then shows a failed/refunded
state.

On a payment-failure event, the Payment is set to failed.

This endpoint is NOT called by the front-end and uses no user authentication. It is secured by verifying the Stripe-Signature header against the Stripe webhook signing secret. The request body is the raw Stripe event; the schema below is illustrative only.

Request

Authorization

OAuth 2.0

Authorization Code

Add the parameter

Authorization

to Headers，whose value is to concatenate the Token after the Bearer.

Example:

Authorization: Bearer ********************

Authorize URL: https://sso.ssl.belga.be/auth/realms/belga/protocol/openid-connect/auth

Token URL: https://sso.ssl.belga.be/auth/realms/belga/protocol/openid-connect/token

Scopes:

offline_access-Offline access

openid-OpenID

profile-Profile

email-Email

Header Params

Body Params application/jsonRequired

Examples

curl --location 'https://api.belga.press/belgapress/api/payments/webhooks/stripe' \ --header 'Stripe-Signature;' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "id": "evt_1Nf1Qe2eZvKYlo2C", "type": "checkout.session.completed", "data": { "property1": "string", "property2": "string" } }'

Stripe webhook (server-to-server)

Request

Responses