Receive payment updates

Connect inbound and outbound notify URLs to your payment records.

Configure destinations

Set Merchant Profile → Transaction Notify URLs in the dashboard. Inbound notifications report collections; outbound notifications report payouts. ZytePe calls your configured URL: this is not a POST /webhooks endpoint on the API host.

Understand the supplied payload

JSON

{
  "txn_id": "3f1fd39c-d4ec-4f7f-bc14-e3134a639f8b",
  "order_id": "ORD-100938",
  "amounts": {
    "gross": 2500,
    "fees": 25,
    "net": 2475
  },
  "status": "completed",
  "utr": "BANKREF98344210",
  "timestamp": "2026-05-03T06:42:10.112Z"
}

This is the supplied contract example. The reviewed local backend additionally emits fields such as event_id, transaction_id, merchant_id, direction and metadata. The deployed payload/version needs confirmation; do not discard unknown fields or require this sample to be exhaustive.

Process updates safely

Verify the callback using the agreed signature contract, correlate its transaction/order identifiers with your records and make processing safe to repeat. Keep a redacted audit trail. Do not invent an event.type envelope from the sample.

Recover missed updates

Use the appropriate signed status GET when confirmation is missing. Exact delivery ordering, acknowledgement expectations, retry timing and retention are not established as a production guarantee here. Confirm these with your integration contact before go-live.