Webhook for Payment and Capture API

[ArvindDave]

We are currently receiving webhook events from Fraud Management Essentials (for example, risk.profile.decision.monitor) during the pre-authorization flow.

Our requirement is to update transaction status in our database for every Payments API flow, including authorization, capture, and settlement.

Could anyone please confirm:

• Which Payments product webhook events should be subscribed to in order to reliably track the full payment lifecycle?

• Whether the following events are the correct ones to use:

  • payments.authorized

  • payments.capture.status.accepted

  • payments.capture.status.updated

  • payments.settlement.status.completed

  • payments.settlement.status.updated

• If there are any alternative or additional events we should rely on instead of Fraud Management Essentials events for payment status updates.

This is my webhook details : 

{
"status": "ACTIVE",
"products": [
{
"productId": "payments",
"eventTypes": [
"payments.authorized",
"payments.capture.status.accepted",
"payments.capture.status.updated",
"payments.settlement.status.completed",
"payments.settlement.status.updated"
]
},
{
"productId": "alternativePaymentMethods",
"eventTypes": [
"payments.payments.updated"
]
}
],
"retryPolicy": {
"algorithm": "ARITHMETIC",
"firstRetry": 1,
"interval": 1,
"numberOfRetries": 3,
"deactivateFlag": false,
"repeatSequenceCount": 0,
"repeatSequenceWaitTime": 0
},
"securityPolicy": {
"securityType": "key"
},
"version": "3",
"createdOn": "2025-11-03T10:35:41.840390",
"updatedOn": "2025-12-17T14:11:01.077Z",
"notificationScope": "DESCENDANTS"
}

Your guidance will help ensure we are using the correct events as per CyberSource best practices.

Thank you for your assistance.

[Elio]

Subscribe to these Payments API webhook events to track the full payment lifecycle: payments.authorized, payments.capture.status.accepted, payments.capture.status.updated, payments.settlement.status.completed, and payments.settlement.status.updated. Avoid relying on Fraud Management Essentials events for transaction status updates. This ensures accurate tracking of authorization, capture, and settlement stages.

[Minato2d]

I’m using the same approach in production. For tracking the full payment lifecycle, you should rely on Payments product events, not Fraud Management Essentials, which are only for risk decisions.

The events you listed are the correct ones for authorization, capture, and settlement, and your configuration looks aligned with CyberSource best practices. Fraud events can be kept for risk visibility, but they shouldn’t drive transaction status updates.