Webhooks¶

Webhooks let your application receive transaction notifications at an endpoint you control. The reference describes the documented payload formats and includes synthetic examples.

Before you begin¶

Arrange webhook configuration for your merchant account with Blackstone support. Provide the HTTPS endpoint where your application will receive notifications and confirm the authentication configuration before enabling delivery.

The legacy Sale subscription groups transaction notifications. Use the transaction details in the payload to determine what happened; the subscription name alone is not a payment status.

Payload¶

The legacy payload contains Request and Response. The response includes ResponseCode, Msg, and Verbiage. Refer to the generated reference for the complete field definitions and examples.

Payload v2 is an optional subscription format with mandatory per-delivery HMAC authentication and a non-expiring opaque secret. See Receiving Events for verification and credential lifetime.

Next steps¶

Use Managing Webhooks in Portal to configure notifications, and follow Receiving Events to implement your endpoint. If you use hosted checkout, see the Payment Links guide.