Downloads & install guides

WooCommerce

Crypto checkout for WooCommerce stores — classic and block checkout.

Full WooCommerce guide

Requires: WordPress 6.5+, WooCommerce 8.2+, PHP 7.4+

Orders are marked paid only after a signed webhook and a server-side status check.

A reversed payment puts the order back on hold; nothing is refunded automatically.

1. 1Download the ZIP with the button on this card.
2. 2In WordPress go to Plugins → Add New → Upload Plugin, choose the ZIP and click Install Now, then Activate “Stablora for WooCommerce”.
3. 3Set the store currency to USD in WooCommerce → Settings → General.
4. 4Open WooCommerce → Settings → Payments → Stablora and click Connect with Stablora. Approve on Stablora: the API key, webhook secret and webhook URL are set for you and the gateway is enabled.
5. 5Place a small order and pay it to check the flow (or connect a test account first and pay with faucet coins).

Manual setup (instead of Connect)

The full guide is the README.md inside the download.

Gravity Forms

Any Gravity Forms form with a total can take crypto; the entry is marked Paid after a verified payment.

Full Gravity Forms guide

Requires: WordPress 6.5+, Gravity Forms 2.5+, form currency USD, EUR or GBP (one-time payments)

Built on Gravity Forms’ payment add-on framework and tested with stand-ins against a real Stablora (Gravity Forms is commercial); try it on a staging site first.

1. 1Upload the ZIP under Plugins → Add New → Upload Plugin and activate Stablora for Gravity Forms.
2. 2In Stablora create an API key with read + payments and add the webhook endpoint https://your-site.com/?callback=stablora; copy its signing secret.
3. 3In Forms → Settings → Stablora paste the key and the secret.
4. 4In a form open Settings → Stablora → Add New: Transaction Type Products and Services, Payment Amount Form Total. Send confirmations on the Payment Completed notification event.

Settings

The full guide is the README.md inside the download.

Paid Memberships Pro

Sell memberships for crypto; the level activates only after a verified payment.

Full Paid Memberships Pro guide

Requires: WordPress 6.5+, Paid Memberships Pro 3.4+, PHP 7.4+, InnoDB tables

Recurring billing is not automatic yet: each renewal creates a new invoice.

1. 1Download the ZIP with the button on this card and upload it in Plugins → Add New → Upload Plugin. Activate it after Paid Memberships Pro.
2. 2Set PMPro’s currency to USD and give the level a one-time initial payment.
3. 3Select Crypto (Stablora) in PMPro’s payment gateway settings.
4. 4Open Settings → Stablora - Paid Memberships Pro and click Connect with Stablora. Approve on Stablora: the API key, webhook secret and webhook URL are set for you.

Manual setup (instead of Connect)

The full guide is the README.md inside the download.

Easy Digital Downloads

Sell e-books, software and other downloads for crypto.

Full Easy Digital Downloads guide

Requires: WordPress 6.5+, Easy Digital Downloads 3.3+, PHP 7.4+, InnoDB tables

1. 1Download the ZIP with the button on this card and upload it in Plugins → Add New → Upload Plugin. Activate it after EDD.
2. 2Under Downloads → Settings → Payments enable the Crypto (Stablora) gateway and set the currency to USD. Keep EDD Test Mode off for live payments (turn it on only with a test key).
3. 3Open Settings → Stablora - Easy Digital Downloads and click Connect with Stablora. Approve on Stablora: the API key, webhook secret and webhook URL are set for you.

Manual setup (instead of Connect)

The full guide is the README.md inside the download.

PrestaShop

Payment module with “Awaiting Stablora payment” and “Stablora payment reversed” order states.

Full PrestaShop guide

Requires: PrestaShop 8.0 – 8.x, store currency USD

1. 1Download the ZIP with the button on this card.
2. 2In the back office open Modules → Module Manager → Upload a module and drop the ZIP.
3. 3Click Configure, then Connect with Stablora. Approve on Stablora: the API key, webhook secret and webhook URL are set for you and checkout is enabled.

Manual setup (instead of Connect)

The full guide is the README.md inside the download.

OpenCart

Payment extension with per-store settings and dedicated review/reversed statuses.

Full OpenCart guide

Requires: OpenCart 4.x, base and checkout currency USD

1. 1Download stablora.ocmod.zip with the button on this card.
2. 2In the admin open Extensions → Installer, upload the file, then go to Extensions → Extensions → Payments and click Install on Stablora.
3. 3Click Edit, choose the store and click Connect with Stablora. Approve on Stablora: the API key, webhook secret and callback URL are set for you.
4. 4Map the four order statuses (awaiting, paid, review, reversed), enable the extension and save. Create dedicated unpaid statuses for review and reversed.

Manual setup (instead of Connect)

The full guide is the README.md inside the download.

Magento

Magento 2 / Adobe Commerce / Mage-OS payment method; orders are invoiced after a verified payment.

Full Magento guide

Requires: Magento 2.4.x, PHP 7.4+ with curl, order currency USD, EUR or GBP

A reorganized payment puts the order on hold; nothing is refunded automatically.

Checked against Magento’s source code; test on a staging store before going live.

1. 1Unzip into your Magento root (adds app/code/Stablora/Payment), then run bin/magento module:enable Stablora_Payment && bin/magento setup:upgrade && bin/magento setup:di:compile.
2. 2In Stablora create a Payments only API key and add the webhook endpoint https://your-store.com/stablora/webhook; copy its secret.
3. 3In Stores → Configuration → Sales → Payment Methods → Crypto (Stablora) enable it and paste the key and the secret.

Settings

The full guide is the README.md inside the download.

Shopware

Shopware 6.7 payment method; transactions are marked paid after a verified payment.

Full Shopware guide

Requires: Shopware 6.7, PHP 8.2+, order currency USD, EUR or GBP

A reorganized payment moves the transaction to chargeback; nothing is refunded automatically.

Checked against Shopware 6.7’s source code; test on a staging shop before going live.

1. 1In Shopware open Extensions → My extensions → Upload extension, upload the ZIP, then install and activate it.
2. 2In Stablora create a Payments only API key and add the webhook endpoint https://your-shop.com/api/stablora/webhook; copy its secret.
3. 3Open the plugin’s Configure page and paste the key and the secret, then assign Crypto (Stablora) to your sales channel.

Settings

The full guide is the README.md inside the download.

Requires: CS-Cart / Multi-Vendor 4.15+, PHP 7.4+, primary currency USD, EUR or GBP

Tested with stand-ins for CS-Cart’s payment functions (CS-Cart is commercial); test on a staging store first.

1. 1Upload the ZIP contents to your CS-Cart root and install Stablora crypto payments under Add-ons → Manage add-ons.
2. 2In Stablora create a Payments only API key and add the webhook endpoint https://your-store.com/index.php?dispatch=payment_notification.notify&payment=stablora.
3. 3In Administration → Payment methods add a method with the processor Stablora (crypto) and paste the key and the secret.

The full guide is the README.md inside the download.

Drupal Commerce

Off-site payment gateway for Drupal Commerce 2/3; payments are recorded from the verified webhook.

Full Drupal Commerce guide

Requires: Drupal 10/11, Commerce 2.x/3.x, PHP 8.1+, order currency USD, EUR or GBP

Tested with stand-ins for Commerce’s off-site gateway classes; test on a staging site first.

1. 1Unzip into modules/custom/commerce_stablora and enable Commerce Stablora.
2. 2Add a payment gateway with the plugin Stablora (crypto) and paste a Payments only API key.
3. 3In Stablora add the webhook endpoint shown in the gateway form (/payment/notify/<gateway id>) and paste its secret.

The full guide is the README.md inside the download.

nopCommerce

nopCommerce 5.00 redirection payment method; orders are marked paid after a verified payment.

Full nopCommerce guide

Requires: nopCommerce 5.00 (build from source), primary currency USD, EUR or GBP

Source release: written against nopCommerce 5.00 but not yet compiled by us — build and test on staging first.

1. 1Download the source ZIP, copy Nop.Plugin.Payments.Stablora into src/Plugins, add it to the solution and build.
2. 2Install Crypto (Stablora) under Configuration → Local plugins and open Configure.
3. 3In Stablora create a Payments only API key and add the webhook endpoint https://your-store.com/Plugins/Stablora/Webhook; paste the key and the secret.

The full guide is the README.md inside the download.

Medusa

Medusa v2 payment provider; payments are captured by the verified webhook.

Full Medusa guide

Requires: Medusa 2.5+, region currency USD, EUR or GBP

1. 1Download the ZIP, run npm install && npm run build && npm pack, and install the package in your Medusa app.
2. 2Add the provider to the Payment Module in medusa-config.ts with your API key and webhook secret (see the README).
3. 3In Stablora add the webhook endpoint https://your-medusa.com/hooks/payment/stablora_stablora, then enable the provider in your regions.
4. 4In the storefront, redirect the customer to payment_session.data.checkout_url.

The full guide is the README.md inside the download.

Vendure

Vendure 3 payment handler, checkout mutation and verified webhook.

Full Vendure guide

Requires: Vendure 3.x, order currency USD, EUR or GBP

1. 1Download the ZIP, build it (npm install && npm run build) and add StabloraPlugin.init({ shopUrl }) to your Vendure config.
2. 2Create a payment method with the handler Crypto (Stablora) and paste your API key and webhook secret.
3. 3In Stablora add the webhook endpoint https://your-vendure-host/stablora/webhook.
4. 4In the storefront call createStabloraCheckout and redirect the customer to the returned URL.

The full guide is the README.md inside the download.

Shopify

A “Crypto (Stablora)” payment method with a pay link in the order email; orders are marked paid automatically.

Full Shopify guide

Requires: Stablora Commerce Bridge (Node.js 20+) on a server with HTTPS, Shopify Admin API app

A native crypto option inside Shopify checkout needs Shopify’s payments-partner approval; the manual method works without it.

1. 1Download the Commerce Bridge with the button on this card, unzip it on your server, copy .env.example to .env and set PLATFORMS=shopify, your Stablora test key and webhook secret. Start it with npm start.
2. 2In Shopify Settings → Payments add a manual payment method named exactly Crypto (Stablora).
3. 3Create an Admin API app with read_orders and write_orders; put SHOPIFY_SHOP, SHOPIFY_ACCESS_TOKEN and SHOPIFY_WEBHOOK_SECRET in .env.
4. 4Subscribe the orders/create webhook to https://your-bridge.com/shopify/webhooks/orders-create.
5. 5Add the Liquid snippet from shopify/README.md to the order confirmation email so buyers get their pay link.
6. 6Paste the bridge’s Stablora webhook URL (shown on this card) into Stablora Settings → Webhook destination.

The full guide is the README.md inside the download.

Ecwid

An Ecwid payment application: buyers are redirected to Stablora and back to the store.

Full Ecwid guide

Requires: Stablora Commerce Bridge (Node.js 20+) on a public HTTPS URL, Ecwid payment app

1. 1Download the Commerce Bridge with the button on this card, set PLATFORMS=ecwid in .env and start it with npm start.
2. 2Register an Ecwid payment application with add_payment_method, read_orders and update_orders.
3. 3Set the app’s payment URL to https://your-bridge.com/ecwid/payment.
4. 4Put ECWID_STORE_ID, ECWID_CLIENT_SECRET and ECWID_ACCESS_TOKEN in .env.
5. 5Paste the bridge’s Stablora webhook URL (shown on this card) into Stablora Settings → Webhook destination.

The full guide is the README.md inside the download.

BigCommerce

An offline “Crypto (Stablora)” method; the bridge creates the invoice and updates the order.

Full BigCommerce guide

Requires: Stablora Commerce Bridge (Node.js 20+) on a public HTTPS URL, BigCommerce API account

1. 1Download the Commerce Bridge with the button on this card, set PLATFORMS=bigcommerce in .env and start it with npm start.
2. 2Add an offline payment method shown as Crypto (Stablora).
3. 3Create a store API account with Orders modify; set BIGCOMMERCE_STORE_HASH, BIGCOMMERCE_ACCESS_TOKEN and a random BIGCOMMERCE_WEBHOOK_SECRET.
4. 4Register the store/order/created webhook as described in bigcommerce/README.md.
5. 5Paste the bridge’s Stablora webhook URL (shown on this card) into Stablora Settings → Webhook destination.

The full guide is the README.md inside the download.

WHMCS

Let hosting clients pay WHMCS invoices with any coin; invoices are marked paid automatically.

Full WHMCS guide

Requires: WHMCS 8.x, PHP 7.4+ with curl, invoices in USD, EUR or GBP

Invoices are paid only after a signed webhook and a server-side payment lookup; the Stablora payment ID is the transaction ID, so nothing is paid twice.

Underpaid, overpaid, late or reversed payments go to the Gateway Log for your decision.

1. 1Download the ZIP and extract it into your WHMCS root folder (it only adds files under modules/gateways/).
2. 2In Stablora create an API key with Payments only permissions (Developers → API keys).
3. 3In Stablora open Developers → Webhook endpoints, add https://your-whmcs.com/modules/gateways/callback/stablora.php and copy the signing secret.
4. 4In WHMCS open System Settings → Payment Gateways → All Payment Gateways → Crypto (Stablora), paste the key and the secret, and save.

Settings

The full guide is the README.md inside the download.

FOSSBilling

Clients pay FOSSBilling invoices with any coin; the invoice is paid after a verified payment.

Full FOSSBilling guide

Requires: FOSSBilling 0.8+ with MySQL/MariaDB, invoices in USD, EUR or GBP (one-time payments)

FOSSBilling answers webhooks before processing them, so Stablora cannot retry a failed one. The client’s return re-checks the payment, and failed deliveries stay under Invoices → Transactions for Process.

Tested against FOSSBilling stand-ins and a real Stablora; try it on a staging install first.

1. 1Download the ZIP and extract it into your FOSSBilling root (it adds library/Payment/Adapter/Stablora/ and public/gateways/stablora.png).
2. 2In FOSSBilling open System → Payment gateways → New payment gateway, install Stablora and note its id in the URL.
3. 3In Stablora create a Payments only API key and add the webhook endpoint https://your-billing.com/ipn.php?gateway_id=<id>; copy its signing secret.
4. 4Paste the key and the secret in the gateway, tick Enabled and Allow one time payments, and save.

Settings

The full guide is the README.md inside the download.

Requires: Blesta 5.x, PHP 7.4+ with curl, invoices in USD, EUR or GBP

The Stablora payment ID is the Blesta transaction ID; underpaid or late payments are recorded as pending and a reversal voids the transaction.

Written against Blesta’s gateway interface and tested with Blesta stand-ins and a real Stablora, not yet inside a licensed Blesta — try it on staging first.

1. 1Download the ZIP and extract it into your Blesta root (it adds components/gateways/nonmerchant/stablora/).
2. 2In Blesta open Settings → Company → Payment Gateways → Available and install Stablora (crypto).
3. 3In Stablora create a Payments only API key and add the webhook endpoint shown in the gateway settings (https://your-blesta.com/callback/gw/<company id>/stablora/); copy its signing secret.
4. 4Paste the key and the secret in the gateway settings and save.

Settings

The full guide is the README.md inside the download.

Discord

Sell Discord roles for crypto: /buy gives a private pay button; the role is added after a verified payment.

Full Discord guide

Requires: Node.js 22.5+ on your server with an https address, a Discord application with a bot (Manage Roles)

Roles can be permanent or time-limited (renewals extend the period); a chain reversal removes the role.

Tested against a real Stablora with a Discord API stand-in; try it with a qk_test_ key first.

1. 1Create a Discord application and bot, install it in your server with Manage Roles, and move its role above the roles it sells.
2. 2In Stablora create an API key with read + payments and add the webhook endpoint https://your-bot.example.com/stablora/webhook; copy its signing secret.
3. 3Download and unzip, fill in .env and products.json (amount, currency, server id, role id, optional days), then run npm run register and npm start.
4. 4Set the application’s Interactions Endpoint URL to https://your-bot.example.com/discord/interactions.

The full guide is the README.md inside the download.

Telegram

Shop bot for physical goods and real-world services: /shop, delivery address, pay button, paid orders in your admin chat.

Full Telegram guide

Requires: Node.js 22.5+ on your server with an https address, a bot from @BotFather

Telegram requires Telegram Stars for digital goods and services sold inside bots, so this bot only sells physical goods and real-world services. Sell digital products with Stars or on your website.

Only need payment alerts in Telegram? Use Dashboard → Notifications → Telegram instead.

Tested against a real Stablora with a Telegram Bot API stand-in; try it with a qk_test_ key first.

1. 1Create a bot with @BotFather and note your admin chat id (your own chat or a private group).
2. 2In Stablora create an API key with read + payments and add the webhook endpoint https://your-bot.example.com/stablora/webhook; copy its signing secret.
3. 3Download and unzip, fill in .env and products.json (type physical or service, amount, currency), then run npm run setup and npm start.

The full guide is the README.md inside the download.

Moodle

Payment gateway for Moodle: learners pay course fees with any coin; enrolment after a verified payment.

Full Moodle guide

Requires: Moodle 4.1+ (tested on 5.0), payment account in USD, EUR or GBP

Tested inside a real Moodle 5.0 site against a real Stablora (enrolment by the verified webhook, return page, reversal notice to admins).

1. 1In Site administration → Plugins → Install plugins upload the ZIP and finish the upgrade.
2. 2In Stablora create an API key with read + payments and add the webhook endpoint https://your-moodle.com/payment/gateway/stablora/webhook.php; copy its signing secret.
3. 3In Site administration → General → Payments → Payment accounts open your account → Stablora (crypto), paste the key and the secret and enable it.
4. 4Sell a course with Enrolment on payment (cost, currency, payment account).

Settings

The full guide is the README.md inside the download.

Requires: XenForo 2.2 or 2.3, PHP 7.4+ with curl, prices in USD, EUR or GBP

One-time upgrades; each renewal is a new purchase.

Not yet tried on a live XenForo board — test on a staging board with a test key first.

1. 1In XenForo open Admin → Add-ons → Install/upgrade from archive and upload the ZIP.
2. 2In Stablora create an API key with Payments only permissions and add a webhook endpoint for https://your-board.com/payment_callback.php?_xfProvider=stablora; copy its signing secret.
3. 3In XenForo open Setup → Payment profiles → Add payment profile → Stablora (crypto), paste the key and the secret, and save.
4. 4Select the Stablora profile on your User upgrades.

Settings

The full guide is the README.md inside the download.

Requires: Self-hosted pretix 2024.1+ (tested on 2026.8), tickets priced in USD, EUR or GBP

A reversed transfer flags the order for check-in attention instead of cancelling tickets; refunds are sent from your Stablora dashboard.

For self-hosted pretix. pretix.eu (hosted) only runs plugins installed by the pretix team.

Tested inside a real pretix 2026.8 against a real Stablora: ticket bought, coin picked on the Stablora page, signed webhook, order paid.

1. 1On the pretix server run pip install pretix-stablora-1.0.0.zip, then python -m pretix migrate and python -m pretix rebuild, and restart pretix.
2. 2In Stablora create an API key with read + payments (qk_test_… while the event is in test mode).
3. 3In pretix open the event → Settings → Plugins and enable Stablora (crypto), then Settings → Payment → Crypto (Stablora).
4. 4Add a webhook endpoint in Stablora for the URL shown there (https://your-pretix.com/_stablora/webhook/), paste the key and the signing secret, enable and save.

Settings

The full guide is the README.md inside the download.

OBS Studio

Crypto donations for Twitch, YouTube and Kick streamers: a public donate page, on-stream alerts and a goal bar as OBS browser sources.

Full OBS Studio guide

Requires: OBS Studio (or Streamlabs Desktop / any app with a browser source) and a Stablora account — nothing to install

An alert appears only after Stablora confirms the payment; underpaid or reversed donations never alert and leave the goal. Links in messages are removed and you can hide any message.

The overlay URLs are secret: anyone with them can watch your alerts. Rotate links issues new ones.

Donations are normal payments in your balance with the 0.5% processing fee.

1. 1In your dashboard open Donations, pick a handle (your page becomes stablora.xyz/d/<handle>), a title, preset amounts and an optional goal, then Save all settings.
2. 2Customize the alert: text template with {name} {amount} {message}, colors, font size, animation, built-in or your own sound (https link), the coin animation or your own GIF (https link), text-to-speech. The preview updates live.
3. 3In OBS add Sources → + → Browser, paste the Alerts URL (800 × 600) and tick Control audio via OBS; add the Goal URL the same way (800 × 110).
4. 4Click Send test donation — it appears in OBS within a few seconds and never counts toward your totals or goal. Then put the donate link in your stream panels or chat commands.

Requires: A Stablora account, an API key on your server and a webhook endpoint — nothing to install

Nothing in the widget can move money on its own: withdrawals wait for your server, and pending requests expire after 24 hours (cashier.withdrawal_expired). A player can have at most 3 waiting requests.

The session link carries its token after #, so it never reaches server logs; only a hash is stored. With allowed sites set, the cashier refuses to run inside any other site.

Destination addresses are screened against sanctions lists before you are even asked. Deposits and payouts use the normal fees: 0.5% per deposit, network fee plus withdrawal commission per payout.

1. 1In your dashboard open Cashier: add the sites allowed to embed it (e.g. https://casino.example), choose the coins and whether players can request withdrawals, then Open a test cashier to try it.
2. 2When a player clicks Deposit or Withdraw, your server calls POST /api/v1/cashier/sessions with your API key and { "externalId": "<your player id>" }. The response contains a url that works for 30 minutes (5–120 with expiresInMinutes). Never create sessions in the browser.
3. 3On your page load cashier.js and call Stablora.openCashier(url) (modal), Stablora.mountCashier("#cashier", url) (inside your page) or Stablora.popupCashier(url).
4. 4Deposits go to the player's permanent address on each network. Credit the player in your system on the signed deposit.confirmed webhook (customer_id tells you who) — never on events from the browser.
5. 5A withdrawal in the widget only creates a request and sends you cashier.withdrawal_requested. Debit the player, then POST /api/v1/cashier/withdrawals/{id}/confirm (it becomes a normal payout with your limits, holds and approval rules) or /reject with a reason the player sees.

Settings

n8n

Verified n8n node: create crypto checkouts from any workflow and start workflows on verified payments. Available on n8n Cloud.

Full n8n guide

Requires: n8n Cloud, or self-hosted n8n 1.x with verified community nodes enabled; a public HTTPS webhook URL

Verified by n8n and published on n8n Cloud (October 2026).

Every trigger delivery is signature-checked, deduplicated and re-read from the API before your workflow runs.

The Stablora node also works as an AI Agent tool.

1. 1n8n Cloud: on the workflow canvas search for Stablora and add it — nothing to install. Self-hosted: enable Verified Community Nodes in the admin panel (or Settings → Community Nodes → Install n8n-nodes-stablora) and restart n8n.
2. 2Create a Stablora API key with Payments only permissions (Developers → API keys) and add it as Stablora API credentials.
3. 3Add Stablora → Checkout Session → Create to send customers to a checkout where they pick any coin and network.
4. 4Add a Stablora Trigger and activate the workflow: it registers its own signed webhook with Stablora and removes it when you deactivate the workflow.

Settings

The full guide is the README.md inside the download.

Zapier

Connect crypto payments to 7,000+ apps: create checkouts, start Zaps on verified payments.

Full Zapier guide

Requires: A Zapier account

Turning a Zap on registers its own signed webhook; turning it off removes it.

Every trigger delivery is signature-checked and the payment re-read from Stablora.

1. 1The Stablora app is not listed in Zapier’s directory yet. Until it is, it can only be used through a private invite link from the Stablora team.
2. 2In a Zap choose Stablora and connect it with a Stablora API key that has Payments only permissions.
3. 3Use the Payment Completed trigger (instant) or the Create Checkout action.

The full guide is the README.md inside the download.

Make

Watch payments and create checkouts in Make scenarios.

Full Make guide

Requires: A Make account

Make cannot verify webhook signatures, so the trigger re-reads every payment from Stablora and outputs only that data. Deduplicate on the payment ID in your scenario.

1. 1The Stablora app is not published in Make yet. Until it is, it can only be used through an invite link from the Stablora team.
2. 2Add a Stablora module and create a connection with a Payments only API key.
3. 3Start scenarios with Watch Payments or create links with Create a Checkout.

The full guide is the README.md inside the download.

Activepieces

Open-source automation: checkouts, payment links, wallets and a verified payment trigger.

Full Activepieces guide

Requires: Self-hosted Activepieces 0.30+ (Cloud after the piece is released upstream)

1. 1Download the ZIP, run npm install && npm run build && npm pack, and upload the package under Platform admin → Pieces → Install piece.
2. 2Create a Stablora connection with a Payments only API key.
3. 3Use the Payment Event trigger or the Create Checkout action in a flow.

The full guide is the README.md inside the download.

Odoo

Payment provider for Odoo eCommerce, portal invoices and payment links; the order is confirmed after a verified payment.

Full Odoo guide

Requires: Odoo 18.0 (Community or Enterprise), orders in USD, EUR or GBP (one-time payments)

Underpayments, a second coin and chain reversals are written to the transaction and to the order’s chatter for you to decide; nothing is refunded from Odoo.

Tested inside a real Odoo 18 shop against a real Stablora; not yet listed on the Odoo Apps store.

1. 1Download the ZIP and extract it into a folder on your Odoo addons_path (you get payment_stablora/), then restart Odoo.
2. 2In Odoo open Apps → Update Apps List and activate Payment Provider: Stablora (crypto).
3. 3In Stablora create an API key with read + payments and add the webhook endpoint https://your-odoo.com/payment/stablora/webhook; copy its signing secret.
4. 4In Configuration → Payment Providers → Stablora paste the key and the secret, choose Test Mode (qk_test_) or Enabled (qk_live_) and Publish.

Settings

The full guide is the README.md inside the download.

Requires: A Bubble app (webhook workflow needs a paid Bubble plan; the return-page check works on every plan)

Bubble hands workflows a parsed webhook body, so the plugin never trusts it: every check re-reads the payment with your API key.

Not yet published on the Bubble marketplace.

1. 1The plugin is not on the Bubble marketplace yet. Download the ZIP and create it as a private plugin in Bubble’s plugin editor (the README walks through it in about 10 minutes), or use the API Connector recipe in the README.
2. 2Fill in the plugin keys: a Payments only Stablora API key (start with qk_test_…) and {BASE}/api/v1.
3. 3Pay button: Stablora - Create checkout (reference = your order id) → save session_id → open checkout_url.
4. 4Return page: Stablora - Check checkout; mark the order paid only when paid is yes. Optional backend workflow for webhooks: Stablora - Get verified payment.

Settings

The full guide is the README.md inside the download.

Node.js SDK

Typed client for every endpoint, automatic retries, pagination and webhook verification.

Full Node.js SDK guide

Requires: Node.js 20+, zero dependencies

1. 1Run npm install @stablora/node in your project (source: github.com/baydd/stablora-node).
2. 2Create the client with your secret key and start with stablora.payments.create(...). See the API reference.

The full guide is the README.md inside the download.

PHP SDK

One dependency-free file: checkouts, payments, wallets, payouts and webhook verification.

Full PHP SDK guide

Requires: PHP 7.4+ with curl and json

1. 1Download and unzip, then require 'stablora-php/src/Stablora.php'; (or add it to Composer).
2. 2Create new Stablora\Client('qk_live_…'), call createCheckoutSession([...]) and verify webhooks with Stablora\Webhook::verify(...). See the API reference.

The full guide is the README.md inside the download.

Python SDK

Standard-library only: checkouts, payments, wallets, payouts, webhook verification and a ready-made order flow.

Full Python SDK guide

Requires: Python 3.8+, no dependencies

1. 1Download and unzip, then pip install ./stablora-python (or copy src/stablora/__init__.py into your project as stablora.py).
2. 2Create stablora.Client('qk_live_…'), call create_checkout_session(reference=…, amount=…) and verify webhooks with stablora.Webhook.verify(...). See the API reference.

The full guide is the README.md inside the download.

MCP server

Let Claude and other AI agents create invoices and check payments — never send funds.

Full MCP server guide

Requires: Node.js 20+, an MCP client (Claude Code, Claude Desktop…)

1. 1Download and unzip.
2. 2Add it to your client, e.g. claude mcp add stablora --env STABLORA_API_KEY=qk_test_... -- node ./stablora-mcp/bin/stablora-mcp.js. Details in the API reference.

The full guide is the README.md inside the download.