by blokko 1 (0 reviews)

Blokko Payments

Name: Blokko Payments
Author: blokko

Accept stablecoins, crypto and real-time payments in your WooCommerce checkout, and with a payment button on any WordPress page.

Blokko Payments ranks #71,498 among WordPress.org plugins with 1+ active installations, is #7,243 of 14,124 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Oct 9, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.0 Current Version v1.0.0

Updated 4 weeks ago Last Update on 09 Oct, 2026

Refreshed 1 week ago Last Refreshed on

#7,243 of 14,124 in E-commerce Actively maintained

View on WordPress.org

Rank

#71,498

— No change

Active Installs

— No change

KW Avg Position

1 better

Downloads

164

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

58,561

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

Current #71,498

Change

Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

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%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Oct 09, 2026
Requires WP: 6.4+
Tested Up To: 7.1
PHP Version: 8.1 or higher
Author: blokko

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

crypto payment gateway qr code stablecoin woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

MonsterInsights – Google Analytics Dashboard for WordPress (Website Stats Made Easy)

Google for WooCommerce

800K+ installs

#74

WooPayments: Integrated WooCommerce Payments

800K+ installs

#76

WooCommerce PayPal Payments

800K+ installs

#82

WooCommerce Stripe Payment Gateway

700K+ installs

#85

WooCommerce Tax (formerly WooCommerce Shipping & Tax)

500K+ installs

#115

View all Ecommerce plugins

Frequently Asked Questions

Common questions about Blokko Payments

Yes. The plugin uses your Blokko account credentials (Merchant ID, API Key and API Secret). The one

your site or opening a wallet there.

Yes. Payment buttons work on any WordPress site: you insert the "Blokko — Direct charge" block, or the [blokko_pago] shortcode, on one of your pages, with a fixed amount or one your customer types. Neither WooCommerce nor any other commerce plugin is required.

According to Blokko: Brazil, Mexico, Colombia, Chile, Bolivia and Peru, with Venezuela, Canada and the European Union announced as upcoming. The plugin adds no geographic restrictions of its own — actual availability is determined by your Blokko account.

Blokko states that it settles in local fiat currency over existing banking rails. The plugin does not convert currency: it sends the total in your store's currency and requires the invoice Blokko returns to match in amount and currency before opening Blokko's payment page. If your store charges in a currency your Blokko account does not settle, that payment does not complete.

No. Payment does not depend on the buyer seeing the return page: the plugin asks Blokko for the status over a signed request, on a scheduled reconciliation, and also reacts to the events Blokko sends. The confirmation arrives either way.

No, and that is deliberate. The notification arrives signed and only brings a check forward; the state it carries never decides a payment. What marks an order as paid is the signed response of Blokko's status endpoint, queried by the plugin.

Only by code, and deliberately. There is no setting for it: when Blokko confirms a payment for the exact amount and currency the order asked for, that order is marked as paid. To refuse settlement for one site, whoever maintains it adds a filter that returns false — blokko_payments_settle_orders for WooCommerce orders, blokko_direct_charge_settle_charges for direct charges. A store that still has the older "settlement off" choice saved keeps that row where it is, and it decides nothing.

Because the list is defined by your Blokko account, and two filters are applied on top: methods subject to AML (anti-money-laundering) controls are not offered, and those above Blokko's high-value transaction threshold are shown with a warning.

No. For a payment made from one of your pages, the move to "paid" is a single atomic transition on the payment's own record: only the process that actually performs it fires the extension event, and a second attempt on the same payment does nothing and duplicates no events.