Payment Links webhooks

Overview

Webhooks are HTTP callbacks that deliver notification messages for events. Peach Payments uses webhooks to inform merchant systems when certain events occur. This way, your servers are always up to date with transaction information.

After configuring and verifying a webhook, Peach Payments delivers POST notifications to the specified URL for the following events:

Webhook eventDescription
initiatedTriggered when you create a payment link.
openedTriggered when a customer opens the payment link.
processingTriggered when a customer attempts to pay.
completedTriggered when a customer completes the payment.
cancelledTriggered when you cancel the payment link.
expiredTriggered when the payment link expires.

📘

  • Peach Payments cannot guarantee the order of webhooks. For example, if your customer initiates a transaction and Peach Payments sends a pending webhook but you have a system issue that causes the webhook to go into exponential backoff, Peach Payments might send the next webhook before the pending webhook gets retried.
  • Payment Links uses Checkout to accept payments. Peach Payments therefore sends you webhooks for Payment Links and Checkout updates. To only receive Payment Links webhooks, contact support.
  • Payment Links sends all webhooks from a known range of IP addresses.

For bulk payment links, Peach Payments sends webhooks for the underlying payment links and for the following batch events:

Webhook eventDescription
initiatedTriggered when you create the batch.
processingTriggered when processing starts on the bulk file.
completedTriggered when Payment Links completes processing of the bulk file.
errorTriggered if Payment Links cannot process the bulk file.
expiredTriggered if you do not upload a file in three hours.

Flow

You can configure webhooks in two ways:

Predefined events, as described above, trigger the webhook.

Webhook flow.

Webhook flow.

  1. The merchant receives a webhook with a result code indicating the updated checkout status.
  2. The merchant returns a 200 status code response acknowledging the webhook.

The merchant can then trigger a query to pull transaction or batch details and statuses.

Webhook retry mechanism

See the Reference materials section for details on the webhook retry mechanism and retry logic.

Webhook events

Peach Payments sends the following webhooks for payment links.

EventParameterTypeExample
InitiatedpaymentIdString00d886d6-4754-4bcc-b88f-74a53d5220e5
statusStringinitiated
urlString (URL)https://l.ppay.io/4c1a48e6dc3b7ebd
OpenedpaymentIdString00d886d6-4754-4bcc-b88f-74a53d5220e5
statusStringopened
ProcessingpaymentIdString00d886d6-4754-4bcc-b88f-74a53d5220e5
statusStringprocessing
CompletedpaymentIdString00d886d6-4754-4bcc-b88f-74a53d5220e5
statusStringcompleted
paymentBrandString enum [VISA, MASTER, DINERS, AMEX, MASTERPASS, MOBICRED, MPESA, 1FORYOU, APLUS, PAYPAL, ZEROPAY, PAYFLEX, BLINKBYEMTEL, CAPITECPAY, MCBJUICE, PEACHEFT]VISA
registrationId*String (optional)8ac7a4a188e7cf090188f7112dbe389a
CancelledpaymentIdString00d886d6-4754-4bcc-b88f-74a53d5220e5
statusStringcancelled
ExpiredpaymentIdString00d886d6-4754-4bcc-b88f-74a53d5220e5
statusStringexpired

* Card registration token, if tokeniseCard was true on the initial request and paymentBrand is a card type.

{
  "status": "initiated",
  "url": "https://l.ppay.io/4c1a48e6dc3b7ebd",
  "paymentId": "00d886d6-4754-4bcc-b88f-74a53d5220e5"
}
{
  "status": "opened",
  "paymentId": "00d886d6-4754-4bcc-b88f-74a53d5220e5"
}
{
  "status": "processing",
  "paymentId": "00d886d6-4754-4bcc-b88f-74a53d5220e5"
}
{
  "status": "completed",
  "paymentId": "00d886d6-4754-4bcc-b88f-74a53d5220e5",
  "paymentBrand": "VISA",
  "registrationId": "8ac7a4a188e7cf090188f7112dbe389a",
}
{
  "status": "cancelled",
  "paymentId": "00d886d6-4754-4bcc-b88f-74a53d5220e5"
}
{
  "status": "expired",
  "paymentId": "00d886d6-4754-4bcc-b88f-74a53d5220e5"
}