Skip to main content
The payment.rejected event is sent when a payment attempt is explicitly rejected and does not proceed to processing. This event indicates that the payment was blocked due to validation rules, risk checks, compliance requirements, or other pre-processing conditions.

Example Payload

{
  "event": "payment.rejected",
  "id": "3b8b71e4-8f4e-4e6c-bbb2-1b7b4c6d9e21",
  "data": {
    "payment_id": "9f4e1a2b-3c8d-4f92-9c27-1e5b8c4f7a63",
    "status": "rejected",
    "amount": 599
  },
  "eventGeneratedTime": 1756723891.902114
}

Data Fields

payment_id
string
Unique identifier for the payment transaction.
status
string
Final payment status. Always rejected for this event.
amount
float
Payment amount expressed in the major currency unit (for example, USD).

Handling the Event

Use this event to:
  • Update the payment record to a rejected state
  • Prevent the payment from progressing further
  • Record rejection details for auditing or review
  • Apply application-specific logic based on rejection outcomes