Payment optimized

Last updated: December 17, 2025

This Intelligent Acceptance event informs you if a payment was optimized or was in the unoptimized control group. If optimized, it specifies the optimizations that were applied.


1{
2  "id": "evt_caxmnvuvbe4elkbdx2imwbnjxu",
3  "type": "payment_optimized",
4  "version": "1.0.29",
5  "created_on": "2025-05-22T11:56:04.8821546Z",
6  "data": {
7    "payment_id": "pay_jnqu6pfovububi2rgmtj3rvwfu",
8    "is_ia_optimized": true,
9    "is_ia_control_group": false,
10    "optimization_groups": [
11      "Smart Payment Routing",
12      "Adaptive Messaging",
13      "Smart Authentication",
14      "Network Tokens"
15    ]
16  }
17}


1{
2  "id": "evt_caxmnvuvbe4elkbdx2imwbnjxu",
3  "type": "payment_optimized",
4  "version": "1.0.29",
5  "created_on": "2025-05-22T11:56:04.8821546Z",
6  "data": {
7    "payment_id": "pay_jnqu6pfovububi2rgmtj3rvwfu",
8    "is_ia_optimized": false,
9    "is_ia_control_group": true,
10    "optimization_groups": []
11  }
12}

Field name Description

Field name	Description
`id` string	The event's unique identifier, prefixed with `evt_`.
`type` string	The type of event. This value is `payment_optimized`.
`version` string	The webhook's version.
`created_on` date-time	The date and time when the event occurred, in UTC. Standard – ISO 8601 code Example – `yyyy-mm-ddThh:mm:ss.sss`
`data` object	The webhook message.
`data.payment_id` string	The payment's unique identifier, prefixed with `pay_`.
`data.is_ia_optimized` boolean	Indicates whether the payment was optimized by Intelligent Acceptance: `true` – One or more optimizations were applied to the payment. `false` – The payment was intentionally not optimized as part of the control group.
`data.is_ia_control_group` boolean	Indicates whether the payment was part of the control group for testing and measuring optimization impacts: `true` – The payment was intentionally not optimized as part of the control group. `false` – The payment was not in the control group and one or more optimizations were applied.
`data.optimization_groups` array of string	The types of optimization applied to the payment. This can be one of: `Adaptive Messaging` – Adaptive Messaging optimization was applied. `Network Tokens` – Network Tokens optimization was applied. `Smart Authentication` – Smart Authentication optimization was applied. `Smart Payment Routing` – Smart Payment Routing optimization was applied. If the payment was in the control group, the array is empty.

id

string

The event's unique identifier, prefixed with evt_.

type

string

The type of event.
This value is payment_optimized.

version

string

The webhook's version.

created_on

date-time

The date and time when the event occurred, in UTC.
Standard – ISO 8601 code
Example – yyyy-mm-ddThh:mm:ss.sss

data

object

The webhook message.

data.payment_id

string

The payment's unique identifier, prefixed with pay_.

data.is_ia_optimized

boolean

Indicates whether the payment was optimized by Intelligent Acceptance:

true – One or more optimizations were applied to the payment.
false – The payment was intentionally not optimized as part of the control group.

data.is_ia_control_group

boolean

Indicates whether the payment was part of the control group for testing and measuring optimization impacts:

true – The payment was intentionally not optimized as part of the control group.
false – The payment was not in the control group and one or more optimizations were applied.

data.optimization_groups

array of string

The types of optimization applied to the payment.

This can be one of:

Adaptive Messaging – Adaptive Messaging optimization was applied.
Network Tokens – Network Tokens optimization was applied.
Smart Authentication – Smart Authentication optimization was applied.
Smart Payment Routing – Smart Payment Routing optimization was applied.

If the payment was in the control group, the array is empty.

Payment optimized

Example webhooks

Webhook fields