2026-04 whenever possible.https://docs-v2.useepay.com/8649675m0.application/json.| Field | Type | Description |
|---|---|---|
id | string | Event ID, a unique identifier starting with evt_ |
name | string | Event name, in the format object.event_type |
data | object | Business object data, such as PaymentIntent, Subscription, Invoice, Refund, CheckoutSession, Dispute, etc. |
{
"id": "evt_79bdd43e4d0f464694fa433a5d467980",
"name": "payment_intent.succeeded",
"data": {
"id": "pi_1234567890",
"object": "payment_intent",
"amount": 10000,
"currency": "USD",
"status": "succeeded",
"customer_id": "cus_abc123",
"payment_method": {
"type": "card",
"card": {
"brand": "visa",
"last4": "4242"
}
},
"created_at": "2024-01-27T10:30:00Z",
"metadata": {}
}
}Business Event Occurs
↓
UseePay System Detects Status Change
↓
Webhook Event Generated
↓
HTTP POST to Your Webhook URL
↓
Your Server Processes Event2xx HTTP status code as soon as the event is received.event.id to implement idempotency and avoid duplicate processing.id, name, and data from the request body.2xx as soon as the event is received.event.id for idempotency handling.2xx status code or times out, UseePay will automatically retry sending the webhook with the following intervals: