Sign in
Events/Orders
order.createdBuyer-initiated

Order created

A buyer completed checkout and Paystack confirmed payment.

When this fires

A buyer finished checkout and Paystack confirmed the payment. This is the canonical 'new order' signal.

High frequency
This event is buyer-initiated, which means it can fire at checkout-traffic volume during busy periods. Make sure your handler responds in under ten seconds; queue any heavy work.

Sample payload

This is the exact envelope shape we POST to your endpoint — outer wrapper plus the per-event data payload. Field values are randomised on each render so you see the general shape, not a fixed example.

json
{
  "id": "8d05a08e-0669-40a4-bd12-9ed7d9d22d78",
  "event": "order.created",
  "created": "2026-10-28T01:10:51.251Z",
  "data": {
    "id": "c2gkj6o099kw0000000000000",
    "number": "TY-F4GABDH",
    "totalKobo": 10307356,
    "itemCount": 4,
    "customer": {
      "name": "Bukola Adebayo",
      "email": "bukola.adebayo66@gmail.com",
      "phone": "+2348128121700"
    },
    "shippingAddress": {
      "line": "Gana Street, Maitama",
      "city": "Abuja",
      "state": "FCT",
      "country": "NG"
    },
    "currency": "NGN"
  }
}

Use cases

  • Print or send a packing slip to the merchant's fulfilment desk.
  • Push the order into your ERP / accounting system in real time.
  • Notify a Slack channel so the team knows a high-value order just landed.

Subscribe in the dashboard

To start receiving this event, add it to a webhook's subscription list in Developers → Webhooks. Wildcard subscriptions ( order.*) work too — see the webhooks guide for the matching rules.