# Payment Notifications
source: https://developer.mastercard.com/open-finance-europe/documentation/unlicensed/aiia-pay/payment-notifications/index.md

Event notifications can be used to create an interactive payment experience for your users. Our service can notify you when a change happens to a payment.

The following steps provide details on how to get the most out of notifications:

1. All event notifications that are relevant for payments
2. Best practices for event notifications

You can read more about how to get started with notifications [here](https://developer.mastercard.com/open-finance-europe/documentation/unlicensed/aiia-pay/event-notifications/index.md).

#### Event notifications for payments {#event-notifications-for-payments}

There are many different event notifications that are offered through the Aiia Pay platform.

Each notification is described below, where we tell you when you receive them and how we suggest that you act on them.

|           **Notification**            |                         **Description**                         |                                                                                                         **Next step**                                                                                                          |
|---------------------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `AccountVerifiedForPayments`          | The status if the account is verified for payments has changed. | API to call - **v1/accounts** If `accounts[].verifiedForPayments = true`. Let your user know that they can now make payments.                                                                                                  |
| `PaymentCreatedWebhook`               | The payment was created.                                        | -                                                                                                                                                                                                                              |
| `PaymentUpdatedWebhook`               | The status of the payment has been updated.                     | API to call - **v2/payments/{{paymentId}}** Retrieve the status of the payment and create an appropriate action for the changed payment status.                                                                                |
| `PaymentAuthorizationCreated`         | The authorisation request was created.                          | -                                                                                                                                                                                                                              |
| `PaymentAuthorizationUpdated`         | The status of the authorisation request changes.                | API to call - **v2/accounts/{accountId}/payment-authorizations/{authorizationId}** Let your user know about the status update (e.g. If the authorisation was approved, you can assure them that authorisation was successful.) |
| `PaymentAuthorizationPaymentsUpdated` | All statuses related to an authorisation have been updated.     | API to call - **v2/accounts/{accountId}/payment-authorizations/{authorizationId}/payments** Notify your users of the updated payments, especially if a status requires an interaction from the user (e.g. a failed payment).   |
| `AccountsOrphanedWebhook`             | The account can no longer be found at the provider.             | API to call - **v1/accounts** If `accounts[].isOrphaned = true`. Notify your user that the account cannot be used for payments.                                                                                                |
| `ConsentRevokedWebhook`               | The user revoked your access to our APIs.                       | API to call - **hv1/oauth/connect** Reach out to re-engage your user.                                                                                                                                                          |

#### Recommended notifications to use {#recommended-notifications-to-use}

To create a valuable experience, we recommend that you make use of all our notifications. There are some notifications that are particularly important.

##### Use **AccountVerifiedForPayments** to finalise onboarding {#use-accountverifiedforpayments-to-finalise-onboarding}

All of your users will be onboarded through the [Connect Flow](https://developer.mastercard.com/open-finance-europe/documentation/unlicensed/aiia-pay/connect/connect-flow/index.md). The onboarding process culminates in a customer due diligence process, where the user needs to fill in information.

Once the onboarding has been finalised, the user is ready to use payments in your product. We suggest that you use this notification to notify your users when they can start using the payments feature in your product by sending an email notifying them that everything is ready to get started.

As the notification tells you when the status of `AccountVerifiedForPayments` changes, you should also use it to let your users know when their account is no longer verified, as they will need to update or re-engage in the customer due diligence process.

##### Communicate with **PaymentAuthorizationUpdated** that authorization has been finalised {#communicate-with-paymentauthorizationupdated-that-authorization-has-been-finalised}

Accounts owned by businesses often require two approvals for an authorisation to be finalised. This means that when the first approver is returned from the flow, a secondary approval is still needed.

Use the notification `PaymentAuthorizationUpdated` to know when the authorization has reached its final status or the authorization has failed. Then you can engage the user with the next step or remind them that the authorization of the payment did not succeed.

##### Use **PaymentUpdatedWebhook** to notify about the outcome of a payment {#use-paymentupdatedwebhook-to-notify-about-the-outcome-of-a-payment}

A payment that has been successfully authorized may stay in the status `pending` for a while. A payment that is in `pending` can still fail or be cancelled by the user.

Use the `PaymentUpdatedWebhook` to be informed of when the payment has succeeded and to let your users know that their payment has succeeded.