Webhooks notify your endpoint when supported events occur in TabaPay. Use webhooks to update your application when ACH payments, verifications, or chargebacks change without repeatedly retrieving the resource.
Create a webhook subscription for each eventType your integration needs to receive.
Webhook Event Types
TabaPay supports webhook events for:
- ACH payments
- Verification Status
- Chargebacks Events
| Event Type | Description |
|---|---|
ACH.Sent | An ACH payment was sent for ACH processing. |
ACH.Return | An ACH payment was returned by the receiving financial institution. |
ACH.NOC | A Notification of Change (NOC) was received for an ACH payment. |
ACH.Rejected | An ACH payment was rejected before it was sent for ACH processing. |
Verification.Created | A verification was created with Create Verification API |
Verification.Pending | Verification is pending and has not reached a final result. |
Verification.Completed | Verification completed successfully. |
Verification.Failed | Verification has failed. User remains unverified. |
Verification.Error | An error occurred during the verification. User remains unverified. |
Chargeback.Open | A chargeback case was opened. |
Chargeback.DocumentationReceived | Chargeback evidence was received from the merchant. |
Chargeback.Representment | Merchant evidence was submitted to the network for issuer review. |
Chargeback.Closed | A chargeback case was closed. |
Set Up Webhooks
Use the Webhook APIs to create and manage subscriptions:
For an overview of Webhook APIs, refer to Webhook <span class="badge>API
Verify Webhook Deliveries
Webhook signing can be used to verify that webhook requests were sent by TabaPay. Signed deliveries include the X-HMAC-Signature header and an Idempotency-Key that remains stable across retries.
For more info on verifying webhook signatures, refer to Verifying Webhook Signatures.