# Payment optimized

This [Intelligent Acceptance](https://www.checkout.com/docs/payments/optimize-payments/boost-acceptance-rates.md) event informs you if a payment was optimized or was in the unoptimized control group.
If optimized, it specifies the optimizations that were applied.

## Example webhooks

**Optimized**

```json
{
  "id": "evt_caxmnvuvbe4elkbdx2imwbnjxu",
  "type": "payment_optimized",
  "version": "1.0.29",
  "created_on": "2025-05-22T11:56:04.8821546Z",
  "data": {
    "payment_id": "pay_jnqu6pfovububi2rgmtj3rvwfu",
    "is_ia_optimized": true,
    "is_ia_control_group": false,
    "optimization_groups": [
      "Smart Payment Routing",
      "Adaptive Messaging",
      "Smart Authentication",
      "Network Tokens"
    ]
  }
}  
```

**Control group**

```json
{
  "id": "evt_caxmnvuvbe4elkbdx2imwbnjxu",
  "type": "payment_optimized",
  "version": "1.0.29",
  "created_on": "2025-05-22T11:56:04.8821546Z",
  "data": {
    "payment_id": "pay_jnqu6pfovububi2rgmtj3rvwfu",
    "is_ia_optimized": false,
    "is_ia_control_group": true,
    "optimization_groups": []
  }
} 
```

---

## Webhook fields

| Field name | Description |
| --- | --- |
| `id`<br>`string` | The event's unique identifier, prefixed with `evt_`. |
| `type`<br>`string` | The type of event. <br><br>This value is `payment_optimized`. |
| `version`<br>`string` | The webhook's version. |
| `created_on`<br>`date-time` | The date and time when the event occurred, in UTC. <br>Standard – ISO 8601 code <br>Example – `yyyy-mm-ddThh:mm:ss.sss` |
| `data`<br>`object` | The webhook message. |
| `data.payment_id`<br>`string` | The payment's unique identifier, prefixed with `pay_`. |
| `data.is_ia_optimized`<br>`boolean` | Indicates whether the payment was optimized by Intelligent Acceptance:<br>- `true` – One or more optimizations were applied to the payment.<br>- `false` – The payment was intentionally not optimized as part of the control group. |
| `data.is_ia_control_group`<br>`boolean` | Indicates whether the payment was part of the control group for testing and measuring optimization impacts:<br>- `true` – The payment was intentionally not optimized as part of the control group.<br>- `false` – The payment was not in the control group and one or more optimizations were applied. |
| `data.optimization_groups`<br>`array of string` | The types of optimization applied to the payment.<br><br>This can be one of:<br><br>- `Adaptive Messaging` – [Adaptive Messaging](https://www.checkout.com/docs/payments/optimize-payments/boost-acceptance-rates.md#Adaptive_messaging) optimization was applied.<br>- `Network Tokens` – [Network Tokens](https://www.checkout.com/docs/payments/optimize-payments/boost-acceptance-rates.md#Network_tokens) optimization was applied.<br>- `Smart Authentication` – [Smart Authentication](https://www.checkout.com/docs/payments/optimize-payments/boost-acceptance-rates.md#Authentication_management) optimization was applied.<br>- `Smart Payment Routing` – [Smart Payment Routing](https://www.checkout.com/docs/payments/optimize-payments/boost-acceptance-rates.md#Dynamic_routing) optimization was applied.<br><br>If the payment was in the control group, the array is empty. |