Brumisphere Checkout Button for HelloAsso
by Brumisphère 1 (0 reviews)

Brumisphere Checkout Button for HelloAsso

Add a HelloAsso checkout button to WordPress with server-side creation, sandbox/production settings, payment logs, and webhooks.

Brumisphere Checkout Button for HelloAsso ranks #71,610 among WordPress.org plugins with 1+ active installations, is #6,488 of 8,848 in the Customization category, a 1/5 rating from 0 reviews, and was last updated Aug 15, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7 (Current: 7.1.4)
v1.0.0 Current Version v1.0.0
Updated 2 months ago Last Update on 15 Aug, 2026
Refreshed 1 week ago Last Refreshed on
#6,488 of 8,848 in Customization
View on WordPress.org
Rank
#71,610
— No change
Active Installs
1+
— No change
KW Avg Position
3
— No change
Downloads
228
+3 today
Support Resolved
0%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 10

Total Progress 10%
0+ 10+
58,673
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 9 more installs to reach 10+

Rank Changes

68,030 69,820 71,610 73,400 75,191 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
52,253 57,741 63,228 68,715 74,203 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #71,610
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 10 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Brumisphere Checkout Button for HelloAsso

It adds a generic HelloAsso checkout button to WordPress and handles server-side checkout creation, payment persistence, and webhook updates.
Yes. You need a HelloAsso organization and API credentials for the environment you want to use.
Yes. Sandbox and production credentials can be configured at the same time. The active environment controls new checkouts only; the Payments screen can show both environments.
Add [helloasso_checkout_button] to a post, page, or compatible editor block.
No. Client secrets, access tokens, webhook signature keys, and Authorization headers are never exposed to visitors. Configured admin secrets are not printed back into password field values; leave the field empty to keep an existing value, enter a new value to replace it, or use the explicit clear checkbox to remove it.
When a Webhook Signature Key is configured for the environment, the plugin validates the x-ha-signature HMAC SHA-256 signature and rejects invalid signatures. Webhook bodies are also limited to 262144 bytes by default before signature validation or JSON parsing.
Use the unsigned webhook fallback only if necessary. It is disabled by default, visibly warned in admin, and only works when the environment key is missing. It cannot bypass an invalid signature when a key is configured.
If the event includes payment_uuid but no local payment row is found yet, the event is stored as pending_payment_match and the endpoint returns HTTP 503 Service Unavailable so delivery can be retried. Once the payment row exists, a later delivery can process the event and mark it processed; later deliveries are then treated as duplicates.
The event is stored as retryable_update_failed without processed_at and the endpoint returns HTTP 503 Service Unavailable. If WordPress reports zero affected payment rows, the plugin accepts that only when rereading the row confirms the expected status is already persisted. Debug logs can report field_mismatch with mismatched_field to identify the field without logging its value. A later delivery of the same event_id can retry the update. Once the update succeeds, the event is marked processed and later deliveries are treated as duplicates.
No. Raw payloads are not stored by default. The webhook event table stores only a minimized, sanitized summary for idempotency and troubleshooting.

Sign In / Register

You need to sign in or register to use this feature.