**Last updated**: 28 October 2025 | [**Change log**](/products/events/changelog/)

# Card/APM event webhooks

Receive status updates from Access Worldpay by setting up a webhook.

### What is a webhook?

Access Worldpay webhooks provide you with real-time information about the status of your requests. Setting up a webhook means you automatically receive updates when there is a status change with your request.

## Boarding with us

Contact your Implementation Manager to add your webhook URL and enable or disable the events based on your requirement.

Info
The webhook destination (URL) must use an encrypted connection  (`https`) and must also have a certificate signed by a trusted certificate authority.

## Receiving the webhook

### Network access

The webhooks originate from the following set of IP addresses and the HTTPS port; 443. Ensure your Web Application Firewall(WAF) allows the webhooks to be received for the following addresses. The full set of IP's must be whitelisted for each of your environments.

#### IP list


```
34.246.73.11
52.215.22.123
52.31.61.0
18.130.125.132
35.176.91.145
52.56.235.128
18.185.7.67
18.185.134.117
18.185.158.215
52.48.6.187
34.243.65.63
3.255.13.18
3.251.36.74
63.32.208.6
52.19.45.138
3.11.50.124
3.11.213.43
3.14.190.43
3.121.172.32
3.125.11.252
3.126.98.120
3.139.153.185
3.139.255.63
13.200.51.10
13.200.56.25
13.232.151.127
34.236.63.10
34.253.172.98
35.170.209.108
35.177.246.6
52.4.68.25
52.51.12.88
108.129.30.203
```

### Validating

We strongly recommend that you perform one of the following checks to ensure the webhook received is from us and has not been tampered with.

* [Certificate check](/products/events/certificate)
* [Signature (HMAC)](/products/events/signature)


### Card/APM event acknowledgement

Respond with a HTTP(S) response code `200` to confirm you've received the event.

Warning
Not acknowledging can cause delays (or loss) of subsequent events in the queue.

* If a `200` event confirmation response is not received within 10 seconds, we retry the event until the confirmation is received.
* Retry intervals increase based on the number of attempts, the time intervals increase starting 30 seconds to 2 hours per event.
* The retry mechanism stops re-sending each event after either; an acknowledgement (`200`) is received, or after one week of attempting to send the event.


## Supported card/APM events

- [Payment](/products/events/openapi/payment) ([Card Payments](/products/card-payments/) and [Payments](/products/payments/) API)
- [Payout](/products/events/openapi/payout) ([Card Payouts API](/products/card-payouts/)) - for **account payout** events see our [Account Payout Event Webhooks guide](/products/account-payouts/account-events)
- [Chargeback](/products/events/openapi/chargeback)


* For [basic disbursement](/products/card-payouts/payouts/#payout-request) payouts the `sentForRefund` payment event is used.
* The payment `error` event is shared for both payment and payout related events.