How to make all plugin features work by setting up webhooks.
There is a one-way communication between WP Full Stripe and Stripe by default; the plugin sends requests to Stripe via the Stripe API.
Stripe webhooks make it possible to send messages in the other direction, so Stripe can notify the plugin when certain events occur.
WP Full Stripe is functional without webhooks, but webhooks are required to use the plugin to its full potential.
For working properly, the following features require webhooks:
Write down the Stripe webhook URL of the plugin on the “Full Stripe / Settings / Stripe account” page in WP admin.
Go to the Developers / Webhooks page on the Stripe dashboard.
Switch to live mode
When the events are added, press the “Add endpoint” button as well.
Make sure that only one webhook endpoint is set up per API mode (one for test, and one for live).
Switch to live mode by pressing the “Test mode” toggle in the top-tight corner:
Repeat steps 2), 3), and 4) in live mode.
You can test your webhook setup by sending a test webhook event to the plugin.
Follow these steps:
Lets see the test procedure with screenshots:
The final step to check the webhook endpoint status in the plugin on the “Full Stripe / Settings / Stripe account” page in WP admin.
If the webhook endpoint is configured properly, then you’ll see a green status indicator, and the time the last event was sent:
If the webhook endpoint is not configured properly, then you’ll see a grey status indicator:
You’ll find the most common errors with possible solutions in this section.
You are sending a test webhook from the Stripe dashboard.
Stripe says that “Test webhook sent successfully” but the response is not empty.
This usually means that there is a security plugin blocking the /wp-admin/admin-post.php URL.
Enable this URL for external callers, or add an exception so that the securiy plugin doesn’t block this URL.
This happens when are trying to send a webhook to local test environment, or there are issues with the DNS entries of <your_host>.
Verify your DNS settings, or use a globally accessible domain name for your test site - consider DynDNS or similar.
It means that the webhook endpoint rejected the webhook request.
It usually happens when the authentication token is not valid anymore. Compare the webhook URL in Stripe and in the plugin.
It means the webhook URL doesn’t exist.
Maybe a few characters of the URL were left off, consider copying and pasting the webhook URL to Stripe again.
Our support team is happy to help you.Contact support
Feature requests are always welcome!
We consider each feature request carefully, and examine how it fits the roadmap for the plugin.