Webhook
Instant event trigger notifications !
A webhook is a way for an application to provide other applications with real-time information. Essentially, a webhook sends data from one application to another as soon as an event occurs, allowing for immediate communication and integration between different systems.
For example, when a specific event occurs in your system, such as a successful payment or a new order, a webhook can automatically send that data to another application or service that needs to know about it. This eliminates the need for manual checks or polling for updates, making the process more efficient and allowing systems to stay synchronized in real-time.
In short, webhooks enable automated, real-time data sharing between applications, improving integration and responsiveness.
Security
when we send webhook events to your system, please confirm whether the signature is correct.
Common
Application
Event |
---|
application.base_information.updated |
Webhook
Event |
---|
webhook.created |
webhook.updated |
webhook.deleted |
webhook.renew.secret |
Agent
Event |
---|
agent.created |
agent.updated |
agent.deleted |
agent.invite.created |
agent.invite.deleted |
B2B payout solution events
Order
Event |
---|
order.received |
order.updated |
order.cancelled |
order.payout.succeed |
Vendor
Event |
---|
vendor.created |
vendor.updated |
vendor.deleted |
vendor.base_information.updated |
vendor.invite.created |
vendor.invite.resend |
vendor.visa.card.created |
Reconciliation
Event |
---|
reconciliations.created |
reconciliations.reject |
reconciliations.settled |
reconciliations.draft_audit.need_check.created |
reconciliations.draft_audit.need_correction.created |
Accounting
Event |
---|
accounting.created |
accounting.executed |
accounting.deleted |
accounting.payout.succeed |
accounting.payout.failed |
Merchant acquiring solution
Customer
Event |
---|
customer.created |
customer.updated |
customer.deleted |
Payment Intent
Event | Description |
---|---|
payment_intent.created | When your user initializes payment_intent. |
payment_intent.checking_out | When the consumer(customer) encounters 3DS (OTP) verification during the authorization process, we will return this event. |
payment_intent.authorized | When the consumer(customer) authorization is completed |
payment_intent.cancel_authorization | We can support you to pre-authorize consumers (customers), but choose to capture at a certain point in time. |
payment_intent.captured | The system defaults to using the T+1 time for automated capture. If you need to turn off automated capture, please contact your Account Manager. |
payment_intent.partial_captured | OwlPay supports the partial capture function, and when this Event occurs, usually your payment_intent status will return |
payment_intent.failed | When your transaction encounters some unexpected behavior at the beginning, we will return failed event. |
payment_intent.refund_created | If the status of the payment_intent is |
payment_intent.refunded | We will return this event when the refund has been successfully returned to the consumer (customer). |
payment_intent.refund_cancelled | Of course, you can also call Cancel a Payment Intent Refund to cancel the refund before the refund is completed. |
payment_intent.financial.reviewed | When OwlPay confirms that your payment can be settled, you will receive this event. |
payment_intent.request_settle | We currently automate this event. When your payment reaches the checkout cycle, the system will automatically trigger this event. |
payment_intent.payout_finished | When you call Settle a Payment Intent , and OwlPay payout to your bank. |
payment_intent.payout_failed | When you call Settle a Payment Intent , and OwlPay payout to your bank failed, funds were not successfully disbursed. |
payment_intent.voided | Used for void Captured. currently, if you call Cancel Transaction , we will cancel authorization together. |
payment_intent.updated | This event is returned when the Payment Intent is updated via Update a Payment Intent . |
Updated 25 days ago