No Crypto Payment Plugin for Your Platform? 3 Real Options

If you run Magento, Wix, or Squarespace and you have been searching for a crypto payment extension, the honest answer is that Aurpay does not have a native integration for any of those three. Neither do most of the gateways whose marketing pages imply otherwise. That is worth saying plainly before anything else, because the wasted week usually comes from believing a plugin exists and only discovering it does not after you have already committed to a checkout redesign.

You have three routes, and your platform decides which applies. Either it has a native integration and you install it, or it does not and you embed a payment button or link beside your existing checkout, or it is extensible enough that you build the integration yourself against a REST API. Those routes differ enormously in one respect above all: whether the crypto payment ever becomes a real order inside your platform.

One disclosure before the table, since it changes how you should read the rest: we build one of these gateways. That gives us a specific view into how the integrations work, and an obvious interest in you picking ours. Where the honest answer is “your platform will never do this properly, change platforms or change gateways,” we have said so.

The platform triage table

Find your platform. The column that matters most is the last one: whether a crypto payment produces a real order record in your platform, with the inventory decrement, order status, and fulfillment trigger that implies.

Platform	Native Aurpay integration	Your actual path	Becomes a real platform order?
WooCommerce	Yes (official WordPress.org plugin)	Install the plugin	Yes
Shopify	Yes, via a Custom App you create in Shopify Admin	Develop Apps in Admin, then connect	Yes
BigCommerce	Yes	Install the integration	Yes
Ecwid	Yes	Install the integration	Yes
PrestaShop	Yes (module)	Install the module	Yes
OpenCart	Yes (extension)	Install the extension	Yes
Paid Memberships Pro	Yes (WordPress add-on)	Install the add-on	Yes
Easy Digital Downloads	Yes (WordPress add-on)	Install the add-on	Yes
Wix	No	Payment Button snippet or payment link	No, it runs parallel to Wix checkout
Squarespace	No	Payment Button snippet (plan-gated) or payment link	No, it runs parallel to Squarespace checkout
Webflow, Blogger, Google Sites, Weebly, GoDaddy	No	Payment Button snippet or payment link	No
YouTube, Twitch, link-in-bio pages	No (no checkout to integrate with)	Payment link in description or panel	Not applicable
Magento / Adobe Commerce	No	Build a payment module against the REST API	Yes, if you build it that way
Shopware, Drupal Commerce, Zen Cart, custom or headless storefronts	No	Build against the REST API	Yes, if you build it that way

The eight platforms in the first group are the whole native list. If yours is not there, skip to the tier that applies rather than hunting for an integration that does not exist.

Tier 1: native integration, and what “native” actually buys you

A native ecommerce cryptocurrency payment plugin does one thing no embed can do: it participates in your platform’s order lifecycle. When a customer picks crypto at checkout, the plugin requests a payment address from the gateway, holds the order pending, and flips that same order to paid once the chain confirms. Inventory decrements, the confirmation email fires, and your fulfillment queue sees it like any card order. That is why the tier matters more than the fee: a 0.8% flat rate on a payment that never becomes an order still costs you the labour of reconciling it by hand.

Two platform-specific notes before you start. Shopify is a native integration but not a public app: you create a Custom App inside your own Shopify Admin under Develop Apps rather than installing something from the Shopify App Store, and we wrote up the full Shopify Custom App setup path separately because the first screen trips people up. WooCommerce is the one platform where the plugin is genuinely a plugin, listed on WordPress.org, which is why WooCommerce guides dominate this search and why platform coverage is the thing most of them never address. If you are choosing among the eight, our breakdown of crypto payment plugin options by platform covers each one.

Tier 2: Wix, Squarespace, and everything else you can paste HTML into

This is where most people searching for a bitcoin payment extension for ecommerce actually land, and where the marketing gets dishonest fastest.

Neither Wix nor Squarespace lets a merchant install an arbitrary payment gateway. Squarespace connects to Squarespace Payments, Stripe, PayPal, and Square and nothing else — there is no third-party gateway slot to fill. Wix operates a curated roster of payment providers it has onboarded per country, and a provider either appears in your country’s list or it is unavailable to you. Wix does list crypto-capable providers in some markets. Aurpay is not one of them. If native Wix checkout integration is your hard requirement, you are choosing a different gateway. Start from our crypto payment gateway comparison and cross-reference it against your country’s Wix roster. (Both platform pages checked 2026-09-07.)

What you can do on both platforms is put an Aurpay Payment Button, or a plain hosted payment link, on the page, next to or instead of the platform’s own checkout. The button comes in Quick-Pay mode for a fixed price and Donations mode for buyer-chosen amounts, and it accepts BTC, Bitcoin Lightning, ETH, USDT on ERC-20 and TRC-20, USDC on ERC-20 and TRC-20, and DAI on ERC-20, at the same 0.8% per transaction, settling straight to your own wallet with no contracts or banking details required.

What the Payment Button does not do

This is the part competitor pages leave out, and it is the part that determines whether this route works for your business. A Payment Button is a payment mechanism sitting beside your store, not inside it. Specifically:

• It does not take over the platform’s checkout. The customer leaves your Wix or Squarespace cart flow and completes a separate payment. There is no unified basket.
• No order record is created in your platform. Squarespace and Wix never learn the payment happened. Nothing appears in your orders list.
• Inventory does not decrement. If you sell a limited-stock item this way, you are tracking stock manually or overselling.
• Order status does not sync. Paid, shipped, and refunded all have to be maintained by you in whatever system you actually use.
• Discount codes, tax rules, and shipping calculation do not apply. Anything your platform computes at checkout is bypassed, so the button amount has to already include it.
• Refunds are manual. On-chain payments are final; you send funds back yourself, which also means the button is a poor fit where returns are routine.

None of that makes the button useless. It makes it right for a specific shape of business: single products, digital goods, services, deposits, tips, and donations, where order volume is low enough that manual reconciliation is trivial. It is the wrong tool for a 200-SKU catalogue with variable shipping.

Two platform gotchas we verified

Squarespace gates the code block by plan. On every plan, a code block accepts plain text, HTML, Markdown, and CSS inside style tags. Adding JavaScript or iframes to a code block requires the Core, Plus, Advanced, Business, Commerce Basic, or Commerce Advanced plans (checked 2026-09-07). If you are on Personal, a snippet that needs JavaScript will not run. That is not a reason to upgrade your plan. It is a reason to use a plain hosted payment link instead, which is just an anchor tag and works on every plan.

Wix embeds are sandboxed. The Wix HTML element renders your snippet inside an iframe that, per Wix’s own developer documentation, has no direct access to the rest of the page. Practically: the button cannot read a Wix cart total, cannot pull the customer’s email from a Wix form, and cannot post back into Wix state. Your embedded code must also be served over HTTPS or Wix will not display it on the live site. Anyone promising you a button that “syncs with your Wix cart” is describing something the platform does not permit.

The underrated option on both platforms is the link, not the snippet. A hosted checkout page produces a URL and a QR code you can paste anywhere: an email, an invoice, a text message, a button on a plan that blocks code. It sidesteps every embed restriction above because there is nothing to embed. We covered the mechanics in our guide to no-code hosted crypto checkout, and the button-specific setup in adding crypto payment buttons to any website.

Since nothing syncs, decide the reconciliation process before you go live rather than after your first disputed order. The minimum that works: give every button a distinct reference so you can tell which product was bought, record each confirmed payment against your own order number the day it lands, and keep the transaction hash with the order. It is public, permanent, and better dispute evidence than a card receipt.

Tier 3: Magento and anything else you can build against

Magento (Adobe Commerce and Magento Open Source) is a different case. There is still no native Aurpay integration, but unlike the site builders, Magento is fully extensible: payment methods are ordinary PHP modules. Adobe distributes even its own payment integrations this way, and several were unbundled from the core release and moved to Commerce Marketplace from version 2.4.4 onward (checked 2026-09-07). So a crypto payment extension for Magento is something that can exist; it just has to be written.

The gateway side is a REST API covering payins, payouts, orders, and invoices, with a separate developer environment that transacts on testnet so you can exercise the whole flow before touching real funds. The integration itself has two shapes, and picking the right one is most of the decision.

Approach	What you build	Customer experience	Use when
Redirect	Create the order server-side, get back a payment URL, send the customer to it	Leaves your site for a hosted page, returns after paying	You want it working quickly and can accept an off-site step
Embedded	Create the order and receive the payment details directly, render them in your own checkout	Stays on your checkout throughout	Brand consistency matters, or you have a headless front end

The redirect shape is the smaller half of the job by a wide margin. That is engineering judgment rather than a benchmarked figure, but the gap is not marginal. You still need a payment method module so Magento renders the option at checkout; you are not rebuilding the payment UI or handling per-coin display logic.

The callback detail that catches people

This is the piece worth reading twice, because it differs from what most gateway integrations condition you to expect. Aurpay’s order callback arrives as an HTTP GET to the URL you registered, and it carries no request body. There are two hooks: a callback for successful payment, and a separate timeout callback for orders that expire unpaid. Your endpoint should answer 200. Signature verification is available and configured in the dashboard.

The consequence: the callback is a notification that something changed, not a payload describing what changed. Your handler should treat it as a trigger to query the order status yourself and act on the authoritative answer, never as a source of truth about the amount. That is stricter than the usual “verify the signature and trust the body” pattern, and it is the safer discipline anyway.

Two more things to get right while you are in there. Key your idempotency on your own order identifier rather than on the callback, because a duplicate notification must not produce a duplicate fulfillment. And handle the timeout callback as a real state, not an error. An expired unpaid order needs its inventory reservation released, and if you only implement the success path, those reservations leak. Our crypto payment API integration guide works through the request and response flow in detail; the Aurpay API reference is the authoritative source for the current field names.

Choosing between the three

The decision is mostly forced by your platform, but where you have a real choice, these are the rules we would apply:

• Your platform is on the native list. Install the integration. There is no scenario where an embed beats it.
• Not on the list, and you sell under roughly a dozen crypto orders a month. Use a button or a payment link. Manual reconciliation at that volume costs less than any build.
• Not on the list, higher volume, platform is extensible (Magento, Shopware, headless). Build the redirect flow. You get real order records and it is the smaller build.
• Not on the list, higher volume, platform is closed (Wix, Squarespace). There is no good answer inside the platform: accept manual reconciliation permanently, or migrate the storefront. If crypto will be a meaningful share of revenue, migrating is usually cheaper than a workaround that quietly costs you an hour a day.
• You need native checkout integration on Wix or Squarespace specifically. Pick a gateway that is already on their provider roster. It will not be us, and that is the correct answer for you.

One thing to avoid at every tier: posting a wallet address on the page and asking customers to send funds and email you proof. No amount matching, no expiry, no exchange-rate lock, no automated confirmation. Every one of those gaps becomes a support ticket. A hosted link costs nothing extra and removes all four.

Where this leaves you

The gateway you can install is worth more than the gateway with the better rate sheet, right up until your platform makes installation impossible. Then the question changes from “which gateway” to “which of these three integration shapes can my business actually operate.” Answer that first.

Aurpay is a non-custodial gateway: payments settle directly into a wallet you control at a flat 0.8% per transaction, whether they arrive through a native plugin, an embedded button, a hosted link, or your own API integration. The custody model does not change with the tier, only how much order plumbing comes with it. If you are still weighing providers, our crypto payment gateway comparison puts the major options side by side on custody, fees, and platform coverage, with each figure checked against the provider’s own pricing page, including who holds your funds among the processors on Wix’s and Squarespace’s rosters.