# Webhook - Payment Authorized

## 1. Webhook Overview

### Purpose

[context]
This Webhook event is sent from the EBP system to the store when a user successfully completes payment authorization through a payment method.<br>
Through this event, the store can verify the payment authorization status in real-time and proceed with subsequent processes such as capture requests or order confirmation.
[/context]

> **Note**: A registered URL is required to receive Webhooks. (Contact: [ebp-server@lge.com](mailto:ebp-server@lge.com))

> **Important Notes on Auto Capture**:
> - If the `autoCapture` field is set to `true` when calling the Create Payment Intent (`payment-intents`) API, capture is processed simultaneously with authorization.
> - In this case, depending on the PG and payment method, the `PAYMENT_AUTHORIZED` webhook may be skipped, and only the `PAYMENT_CAPTURED` webhook may be sent.
> - Even if both authorization and capture webhooks are sent, the sequence of receipt is not guaranteed due to the system environment. Merchants should consider this when designing their systems.

### Details

[table:key-value]
| Item | Value |
| :--- | :--- |
| **Webhook Name** | Payment Authorized |
| **Event Type** | `PAYMENT_AUTHORIZED` |
| **HTTP Method** | [badge:POST,blue,lg] |
| **Region** | [badge:Global,green-subtle,lg] |
[/table]

@@include:webhook-authentication.md@@

## 3. Data Schema

### 3.1. Payload Data Schema

| depth | Field | Details & Description |
| :--- | :--- | :--- |
| -1 | eventType | [type:string] [req:Yes] [desc:Event type] [eg:PAYMENT_AUTHORIZED] |
| -1 | eventTime | [type:string] [req:Yes] [desc:Timestamp when the event occurred[tooltip:UTC, ISO-8601]] [eg:2025-12-30T07:19:28Z] |
| -1 | data | [type:object] [req:Yes] [desc:Detailed payment authorization data] |
| 0 | orderNo | [type:string] [req:Yes] [desc:Order number issued by EBP] [eg:ORD_7202603277730794] |
| 0 | paymentStatus | [type:string] [req:Yes] [desc:Payment status code] [eg:AUTHORIZED] |
| 0 | authorizedAmount | [type:number] [req:Yes] [desc:Authorized amount] [eg:1250000] |
| 0 | currencyCode | [type:string] [req:Yes] [desc:Currency code. ISO 4217] [eg:USD] |
| 0 | exponent | [type:number] [req:Yes] [desc:Currency decimal exponent] [eg:2] |
| 0 | resultCode | [type:string] [req:Yes] [desc:EBP result code ('0' for success)] [eg:0] |
| 0 | resultMessage | [type:string] [req:Optional] [desc:Result message] [eg:SUCCESS] |
| 0 | authorizedAt | [type:string] [req:Yes] [desc:Timestamp when the payment was authorized[tooltip:UTC, ISO-8601]] [eg:2025-12-30T07:19:28Z] |
| 0 | pgProvider | [type:string] [req:Yes] [desc:Payment Gateway provider] [eg:WORLDPAY, CNSPAY] |

## 3.2. Payload Example

### HTTP Request
```http
POST /your-webhook-endpoint HTTP/1.1
Content-Type: application/json
x-webhook-signature: 25f0e... (HMAC-SHA256 Hex String)
x-webhook-signature-timestamp: 1735543168 (Unix Epoch Seconds)

{
  "eventType": "PAYMENT_AUTHORIZED",
  "eventTime": "2025-12-30T07:19:28Z",
  "data": {
    "orderNo": "ORD_7202603277730794",
    "paymentStatus": "AUTHORIZED",
    "authorizedAmount": 1250000,
    "currencyCode": "USD",
    "exponent": 2,
    "resultCode": "0",
    "resultMessage": "SUCCESS",
    "authorizedAt": "2025-12-30T07:19:28Z",
    "pgProvider": "WORLDPAY"
  }
}
```