Request Header
Verifying the origin of webhooks from our API guarantees the authenticity of a webhook notification. Each request sent to your webhook URL will carry a header namedX-Caller-Auth, containing the SHA256 encryption of your API key. It
is of utmost importance to authenticate this key in order to ascertain that the webhook request indeed originates from
our API.
Security
Your webhook URL in the our sandbox and production environment must be HTTPS or the webhook event will not be sent.Response & Retry Logic
You must respond with HTTP status code 200 OK to confirm that you have received and successfully processed the webhook request.Available Webhook Events
Bank Account Removed Event
Our API offers a webhook that executes each time when a bank account has been deleted. The webhook payload structure is:Bank Link Failed Event
Our ACH API offers a webhook that executes each time when a bank account has not linked due to some reason. The webhook payload structure is:Bank Linked Successfully Event
Our ACH API offers a webhook that executes each time when a bank account has been linked successfully. The webhook payload structure is:Batch Payout Event
Our ACH API offers a webhook that execute each time when batch payout has been initiated to processor. The webhook payload structure is:Batch Refund Event
Our ACH API offers a webhook that execute each time when Debit ACH has been created from processor’s bank account. Note:- This webhook will be initiated only when processor has been configured to batch payouts.
- Our ACH API will create a debit ACH from the processor for all refund requests of the day.
Business Created Event
Our ACH API offers a webhook that executes each time when a business account has created. The webhook payload structure is:Business Updated Event
Our ACH API offers a webhook that execute each time when a business has updated The webhook payload structure is:Clawback Completed Event
Our ACH API offers a webhook that execute each time when payout return has been completed.- Please note that this event indicates that the payout return has been sent on our end. It does not indicate that the money has been successfully delivered by the bank yet.
Clawback Failed Event
Our ACH API offers a webhook that execute each time when payout return has been failed. The webhook payload structure is:Clawback Started Event
Our ACH API offers a webhook that execute each time when payout return has been initiated. A payout return occurs when a transaction fails (with a specific reason code) after the payout has already been initiated. The webhook payload structure is:Payout Completed Event
Our ACH API offers a webhook that executes each time the payout (transfer money to payee) has been completed.- Please note that this event indicates that the payout has been sent on our end. It does not indicate that the money has been successfully delivered by the bank yet.
Payout Failed Event
Our ACH API offers a webhook that executes each time the payout (transfer money to payee) has failed due to some reason. The webhook payload structure is:Refund Capture Completed Event
Our ACH API offers a webhook that execute each time when Debit ACH has been completed from payee’s or processor’s bank account. The webhook payload structure is:Refund Capture Failed Event
Our ACH API offers a webhook that execute each time when Debit ACH has been failed from payee’s or processor’s bank account. The webhook payload structure is:Refund Capture Started Event
Our ACH API offers a webhook that execute each time when refund request has been started and Debit ACH has been initiated from payee’s or processor’s bank account. Note:- For individual payouts, Our ACH API will create a debit ACH from the payee or processor for each refund request.
- For batch payouts, Our ACH API will create a debit ACH from the processor for all refund requests of the day.
- In both cases, this webhook will be initiated for each refund request.
Refund Payout Completed Event
Our ACH API offers a webhook that execute each time when refund has been completed and fund has been sent to payer’s bank account. The webhook payload structure is:Refund Payout Failed Event
Our ACH API offers a webhook that execute each time when Credit ACH has been failed to payer’s bank account. The webhook payload structure is:Refund Payout Pending Event
Our ACH API offers a webhook that execute each time when Credit ACH has been initiated to payer’s bank account. The webhook payload structure is:Refund Pending Event
Our ACH API offers a webhook that execute each time when refund request has been created. The webhook payload structure is:Reverse Payout Completed Event
Our ACH API offers a webhook that execute each time when reverse payout has been completed. The webhook payload structure is:Reverse Payout Failed Event
Our ACH API offers a webhook that execute each time when reverse payout has been failed due to some reason. The webhook payload structure is:Reverse Payout Started Event
Our ACH API offers a webhook that execute each time when reverse payout has been processed. The webhook payload structure is:Transaction Capture Started Event
Our ACH API offers a webhook that executes each time when ACH has been processed The webhook payload structure is:Transaction Canceled Event
Our ACH API offers a webhook that executes each time when transaction has been canceled. The webhook payload structure is:Transaction Completed Event
Our ACH API offers a webhook that executes each time when transaction has been completed. The webhook payload structure is:Transaction Failed Event
Our ACH API offers a webhook that executes each time the transaction has failed due to some reason. The webhook payload structure is:ach_return_code along with the corresponding R code in ‘ach_return_code’. For a list of ACH return
codes see our Return Codes documentation.
