Online store plugins
Musqet plugins let you take payments on your own online store. Install a plugin on WooCommerce or Magento 2, enter your Musqet credentials, and your customers can pay at your checkout with a card, Google Pay, Apple Pay or bitcoin. There is nothing to build; the plugin does the payment work.
There is also a bitcoin-only plugin for stores that want to accept bitcoin and nothing else.
On WooCommerce, the plugin can also take subscription payments if you sell subscriptions with WooCommerce Subscriptions. See Taking subscription payments.
Every plugin needs PHP 8.2 or later on the server that runs your store.
Adding Musqet to WooCommerce
Section titled “Adding Musqet to WooCommerce”- Download the latest plugin zip from musqet.com/downloads.
- In your WordPress admin, go to Plugins > Add New Plugin > Upload Plugin, choose the zip and install it, then activate it. It is listed as Musqet Cardstream for WooCommerce (or Musqet Bitcoin for WooCommerce for the bitcoin-only plugin).
- Go to WooCommerce > Settings > Payments and open Musqet to set it up. A Settings link also appears next to the plugin on the Plugins page.
From version 1.7.2 of the Musqet plugin (1.4.3 of the bitcoin-only plugin), WordPress tells you when a new version is out: it appears on the Plugins and Updates screens like any other plugin update, with View details showing what changed, and you can turn on automatic updates for it. Before installing an update, the plugin checks the download against the checksum published on musqet.com/downloads, and refuses it if they don’t match or the download can’t be checked. If you have an earlier version, install the latest zip once by hand and updates arrive this way from then on. If you installed the plugin under a different folder name, updates are not offered; reinstall the latest zip from musqet.com/downloads.
The plugin works with classic WooCommerce checkout, the newer Cart and Checkout blocks, and High-Performance Order Storage. In embedded checkout the card fields reload on their own whenever the checkout refreshes, for example when the customer changes their address or delivery method, so customised and multi-step classic checkouts work too. If a payment is declined, the customer sees the reason at the top of the checkout and can try again with the same or another card.
Adding Musqet to Magento
Section titled “Adding Musqet to Magento”-
Add the Musqet Composer repository to your Magento installation (once), then require the module. Package names are listed on musqet.com/downloads:
Terminal window composer config repositories.musqet composer https://musqet.com/downloads/composer# for the bitcoin-only plugin, require musqet/module-payment-btc insteadcomposer require musqet/module-payment-cardstreamIf you can’t use Composer, download the zip from the same page and copy the module into
app/code/Musqet/instead. -
Enable and install it:
Terminal window # for the bitcoin-only plugin, enable Musqet_MusqetPaymentBtc insteadbin/magento module:enable Musqet_MusqetPaymentCardstreambin/magento setup:upgradebin/magento setup:di:compilebin/magento cache:flush -
Open Stores > Configuration > Sales > Payment Methods and find Musqet Payment (Cardstream gateway) to set it up.
To update a module installed with Composer, run composer update followed by the same
bin/magento commands. Each release on musqet.com/downloads lists
what changed.
If your store installed one of the earlier package names, Composer reports it as abandoned. Switch to the new name once, then update as usual:
# Cardstream modulecomposer remove musqet/musqetpaymentcardstreamcomposer require musqet/module-payment-cardstream
# bitcoin-only modulecomposer remove musqet/musqetpaymentbtccomposer require musqet/module-payment-btcSetting up your gateway
Section titled “Setting up your gateway”In the plugin settings you:
- Enable the payment method so it appears at checkout.
- Set the title your customers see next to the payment option (for example, “Card or bitcoin”).
- Enter your Gateway Merchant ID and Gateway Signature Key from Musqet, so the plugin can take payments on your behalf.
There is no separate test or live switch for cards: card payments are live or test according to the credentials Musqet gave you. Bitcoin has its own Bitcoin Environment setting, covered under Taking bitcoin payments.
You can turn each payment method (card, Google Pay, Apple Pay, bitcoin) on or off individually, so you offer only the ones you want.
Choosing how your checkout appears
Section titled “Choosing how your checkout appears”You can present the payment step in one of two ways, using the Checkout Mode setting:
- Redirect (the default). The customer is sent to a secure Musqet-hosted payment page to pay, then returned to your store. Nothing sensitive touches your site.
- Embedded. The payment fields appear inside your own checkout, so the customer never leaves your store. Card details are entered in secure fields that Musqet hosts inside the page, and Google Pay, Apple Pay and bitcoin appear as options in the same step. In embedded mode you can also set the Payment Option Order; the option at the top opens by default.
Pick whichever suits your store. Embedded gives a seamless checkout; redirect keeps your site out of the payment path entirely, and needs less setup for Google Pay and Apple Pay.
Taking card payments
Section titled “Taking card payments”With card payments enabled, customers pay with Visa, Mastercard and other major cards. In embedded mode the card number, expiry and security code are entered in secure Musqet-hosted fields, so the card details never touch your server. In redirect mode the card is entered on the Musqet payment page.
Protection against card testing
Section titled “Protection against card testing”Card testing is when someone tries many stolen card numbers on a store in quick succession, placing small orders that are mostly declined. It costs you gateway fees and can get your account flagged.
From version 1.8.0 of the Musqet WooCommerce plugin and 2.3.0 of the Musqet Magento module, the plugin watches for this. After 3 unsuccessful card payments within 10 minutes from the same shopper, counted by IP address, customer account and browser session (on Magento, the basket), it pauses card payments for that shopper for 1 hour. While paused, the shopper sees “Too many unsuccessful payment attempts. Please try again later.” and nothing is sent to Musqet. This covers card payments in redirect and embedded checkout, Google Pay, Apple Pay, express checkout and (on Magento) payment links. Subscription renewals and payments you take in your admin are not affected.
It is on by default, including after an upgrade. You can change the number of attempts, the time window
and the length of the pause, or turn it off, in the plugin settings under Card-testing protection.
Each pause is written to the log: in WooCommerce under WooCommerce > Status > Logs
(musqet-cardstream), and in Magento to the system log. The plugin stores only scrambled versions of
the IP address, account and session or basket, never card details, and forgets them when the pause or
the time window ends. On Magento, pauses are kept in the cache, so flushing the cache lifts them.
In redirect checkout the protection decides whether a shopper is sent to the Musqet payment page. A payment page already open in a shopper’s browser before a pause began can still be submitted, so in redirect checkout the pause works alongside the payment page’s own fraud checks rather than replacing them. Embedded checkout, Google Pay, Apple Pay and express checkout are checked on every payment.
On WooCommerce without a persistent object cache (Redis or Memcached), the counts are kept as short-lived WordPress options, which WordPress clears daily; an object cache keeps them out of the database.
Email addresses are not counted, so nobody can pause one of your customers by entering their email address with bad cards. Shoppers buying the same items are counted separately.
If your store is behind Cloudflare, the plugin recognises it and reads each shopper’s own IP address from it, with nothing for you to set up. If it is behind another proxy, CDN or load balancer, every shopper reaches your server from the proxy’s address, so repeated declines from any of them could pause card payments for all of them. List the proxy’s addresses or ranges under Trusted proxies in the Card-testing protection settings, on WooCommerce and on Magento alike. Leave Trusted proxies empty if visitors reach your server directly.
Google Pay and Apple Pay at a glance
Section titled “Google Pay and Apple Pay at a glance”What you need to do depends on your checkout mode:
| Redirect checkout | Embedded checkout | |
|---|---|---|
| Where the buttons appear | On the Musqet payment page | In your own checkout |
| Plugin settings to change | None. The Enable Google Pay and Enable Apple Pay settings do not apply in redirect mode | Turn on Enable Google Pay and Enable Apple Pay |
| Google Pay Merchant ID | Not needed | Needed. See Getting a Google Pay Merchant ID |
| Apple Pay domain registration | Not needed | Ask Musqet to register your store’s domain with Apple Pay |
| Apple certificate or developer account | Not needed | Not needed |
Express checkout is separate from the checkout mode. If you use it, it needs the embedded column’s setup whichever mode you choose.
In redirect mode the Musqet payment page offers Google Pay and Apple Pay when your Musqet account has them turned on. If you do not see them there, ask Musqet to turn them on for your account.
Accepting Google Pay
Section titled “Accepting Google Pay”In embedded checkout:
- Get your Google Pay Merchant ID from Google. If you do not have one yet, follow Getting a Google Pay Merchant ID below.
- In the plugin settings, turn on Enable Google Pay.
- Enter your ID in Google Pay Merchant ID.
A Google Pay button then appears for customers whose browser and device support it (typically Chrome with a card saved to their Google account). Customers who do not have Google Pay simply see the other payment options.
While you are testing, you can enter TEST as the Google Pay Merchant ID. Google Pay then runs in
Google’s test mode and no real card is charged by Google. Replace it with your real ID before you go
live.
In redirect checkout there is nothing to set up in the plugin; see Google Pay and Apple Pay at a glance.
Getting a Google Pay Merchant ID
Section titled “Getting a Google Pay Merchant ID”A Google Pay Merchant ID is an identifier Google gives your business so that Google Pay can run on your website. It is free, it comes from Google rather than from Musqet, and it is different from the Gateway Merchant ID Musqet gives you. You only need one for embedded checkout.
- Go to the Google Pay & Wallet Console and sign in with the Google account you want to manage your business with.
- Choose Merchant as your type of business and complete your Business profile.
- Open the Google Pay API tab, select Get started, and accept the terms.
- Your Merchant ID is shown in the top-right corner of the console. Copy it into the plugin’s Google Pay Merchant ID setting.
- Before Google lets you take real payments, it reviews your website. In the console, go to
Google Pay API > Integrations > Integrate with your website and select Add website:
- Enter your store’s domain (for example,
shop.example.com). - For the integration type, choose Gateway, because Musqet processes the payment for you.
- Upload the screenshots Google asks for, showing the Google Pay button and payment sheet on your
checkout. The
TESTsetting described above lets you show these before you are approved. - Select Save, then Submit for approval.
- Enter your store’s domain (for example,
- When Google approves your website, make sure the plugin has your real Merchant ID (not
TEST). Google Pay is then live.
Google’s own guide, Request production access, describes the review in more detail. If you get stuck, Musqet can help.
Accepting Apple Pay
Section titled “Accepting Apple Pay”In embedded checkout:
- Ask Musqet to register your store’s domain for Apple Pay. Musqet handles Apple Pay on your behalf, so you do not need an Apple developer account, a certificate or an Apple Pay merchant ID of your own.
- Once Musqet confirms the domain is registered, turn on Enable Apple Pay in the plugin settings.
Customers using Safari on an Apple device then see an Apple Pay button and confirm the payment with Face ID, Touch ID or their passcode. Apple Pay does not appear on browsers or devices that do not support it.
In redirect checkout there is nothing to set up in the plugin; see Google Pay and Apple Pay at a glance.
Express checkout
Section titled “Express checkout”Express checkout puts Google Pay and Apple Pay buttons earlier in the journey, so a customer can pay without filling in the checkout form: on the cart page and mini-cart in Magento, and on the cart and checkout pages in WooCommerce. Turn on Enable Express Checkout (Magento) or Express Checkout (WooCommerce), along with Google Pay, Apple Pay or both. The Google Pay and Apple Pay buttons then appear on your cart page (and the mini-cart in Magento) for customers whose device supports them.
Express checkout uses the same Google Pay and Apple Pay settings as embedded checkout, so it needs your Google Pay Merchant ID and, for Apple Pay, your store’s domain registered by Musqet. On Magento it works with either checkout mode. On WooCommerce the Google Pay, Apple Pay and Express Checkout settings only appear while Checkout Mode is set to Embedded, so set up express checkout in embedded mode.
If a card needs 3D Secure authentication, express checkout can’t complete it: on WooCommerce the customer is sent to the standard checkout, and on Magento they’re asked to pay through the standard checkout instead.
Taking bitcoin payments
Section titled “Taking bitcoin payments”Turn on bitcoin and customers can pay with Lightning or on-chain bitcoin. When they choose bitcoin at checkout, they are shown a QR code to scan with their bitcoin wallet. Once the payment confirms, the order is marked paid and the customer returns to your confirmation page; if they cancel, the order is cancelled. Bitcoin payments use your Bitcoin Business ID and Musqet API Key (a separate key Musqet issues alongside your other credentials), which you enter in the plugin settings. Set Bitcoin Environment to Staging while you test and Production when you go live.
Accepting bitcoin only
Section titled “Accepting bitcoin only”If you want to accept bitcoin and nothing else, install the bitcoin-only plugin instead. It needs your Bitcoin Business ID and Musqet API Key, with no card gateway credentials, and it can run alongside the full plugin without conflict. Customers see a single “Pay with Bitcoin” option that opens the same QR code flow.
Taking subscription payments (WooCommerce)
Section titled “Taking subscription payments (WooCommerce)”If you sell subscriptions with WooCommerce Subscriptions, WooCommerce’s own extension (sold separately by WooCommerce), the Musqet WooCommerce plugin takes the payments: the customer’s first payment at checkout, then each renewal automatically on its due date. You need version 1.7.0 or later of the Musqet WooCommerce plugin. It works in both redirect and embedded checkout, and there is nothing extra to set up: once WooCommerce Subscriptions is active, Musqet is offered at checkout for subscription products. Subscriptions are available on WooCommerce only, not Magento.
Before you start selling subscriptions, ask Musqet to confirm that recurring card payments are turned on for your account, because renewals are charged as recurring payments.
Card only
Section titled “Card only”Subscriptions are paid by card. When a customer’s basket contains a subscription, Google Pay, Apple Pay, bitcoin and express checkout are not offered, because only a card can be charged again for renewals. In embedded checkout the customer sees just the card fields; in redirect checkout the Musqet payment page shows only the card option. In embedded checkout, Enable Card must be on for subscriptions to be offered.
Renewals
Section titled “Renewals”Each renewal is charged to the customer’s card automatically, without the customer being there and without 3D Secure. When it succeeds, WooCommerce creates a paid renewal order and the subscription stays Active.
If the bank declines a renewal, the renewal order is marked Failed and the subscription goes On hold. WooCommerce Subscriptions then asks the customer to pay. When they pay, the subscription becomes Active again, and the card they paid with is used for later renewals.
Renewals are run by WordPress’s scheduled tasks. On a store with little traffic, make sure scheduled tasks run on time, for example from a server cron job, or renewals can be late.
Changing the card
Section titled “Changing the card”A customer changes the card their subscription renews on from My Account > Subscriptions: they open the subscription and choose Change payment. They enter the new card, and the bank may ask them to confirm it with 3D Secure. Nothing is charged: the card is only checked. When it is accepted, the customer is returned to their subscription with a confirmation, and the next renewal uses the new card. If the check fails, the customer sees why, and renewals carry on using the old card.
Free trials
Section titled “Free trials”If a subscription costs nothing at checkout, for example during a free trial, the customer’s card is checked but not charged, and the first renewal charges it when the trial ends.
Viewing the stored card reference
Section titled “Viewing the stored card reference”On the subscription’s page in your WordPress admin, the payment details show the Cardstream xref for the next renewal, Musqet’s reference for the card that the next renewal will charge. You do not normally need to change it. WooCommerce will not save the subscription with this field empty.
Testing before you go live
Section titled “Testing before you go live”Ask Musqet for test credentials and enter them while you set up. With test credentials you can
place orders without moving real money, and use the Musqet test cards to see approved, declined and
authentication outcomes. For Google Pay in embedded checkout, use TEST as the Google Pay Merchant ID;
for bitcoin, set Bitcoin Environment to Staging. When you are ready to trade, swap in your live
credentials, your real Google Pay Merchant ID and the Production bitcoin environment.
Refunds
Section titled “Refunds”You refund a store order from your store admin as usual. In WooCommerce, open the order and choose Refund; in Magento, open the order’s invoice and create a credit memo. The refund is sent back through Musqet, and a note is added to the order recording whether it succeeded.
Card payments are settled overnight. In WooCommerce, a refund before then reduces the payment instead, so the customer is only charged what is left, and refunding the whole amount cancels the payment. For a short time while a payment is being settled it cannot be changed; WooCommerce then says so, and you can refund it the next day.
Troubleshooting
Section titled “Troubleshooting”| What you see | What it means | What to do |
|---|---|---|
| A payment link could not be generated | The gateway credentials are wrong | Check your Gateway Merchant ID and Gateway Signature Key, and that you are using the right live or test credentials |
| The card form does not load at the checkout | The embedded card fields could not load | Make sure your checkout is served over HTTPS and check the browser console for errors |
| The card fields disappear after the customer changes their address or delivery method, or a declined customer sees the checkout reload with no message | The store is on a WooCommerce plugin version older than 1.6.3 | Update the Musqet WooCommerce plugin to 1.6.3 or later |
| The Google Pay button does not appear in embedded checkout | Google Pay is unavailable on the device or not configured | Confirm Enable Google Pay is on and your Google Pay Merchant ID is set, and test in Chrome on a device with a card saved to Google Pay |
Google Pay works with TEST but fails with your real Merchant ID | Google has not yet approved your website | Check the status of your website in the Google Pay & Wallet Console and finish the review |
| The Apple Pay button does not appear in embedded checkout | Apple Pay is unavailable on the device, or your domain is not registered | Test in Safari on an Apple device with a card in Wallet, and check with Musqet that your store’s domain is registered for Apple Pay |
| Google Pay or Apple Pay does not appear on the Musqet payment page (redirect checkout) | The wallet is not turned on for your Musqet account | Ask Musqet to turn it on |
| A bitcoin payment does not complete | The bitcoin component could not load or confirm | Confirm your Bitcoin Business ID and Musqet API Key are set, and that browser extensions or security settings are not blocking the payment window |
| A bitcoin payment was received but the order is not marked as paid | The amount or currency of the bitcoin payment did not match the order, for example because the order total was changed after the customer started paying | Check the payment against the order in your Musqet dashboard, and reconcile it by hand. The plugin records the mismatch in its log |
| An order is stuck as pending | The return from the payment page did not reach your store | Make sure the return and callback URLs are not blocked by a firewall or security plugin |
| A card payment was taken but the WooCommerce order is not marked as paid, and the order has a note saying the order total is different | Cardstream reported a charge for a different amount from the order total, or did not say the amount, for example because the order total was changed after the customer paid | Check the payment against the order in your Musqet dashboard using the xref in the note. If the amount is right, mark the order paid by hand; if not, refund the payment and ask the customer to pay again |
| A bitcoin payment on a payment link was received but the order is not marked as paid | On Magento, the payment could not be applied to the order automatically, for example because the link had been cancelled or already paid, or the payment was more than the balance left | Check the order’s comments: the plugin adds a note with the amount and the Musqet checkout reference. Reconcile the payment by hand |
| A Magento order is in Payment Review with a note that the order could not be updated, or that no answer came back | The card details reached Cardstream, but the store could not finish the order, so the payment may have been taken. The plugin holds the order rather than cancelling it or asking the customer to pay again (Cardstream module 2.3.0 or later) | Check the payment in your Musqet dashboard, using the transaction in the note if there is one. If it was taken, invoice and complete the order; if not, cancel the order and ask the customer to pay again |
| Authentication errors | The credentials are wrong or are test credentials on a live store | Make sure you are using the right live or test credentials |
| A customer paying an order from its payment page, or changing their subscription’s card, sees “Your payment details were not received” | The store is on a WooCommerce plugin version older than 1.7.0 | Update the Musqet WooCommerce plugin to 1.7.0 or later |
| Musqet is not offered at checkout for a subscription product | The plugin is older than 1.7.0, or embedded checkout has card payments turned off | Update the plugin to 1.7.0 or later, and in embedded checkout turn on Enable Card |
| A subscription renewal is declined | The customer’s bank declined the charge, or recurring card payments are not turned on for your account | Check the renewal order’s notes for the reason. If every renewal is declined, ask Musqet to check that recurring payments are turned on for your account |
| A subscription renewal is late | WordPress’s scheduled tasks have not run | Make sure scheduled tasks run on time, for example from a server cron job |
| A customer sees “Too many unsuccessful payment attempts. Please try again later.” | Card-testing protection paused card payments after repeated declines from their IP address, customer account or browser session | Ask them to wait for the pause to end (1 hour by default) and check their card details. If customers share an IP address, for example in an office, you can raise the number of attempts allowed under Card-testing protection. If many unrelated customers see it at once and your store is behind a proxy or CDN other than Cloudflare, list it under Trusted proxies (see Protection against card testing) |
See also
Section titled “See also”- Bitcoin payments for how bitcoin settlement works
- Settlements and fees for how you are paid and charged
- Refunds for how a refund is recorded and paid out
- Agentic commerce for letting AI shopping agents buy from your store