# Payout notification

> POST to your notification URL
> Sent by Ozow. Part of the Payouts API reference. Source: https://hub.ozow.com/api-reference/payouts-api/webhooks/notification-response/

Sent to the notification URL once a payout reaches a final status.

The URL comes from the `NotifyUrl` field on the payout request, or from the site configuration in the merchant admin site. Without one, no notification is sent.

Verify the `hashCheck` field before acting on the contents. A notification is an unauthenticated POST to a URL that anyone can call.

**The same payout can be notified more than once.** Ozow works to avoid duplicates and cannot guarantee their absence, so your handler must be idempotent: a repeated notification for a payout you have already processed must not credit or debit anyone a second time.

## Authentication

Ozow sends no credential with this call, so this check is the only thing standing between a real delivery and a stranger’s. Verify the hashCheck field before acting on the contents: your notification URL is public, and anyone can post to it.

## Payload

**application/json**

- `payoutId` (string, uuid) - Ozow's unique reference for the payout.
- `siteCode` (string, required, max length 50) - A unique code for the site currently in use. A site code is generated when adding a site in the Ozow merchant admin section. [Please contact support for SiteCode - support@ozow.com]
- `merchantReference` (string, required, max length 20) - The merchant's reference for the transaction.
- `customerMerchantReference` (string, required, max length 20, pattern ^[A-Za-z0-9 -]+) - The reference that will be prepopulated in the "their reference" field in the customers online banking site. This will be the payout reference that appears on the merchant’s bank statement and can be used for recon purposes.
- `payoutStatus` (object, required) - Payout status.
- `hashCheck` (string, required) - SHA512 hash used to ensure that certain fields in the message have not been altered after the hash was generated. Check the generate hash section in the documentation for more details on how to generate the hash.

## Your response

### 200 Acknowledged. Return this once you have stored the notification.

No body.