FILTER BY TAG

Webhooks Support

Unified Checkout
supports webhooks. You can use webhooks to obtain the complete response from the
completeMandate
call. To receive a webhook notification, you must first subscribe to the webhook.

Prerequisite

Webhook payloads are encrypted. In order to receive a
Unified Checkout
webhook notification, you must enabled message-level encryption (MLE). For information about enabling MLE, see Enable Message-Level Encryptionin the
Getting Started with REST Developer Guide
.

Webhook Events

Unified Checkout
Webhook Events
Product ID
Event Types
Description
unifiedCheckout
uc.orders.transactionresults
Full payload response from the payment service call made by
Unified Checkout

Set Up Webhook Subscriptions

For information on setting up a webhook for the
unifiedCheckout
product, see the How to Set Up Webhook Subscriptions section of the
Webhooks Developer Guide
.

Example Webhook Payload

Example: Webhooks Request for
Unified Checkout
Events
{ "organizationId": "your_merchant_id", "webhookId": "2d55e648-d96c-d727-e063-3cb8d30a938e", "productId": "unifiedCheckout", "eventType": "uc.orders.transactionresults", "eventDate": "2025-03-27T08:44:55", "payload": { "id": "7435188899356405003091", "status": "AUTHORIZED", "outcome": "AUTHORIZED", "details": { "processorInformation": { "transactionId": "2016011808153910011808153AUTH" }, "paymentInformation": { "card": { "type": "001" } }, "riskInformation": { "score": { "result": "42" } } } } }
The
payload
field object contains the same fields as the response from a direct payment authorization request. Use the
id
field for capture requests or to look up a transaction.