Webhook usage
Use webhook notifications to react to PayNowPro activity in your own systems.
Webhooks are outbound notifications for PayNowPro activity. Use them to keep your application in sync with payment, customer, product, price, and subscription changes without asking your customers to wait for a browser redirect or manual refresh.
Design your receiver
Your webhook receiver should:
- Accept requests at a dedicated HTTPS endpoint in your application.
- Validate the event against the webhook configuration and documentation provided for your account.
- Hand the event to durable background processing as quickly as possible.
- Return a successful HTTP response only after your application has accepted the event for processing.
- Keep a record of the business action you performed so repeat deliveries do not create duplicate side effects.
Do not rely on a return URL or browser session as the only signal for a payment or subscription change. Use the relevant webhook event or account-supported status flow before granting access or fulfilling an order.
Event categories
The sidebar documents the available event categories:
- Customer lifecycle events
- Product, product-group, and price events
- Subscription creation, cancellation, upgrade, and downgrade events
- Transaction and recurring-transaction events
Use the event-specific page to understand the intended business meaning. Configure and test only the events your application needs.
Keep processing separate from delivery
Your receiver should acknowledge delivery promptly and process longer-running work asynchronously. For example, a subscription event can update your application's billing state in a queue worker rather than inside the HTTP request.
Keep webhook payloads out of client-side logs and avoid including payment details, API keys, or other secrets in error messages.
Next, read Webhook retries and Webhook security.