React to every payment event as it happens.

Webhooks push payment, payout, refund and settlement events to your server in real time — so your systems, and any AI agent working for you, act on changes instead of polling for them.

Request Sandbox Access API Reference

Payments
Payouts
Refunds
Settlements

What webhooks are

Paynancial tells you when something changes.

When a payment, payout, refund or settlement changes state, Paynancial sends an HTTPS request to an endpoint on your server describing what happened. Your server responds, and then does whatever that event means for your business — fulfilling an order, marking a vendor as paid, updating your books.

Webhooks also give you a real-time, timestamped record of every state change in your account. That is the same data an audit trail draws from, and the reason an automated workflow can react to events instead of checking for them on a schedule.

Events

Four families of events.

For the exact event names and payload fields for your account, contact developer support.

Webhook event families
Event family	Sent when	Typical action in your system
Payments	A payment changes state, for example when it succeeds or fails.	Fulfil the order or release the service.
Payouts	A payout changes state.	Mark the vendor, employee or partner as paid.
Refunds	A refund changes state.	Update the customer's order and notify them.
Settlements	Funds are settled to your account.	Reconcile settled amounts against your books.

Building a reliable handler

Six rules for a reliable webhook endpoint.

These are general practices for receiving webhooks from any payments platform, and they apply to Paynancial.

01
Use an HTTPS endpoint
Receive events on a URL served over HTTPS, reachable from the internet.
02
Respond quickly
Acknowledge the request as soon as you have stored it, then do slow work — emails, fulfilment — afterwards.
03
Expect duplicates
Record which events you have processed and skip any you have already handled.
04
Do not rely on order
Do not assume events arrive in the order they happened. Act on the state each event describes.
05
Verify the source
Before going live, confirm with developer support how to check that a request came from Paynancial.
06
Log everything
Keep the raw event and your response. When something goes wrong, the log is the first thing you will need.

Event-driven automation

Why agents need webhooks.

An AI agent reconciling a ledger or retrying a failed collection needs to know the moment something changes. Webhooks give it that signal without polling, and the idempotency keys it sends on write requests mean acting on an event twice cannot create a duplicate payment or payout.

Pair event-driven agents with the permissions, policy limits and approval thresholds described on the AI Governance page.

Without webhooks: The agent asks on a timer whether anything changed, reacts late, and spends most requests learning nothing.
With webhooks: The agent is told the moment a payment, payout, refund or settlement changes, and acts on it immediately.

FAQ

Webhook questions.

What is a Paynancial webhook?

An HTTPS request Paynancial sends to a URL on your server when something happens in your account — a payment, payout, refund or settlement changes state — so your system learns about it immediately instead of asking repeatedly.

Which events does Paynancial send?

Events for payments, payouts, refunds and settlements. For the exact event names and payload fields for your account, contact developer support.

Why use webhooks instead of polling?

Polling asks "has anything changed?" on a timer, which is slow when something has changed and wasteful when nothing has. A webhook arrives when the change happens, so orders are fulfilled and payouts marked paid in real time.

Can I receive the same event more than once?

Design for it. Any system that retries delivery can deliver an event twice, so make your handler safe to run more than once for the same event.

How do I test webhooks?

Test your handler in the Sandbox before going live, and confirm with developer support how events are delivered for sandbox activity.

Test your webhook handler in the Sandbox.

Build and test your integration with no real money involved before going live.

Request Sandbox Access Contact Developer Support