Payment webhooks
Payments are confirmed by the gateway calling your site, not by the buyer’s browser. Getting this right is the difference between “paid and delivered” and “paid but stuck”. This page explains the webhook and the activity log that helps you debug it.
What the webhook does
When a buyer pays, the gateway sends a signed message to your site. AcquisitionSuite verifies it, marks the order paid, creates or updates the lead, fires automation and sends the receipt. Until that message arrives, the buyer sees a pending screen.
Your webhook addresses
Each gateway has its own address, shown on its tab in Payment Settings (“Webhook URL to configure in your gateway dashboard”):
| Gateway | Address |
|---|---|
| Stripe | https://yoursite.com/?acquis_pay_webhook=1&gateway=stripe |
| Paystack | https://yoursite.com/?acquis_pay_webhook=1&gateway=paystack |
| Flutterwave | https://yoursite.com/?acquis_pay_webhook=1&gateway=flutterwave |
Copy the exact address from your own screen, then paste it into the gateway’s dashboard. For Stripe you must also copy the Signing Secret back into AcquisitionSuite. See Stripe setup.
The webhook activity log
Every event your gateways send is recorded under Payment Settings in Recent Webhook Activity, whether it succeeded or failed. Each entry shows the gateway, the event, the result and the time. If purchases are not being confirmed, this is the first place to look.
Reading the results
- No activity at all: the gateway is not reaching your site. Re-check the webhook address, that your site is publicly reachable over HTTPS, and that no firewall or security plugin blocks it.
- Failed with a signature error: the secret or key does not match. Re-enter it.
- Success but order still pending: reload Orders; if it persists contact support with the log entry.
Buyer-side timeout
If confirmation takes longer than about 60 seconds the buyer sees your Pending / Timeout screen instead. See Success screens. The order still completes when the webhook arrives.
See also Payment not confirmed.