Webhook URL is an URL from your server which has an endpoint to receive webhook sent by Xendit as a notification once the invoice has expired, the virtual account has been created and paid (only for Indonesia), or disbursement has been completed.

Xendit will send updates to your webhook URL when there is a notification for your payments. You can add and test your webhook URL here.

If you have a website/application, you need to set up an active URL and ensure that it should always be active and can process your webhook. If not, the end-user will not receive the payment notification you’re sending as well as the confirmation of the payment status.

Xendit has several webhook workflows, such as:

• Money-in

  • invoice: Notification when Invoice has been paid or expired;
  • Subscription
    • recurring: Xendit will send webhook to your system when recurring plan has been activated or deactivated or recurring cycle has been created, failed, succeeded or for each retry attempts.
      • Note: This callback setting does not work for /recurring_payments endpoint
  • Payments API
    • Payment Request
    • payment_method_v2: Notification when payment method V2 is expiring and/or has activated or expired;
    • Refunds
      • Refund request succeded: Notification for any successful refund transaction event;
      • Refund request failed: Notification for any failed refund transaction event;
  • Cards
    • Cards authentication: Notification for any Cards successful authentication event;
    • Cards tokenization: Notification for any Cards successful tokenization event;
  • Direct Debit
    • direct_debit: Notification for any Direct Debit successful payment event;
    • payment_method: Notification when payment method is expiring and/or has expired;
      • Payment Method is a mandatory step to abstract Debit Card / Bank Account for Direct Debit transactions;
  • ewallet: New eWallet type to receive charge and other eWallet events across eWallets channels from /ewallets/charges API;
  • qr_code:Xendit notifies your system when QR payment has been made or QR refund has been completed. This field is only supported for qr_codes API version 2022-07-31.
  • Fixed Virtual Account
    • fva_status: Notification when Virtual Account in Indonesia has been created or updated successfully;
    • fva_paid: Notification when Virtual Account in Indonesia has been paid successfully;
  • PayLater
    • PayLater Payment Status: Notification when PayLater transaction has been created or updated successfully;
  • Retail Outlet
    • ro_fpc_paid: Notification when Retail Outlet payment code (Alfamart/Indomaret) in Indonesia has been paid successfully;
    • regional_ro_paid: Notification when Over-the-Counter payment code (7 Eleven, Cebuana, ECPay) in Philippines has been paid successfully.

• Money-Out

  • batch_disbursement: Notification when Batch Disbursement on Indonesian accounts have been executed successfully by Xendit.
  • disbursement: Notification when disbursement on Indonesian account has been executed successfully, either withCOMPLETEDorFAILEDstatus;
  • ph_disbursement: Notification when disbursement on the Philippines account has been executed successfully, either withCOMPLETEDorFAILEDstatus;

• xenPlatform

  • Account Created: Notification when sub account of xenPlatform is created;
  • Account Updated: Notification when KYC status of LIVE MANAGED sub account is updated;
  • Account Suspension: Notification when sub account of xenPlatform is suspended;

• Reports

  • Balance and Transaction Report: Your report will be delivered to this URL

You can create a specific Webhook URL for each product. We also provide the option to add a webhook URL in Test/Live Mode.

Does Xendit has example of Webhook URL?

We don't have a sample webhook URL that you can use in Live mode.

But for the purpose of testing, you can use websites that can provide a public host URL like ngrok.io, beeceptor.com, or any webhook site

To read more about how the Xendit webhook URL works, you can refer to this link.