The payment_configuration_update field reports changes to a WABA's payment configurations for Meta's Payments API India and Payments API Brazil. A payment configuration links the WABA to a payment gateway account and is referenced by name in Order Details messages.
What payment_configuration_update Reports
| Field | Notes |
|---|---|
configuration_name | The payment configuration name used in Order Details messages, for example razorpay-prod. |
provider_name | The payment gateway: billdesk, payu, razorpay, or zaakpay. |
provider_mid | The merchant account ID at the payment gateway. |
status | Active, Needs Connecting, or Needs Testing. |
created_timestamp | Unix timestamp when the configuration was created. |
updated_timestamp | Unix timestamp of this update. |
The status values are mixed-case strings with spaces, not uppercase enums:
status | Meaning |
|---|---|
Needs Testing | Connected to the payment gateway, but still needs testing in WhatsApp Manager. |
Active | Tested in WhatsApp Manager and usable with the Payments API. |
Needs Connecting | Disconnected from the payment gateway and must be connected again. |
When It Fires
Meta sends it when a payment configuration on the WABA is connected to a payment gateway account, disconnected from one, or becomes active.
Payload Shape
{
"object": "whatsapp_business_account",
"entry": [
{
"id": "<WABA_ID>",
"time": 1739321024,
"changes": [
{
"field": "payment_configuration_update",
"value": {
"configuration_name": "razorpay-prod",
"provider_name": "razorpay",
"provider_mid": "acc_GP4lfNA0iIMn5B",
"status": "Needs Testing",
"created_timestamp": 1748827100,
"updated_timestamp": 1749320300
}
}
]
}
]
}Dualhook Handling
Dualhook subscription: not subscribed. Dualhook's Meta app does not subscribe to payment_configuration_update, so a Dualhook connection never delivers it to you, and Meta does not list it among the fields that support Webhook Override. To receive it, subscribe your own Meta app to the field and to the WABA.
Dualhook does not create, test, or manage payment configurations, and the Runtime API has no payment configuration routes. Set them up and test them in WhatsApp Manager.
Implementation Notes
- Compare
statusas an exact string, including the space and capitalization. - Stop sending Order Details messages that reference a configuration once it reports
Needs Connecting. - Key stored state on
configuration_nameper WABA, and useupdated_timestampto ignore out-of-order deliveries.