> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.coinflow.cash/guides/developer-resources/webhooks/configuration-webhooks/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.coinflow.cash/_mcp/server.
# Configuration Webhooks
Configuration webhooks notify you when a change is made to the
merchant-visible settings on your account. Every setting shown on the **Account
Configuration** page is covered — pay-in and pay-out methods and their fees,
chargeback protection, 3D Secure, card-on-file and MIT limits, dynamic
interchange, and geo-blocking. They exist so a Coinflow-side change can't
silently affect your processing without warning.
The feed is still intentionally narrow: it covers only the fields shown on that
page and never includes internal risk, underwriting, or KYC/KYB settings,
downstream processor names, or who made the change.
## Event Types
|
Event Type
|
Description
|
|
Config Method Status Changed
|
A setting on the page was enabled or disabled — a pay-in or pay-out method, chargeback protection, 3D Secure, card on file, or an interchange dimension.
|
|
Config Fee Changed
|
A fee or limit on the page changed — variable, fixed, minimum and maximum fees, fee mode, chargeback and ACH return fees, 3DS threshold, card-on-file caps, and geo-blocking rule counts.
|
Both events are available on **Version 3** webhooks. Subscribe to them like any
other event in your webhook settings.
## Payload
Each event carries a batch of `changes` — a single administrative save that
touches several fields is delivered as one event, not many. Every change is a
clean diff of display values; raw internal values are never included.
**`Config Fee Changed`**
```json Config Fee Changed
{
"eventType": "Config Fee Changed",
"category": "Configuration",
"created": "2026-09-12T00:00:00.000Z",
"data": {
"changedAt": "2026-09-12T00:00:00.000Z",
"changes": [
{
"field": "cardSettings.variableFeeBps",
"label": "Card · Variable fee",
"group": "PayInFees",
"previousValue": "2.5%",
"newValue": "2.9%",
"previousValueRaw": 250,
"newValueRaw": 290
}
]
}
}
```
**`Config Method Status Changed`**
```json Config Method Status Changed
{
"eventType": "Config Method Status Changed",
"category": "Configuration",
"created": "2026-09-12T00:00:00.000Z",
"data": {
"changedAt": "2026-09-12T00:00:00.000Z",
"changes": [
{
"field": "achSettings.processor",
"label": "ACH",
"group": "PayInMethods",
"previousValue": "Not enabled",
"newValue": "Enabled",
"previousValueRaw": false,
"newValueRaw": true
}
]
}
}
```
> **Note**
>
> These notifications are best-effort and cover only changes made through
> Coinflow's audited settings flow. They are not a substitute for reconciling
> your account configuration directly.