Overview

A case may arise when we don't receive our expected response, 200 (OK), from your endpoint consecutively and our auto-disable feature triggers. In turn, your application will be out of sync with our platform.

❗️

Signs That Your Webhook is Disabled

• Pending transactions are not being updated to "paid" or "failed" status.
• WooCommerce, Magento, or Prestashop orders statuses are not updated accordingly.
• Transactions are updated on your PayMongo Dashboard and not on your integration.

Re-enable a Webhook

1. Retrieve the webhook ID of the disabled endpoint by listing all your registered endpoints .
2. Conduct an Enable a Webhook API call and input the webhook ID.
3. Verify the re-enablement was successful by way of the response your application received from us.

Implementation

1.Retrieve the Webhook ID

To re-enable a disabled endpoint, you will need the equivalent webhook ID allocated to it. In order to do this, you may need to list down all the endpoints you registered with our platform if you do not have this information on hand. You can do this by conducting a List all Webhooks API call.

2. Re-enable the Webhook by ID

Once you have retrieved the corresponding webhook ID of the disabled endpoint, you can now re-enable it. Conduct an Enable a Webhook API call and input the webhook ID.

3. Verify the Status of the Endpoint

Verify that the endpoint has been re-enabled by checking the status attribute of the response you received. The value must now be enabled.

Troubleshooting

If you encounter a response with code, resource_processing_state, please send over a 200 (OK) from the indicated endpoint to our servers first and try re-enabling the endpoint again.

HTTP/1.1 400
Content-Type: application/json

{
  statusCode: 400,
  "errors": {
    "code": 'resource_processing_state',
		"detail": 'Webhook with id hook_xxxxx still has processes that are currently in progress.'
  }
}