First stable release. No functional changes since 0.5.0.<\/p>","0.5.0":"
"Pay for order" now pays in a window over your store, payment confirmation stays fast with any number of abandoned carts, WooCommerce's payment settings explain your Blokko connection, and a notice says which credentials are still missing.<\/p>","0.4.0":"
Direct charges now open Blokko's payment page in a window over your page, the same way WooCommerce checkouts do, and a buyer who retries gets the same payment page back.<\/p>","0.3.0":"
Fixes a double charge: a buyer who came back to pay could end up with two payable pages for one order. Payments are now marked as paid automatically, with no switch. A stuck direct charge closes on its own and can be checked against Blokko from Transactions.<\/p>","0.2.2":"
Direct charges always failed. If you use that module, please update.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3737063,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3737063,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3737063,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3737063,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"blokko\/charge":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"blokko\/charge","title":"Blokko \u2014 Direct charge","category":"widgets","icon":"money-alt","description":"Direct-charge form via Blokko (fixed or variable amount), without a shopping cart.","keywords":["blokko","payment","charge","checkout"],"textdomain":"blokko-payments","attributes":{"amountMode":{"type":"string","default":"fixed"},"amount":{"type":"string","default":"0.00"},"minAmount":{"type":"string","default":"0.00"},"maxAmount":{"type":"string","default":"0.00"},"currency":{"type":"string","default":"USD"},"label":{"type":"string","default":""},"description":{"type":"string","default":""},"buttonText":{"type":"string","default":""}},"supports":{"html":false},"editorScript":"blokko-charge-block-editor","render":"file:.\/render.php"}},"tagged_versions":["0.5.0","1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3737063,"resolution":"1","location":"assets","locale":"","width":1440,"height":1000},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3737063,"resolution":"2","location":"assets","locale":"","width":1440,"height":1000},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3737063,"resolution":"3","location":"assets","locale":"","width":1440,"height":1000},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3737063,"resolution":"4","location":"assets","locale":"","width":1440,"height":1000},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3737063,"resolution":"5","location":"assets","locale":"","width":1440,"height":1000}},"screenshots":{"1":"The Blokko Payments settings screen: credentials, environment and the active-environment badge.","2":"The webhook section, with the callback URL visible and copyable and registration against Blokko.","3":"Gateway settings under WooCommerce \u2192 Settings \u2192 Payments.","4":"The \"Blokko \u2014 Direct charge\" block in the WordPress editor, with a fixed or buyer-entered amount.","5":"The \"Payments from your pages\" screen: every payment started from a page, with its own status."}},"plugin_section":[],"plugin_tags":[21057,6593,1373,231844,286],"plugin_category":[45],"plugin_contributors":[285413],"plugin_business_model":[],"class_list":["post-376198","plugin","type-plugin","status-publish","hentry","plugin_tags-crypto","plugin_tags-payment-gateway","plugin_tags-qr-code","plugin_tags-stablecoin","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-blokko","plugin_committers-blokko"],"banners":{"banner":"https:\/\/ps.w.org\/blokko-payments\/assets\/banner-772x250.png?rev=3737063","banner_2x":"https:\/\/ps.w.org\/blokko-payments\/assets\/banner-1544x500.png?rev=3737063","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/blokko-payments\/assets\/icon-128x128.png?rev=3737063","icon_2x":"https:\/\/ps.w.org\/blokko-payments\/assets\/icon-256x256.png?rev=3737063","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/blokko-payments\/assets\/screenshot-1.png?rev=3737063","caption":"The Blokko Payments settings screen: credentials, environment and the active-environment badge."},{"src":"https:\/\/ps.w.org\/blokko-payments\/assets\/screenshot-2.png?rev=3737063","caption":"The webhook section, with the callback URL visible and copyable and registration against Blokko."},{"src":"https:\/\/ps.w.org\/blokko-payments\/assets\/screenshot-3.png?rev=3737063","caption":"Gateway settings under WooCommerce \u2192 Settings \u2192 Payments."},{"src":"https:\/\/ps.w.org\/blokko-payments\/assets\/screenshot-4.png?rev=3737063","caption":"The \"Blokko \u2014 Direct charge\" block in the WordPress editor, with a fixed or buyer-entered amount."},{"src":"https:\/\/ps.w.org\/blokko-payments\/assets\/screenshot-5.png?rev=3737063","caption":"The \"Payments from your pages\" screen: every payment started from a page, with its own status."}],"raw_content":"\n
Blokko Payments connects Blokko's alternative payment methods to your store without changing how\nyou operate today. Blokko sums it up in its own tagline: \"More Ways to Pay\".<\/p>\n\n
According to Blokko, its service lets you accept stablecoins, real-time international payments and\ncrypto through the systems you already use, settling in local fiat currency over existing banking\nrails, with connectivity to payment networks and regulated exchanges handled by Blokko. This plugin\nis the WordPress side of that service.<\/p>\n\n
The buyer needs no account and no wallet on your site: they pick a payment method and pay on a\npayment page hosted by Blokko, and several methods are paid by scanning a QR code. How they get\nthere depends on where the payment started:<\/p>\n\n
Either way, Blokko returns the buyer to your site when they are done.<\/p>\n\n
This is the part worth reading closely, because it defines what the plugin guarantees:<\/p>\n\n
The available methods are not hardcoded in the plugin: they are read from your Blokko account and\ngrouped into real-time payments, stablecoins and exchanges. Two criteria are applied on top of that\nlist:<\/p>\n\n
Blokko states more than 700 wallets (among them Binance, Crypto.com and Strike), more than 200\nalternative payment methods (including USDC, USDT, Bitcoin and international real-time payments)\nand operation in Brazil, Mexico, Colombia, Chile, Bolivia and Peru, with Venezuela, Canada and the\nEuropean Union announced as upcoming. Coverage is defined by Blokko and depends on your account:\nthe plugin imposes no geographic restrictions of its own.<\/p>\n\n
Blokko Payments is a client of Blokko, a payment gateway, and it does not work without it: every\npayment the plugin starts is created, hosted and settled by Blokko's service. This plugin is the\nWordPress side of a service you already have an account with. The service is described at\nhttps:\/\/www.blokko.io\/, and it is governed by its own terms of use and its own privacy policy:<\/p>\n\n
The plugin talks to these Blokko hosts, and to no others. Which pair is used depends on the\nenvironment you select in the plugin's settings:<\/p>\n\n
What follows is what the shipped code does. There is no telemetry, no usage reporting, no license\ncheck and no update check against any server: every call below exists to start a payment or to\nconfirm one.<\/p>\n\n
No buyer data. The buyer pays on the page hosted by Blokko without an account on your site, and the\nplugin never receives or stores their name, email address, postal address, card details or wallet\nkeys \u2014 it does not read any of them, so there is nothing of theirs for it to send. The buyer's own\nbrowser does visit Blokko's payment page, or loads it in the frame of the embedded checkout; that\nrequest is the buyer's browser contacting Blokko, the way any visit to a website is.<\/p>\n\n
Your credentials: the signed calls to Blokko's API carry your Merchant ID and your API Key to\nidentify your account, and each one carries a signature computed on your site with your API Secret.\nThe API Secret is never sent. What stays on your site is what Blokko has no need for: your orders\nand charges, and the credentials you saved.<\/p>\n\n
On a store that can pay with Blokko, the plugin can open the hosted payment page in a window on your\nown checkout page, or on the page that carries a payment button, instead of navigating to it. That window loads the invoice URL Blokko returned for\nthat payment attempt in an iframe, and that URL is served by the payment page host of the\nenvironment your store is bound to: payment-link-sandbox.blokko.dev in sandbox, payment-link.blokko.app\nin production. The plugin accepts that frame's address only when its host is exactly the one\nconfigured for the environment in use \u2014 never a subdomain of it, never a suffix, never a wildcard \u2014\nand it sets no sandbox and no allow attribute on the frame. Nothing about the payment is decided in\nthat frame: the store's own status endpoint decides it, as the Description of this plugin explains.<\/p>\n\n\n
If you are going to take payments at your WooCommerce checkout:<\/p>\n\n
If you are going to put payment buttons on your own pages:<\/p>\n\n
Yes. The plugin uses your Blokko account credentials (Merchant ID, API Key and API Secret). The one\nwho needs no account is the buyer: they pay on the page hosted by Blokko, without registering on\nyour site or opening a wallet there.<\/p><\/dd>\n
Yes. Payment buttons work on any WordPress site: you insert the \"Blokko \u2014 Direct charge\" block, or\nthe [blokko_pago] shortcode, on one of your pages, with a fixed amount or one your customer types.\nNeither WooCommerce nor any other commerce plugin is required.<\/p><\/dd>\n
According to Blokko: Brazil, Mexico, Colombia, Chile, Bolivia and Peru, with Venezuela, Canada and\nthe European Union announced as upcoming. The plugin adds no geographic restrictions of its own \u2014\nactual availability is determined by your Blokko account.<\/p><\/dd>\n
Blokko states that it settles in local fiat currency over existing banking rails. The plugin does\nnot convert currency: it sends the total in your store's currency and requires the invoice Blokko\nreturns to match in amount and currency before opening Blokko's payment page. If your store charges\nin a currency your Blokko account does not settle, that payment does not complete.<\/p><\/dd>\n
No. Payment does not depend on the buyer seeing the return page: the plugin asks Blokko for the\nstatus over a signed request, on a scheduled reconciliation, and also reacts to the events Blokko\nsends. The confirmation arrives either way.<\/p><\/dd>\n
No, and that is deliberate. The notification arrives signed and only brings a check forward; the\nstate it carries never decides a payment. What marks an order as paid is the signed response of\nBlokko's status endpoint, queried by the plugin.<\/p><\/dd>\n
Only by code, and deliberately. There is no setting for it: when Blokko confirms a payment for the\nexact amount and currency the order asked for, that order is marked as paid. To refuse settlement\nfor one site, whoever maintains it adds a filter that returns false \u2014 Because the list is defined by your Blokko account, and two filters are applied on top: methods\nsubject to AML (anti-money-laundering) controls are not offered, and those above Blokko's\nhigh-value transaction threshold are shown with a warning.<\/p><\/dd>\n No. For a payment made from one of your pages, the move to \"paid\" is a single atomic transition on\nthe payment's own record: only the process that actually performs it fires the extension event, and\na second attempt on the same payment does nothing and duplicates no events.<\/p><\/dd>\n No. The buyer picks the method and pays on the page hosted by Blokko; the plugin never receives or\nstores that data. What stays on your site is your Blokko account credentials and the payment\nrecords.<\/p><\/dd>\n Yes. Production is selectable on the settings screen and each environment keeps its own\ncredentials, so a store with production selected and production credentials saved charges for\nreal. Do it deliberately: switching the selector does not move anything else, and the environment\nyou save is the one this store transacts against from then on.<\/p><\/dd>\n Everything the plugin created is removed: its options, the payment records and its scheduled tasks.\nOn a multisite installation, the cleanup applies to the site being uninstalled or to the whole\nnetwork, depending on how it is uninstalled.<\/p><\/dd>\n\n<\/dl>\n\n\n After activating the plugin, a dismissible notice tells you when your store still needs\ncredentials and where to add them \u2014 on the plugin's settings screen, WooCommerce's Payments\nscreen, and the plugins list. It goes away on its own once your credentials are complete.<\/p><\/li>\n If your store stops receiving payment confirmations, the connection details now offer\n\"Reconnect Blokko's notifications\": it tells Blokko to notify this site's address again, and\nsays so before it does. If a reconnect fails, the settings screen keeps saying so until one\nsucceeds.<\/p><\/li>\n<\/ul>\n\n The payment method's default description no longer says the buyer is redirected to Blokko:\nthe Blokko checkout now opens in a window on your own checkout page, and the description\nworks on both paths. A store that saved a description of its own keeps it \u2014 check yours if\nit mentions a redirect.<\/p><\/li>\n Settlement is applied automatically, with no switch to turn on: when Blokko confirms a payment for\nthe exact amount and currency an order asked for, that order is marked as paid. The Settlement\nsection is gone from the settings screen, and refusing settlement for one site is a code-level\ndecision, documented in this readme.<\/p><\/li>\n<\/ul>\n\n Earlier releases are listed in changelog.txt.<\/p>","raw_excerpt":"Accept stablecoins, crypto and real-time payments in your WooCommerce checkout, and with a payment button on any WordPress page.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/376198","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=376198"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/blokko"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=376198"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=376198"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=376198"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=376198"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=376198"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=376198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}blokko_payments_settle_orders<\/code>\nfor WooCommerce orders, blokko_direct_charge_settle_charges<\/code> for direct charges. A store that still\nhas the older \"settlement off\" choice saved keeps that row where it is, and it decides nothing.<\/p><\/dd>\nWhy don't I see every payment method?<\/h3><\/dt>\n
Can the same payment be confirmed twice?<\/h3><\/dt>\n
Does the plugin store card data or wallet keys?<\/h3><\/dt>\n
Can I use it in production today?<\/h3><\/dt>\n
What happens to my data if I uninstall the plugin?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n
0.5.0<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
blokko_payments_settle_orders<\/code>\nor blokko_direct_charge_settle_charges<\/code> filter (see the FAQ).<\/li>\n