Cryptomus

Take cryptocurrency payments on any Blesta invoice through Cryptomus, with the coin, network and settlement currency you choose.

What it does

Crypto customers are easy to lose at checkout. Without a crypto option they either pay by card or go elsewhere, and if you handle coin payments by hand you end up watching a wallet, converting amounts yourself and marking invoices paid after the fact.

This gateway puts Cryptomus alongside your other payment options on every Blesta invoice. Your client picks Cryptomus, sees exactly what is due and how long they have to pay, and completes the payment on Cryptomus's hosted checkout in whichever cryptocurrency suits them. When Cryptomus confirms the payment, Blesta records the transaction and applies it to the right invoices on its own, so nothing is reconciled by hand.

This is an independent gateway built by Blesta Club. It is not the gateway published by Cryptomus themselves, and we cannot offer support for theirs.

Key features

• Crypto checkout for any invoice: Your clients pay any Blesta invoice in the cryptocurrency they prefer, and the money is applied back to the right invoices automatically, including when several invoices are settled in one payment.
• 47 billing currencies: Bill in any of 47 supported currencies, from USD, EUR and GBP to INR, TRY and UAH, and let Cryptomus handle the conversion into crypto at checkout.
• Automatic settlement conversion: Optionally convert every incoming payment into USDT or USDC as it arrives, so you are not left holding whichever coin the customer chose.
• Restrict the blockchain network: Accept payments on a single network only, choosing from Tron, Ethereum, BNB Smart Chain, Polygon or TON, or let the customer pick any network at checkout.
• A payment window you control: Set how long a generated payment link stays payable, anywhere from 5 minutes to 12 hours. The payment panel shows the amount due and a live countdown so the customer knows exactly how long they have.
• Underpayment top-ups: Let a customer who sends slightly too little send the difference instead of losing the payment. An overpayment still settles the invoice in full, with the surplus left in your Cryptomus balance.
• Confirmed before it is recorded: Every payment notification is signature-checked and re-confirmed with Cryptomus before anything is applied, so an invoice is only ever marked paid on a payment Cryptomus itself confirms.
• Built-in demo mode: A demo mode answers from bundled sample data, so you can trial every screen and the whole payment flow before you have a Cryptomus account or API key.

Installing Cryptomus

Before you start

• If you are on the leased (subscription) licence, the Blesta Club Subscription Manager must be installed and your subscription active. The owned and owned-source licences have no such requirement.
• You need a Cryptomus merchant account. You can create one from the Signup link shown next to the gateway in Blesta, or directly at app.cryptomus.com/signup.

1. Upload the files

Upload the extension folder into your Blesta installation so it lands under your Blesta directory at:

components/gateways/nonmerchant/cryptomus/

For example, on a typical install: /var/www/html/blesta/components/gateways/nonmerchant/cryptomus/

2. Install it in Blesta

1. Log in to your Blesta admin area with a staff account that has the Payment Gateways and Install Gateway permissions. You will find these as checkboxes in the Settings group of the Access Control List, on the Edit Group page under Settings > System > Staff > Staff Groups.
2. Go to Settings > Company > Payment Gateways and click the Available tab.
3. Find Cryptomus in the Non-Merchant section of the list and click Install.

Cryptomus now appears on the Installed tab, under Non-Merchant, with Manage and Uninstall links.

3. Configure it

1. On the Installed tab, click Manage next to Cryptomus.
2. Enter your Merchant UUID and your Payment API Key. Both come from your Cryptomus merchant dashboard, under Settings > API. They must belong to the same merchant, because the API key is also what signs the payment notifications Cryptomus sends back to Blesta. Your API key is stored encrypted in Blesta.
3. The remaining settings are all optional and have working defaults. Settlement currency, Restrict network, Network commission, Payment lifetime (seconds) and Allow partial top-up payments are explained in the usage guide, and each one has a ? tooltip on the page.
4. Scroll to Accepted Currencies on the same page and tick the currencies you want to bill in. Only currencies you have configured in Blesta under Settings > Company > Currencies can be enabled here.
5. Click Update Settings. You should see the message "The gateway was successfully updated."

There is no callback or webhook address to paste into your Cryptomus dashboard. The gateway sends its own notification address to Cryptomus with every payment it creates, so this is handled for you. The gateway also registers no cron tasks and creates no database tables.

Trying it out first

Cryptomus has no separate sandbox account. To try the gateway out without moving real money, or to demo it before you have a Cryptomus account at all, tick Mock API in the gateway settings. The gateway then answers from built-in sample responses instead of contacting Cryptomus, and the whole payment flow works end to end. Never leave this enabled on a live install.

You're ready to go - see the usage guide for a walkthrough of day-to-day use.

Updating Cryptomus

Upgrading works just like installing: upload the new files over the old ones, then run the upgrade from the same page you installed it on.

1. Back up your current extension files first - good practice before any upgrade.
2. Upload the new version over the existing folder, replacing the old files.
3. Log in to your Blesta admin area and go to Settings > Company > Payment Gateways, on the Installed tab.
4. Find Cryptomus in the Non-Merchant section and click Upgrade to run the upgrade. That button only appears once Blesta sees uploaded files newer than the installed version, so if you do not see it, check that the upload actually replaced the old files.

Your existing settings are carried over. None of the releases below need you to re-enter your credentials or reconfigure anything to keep working as before.

Version-specific notes

• 2.0.0: Adds five optional payment settings on the gateway's Manage page: settlement currency, network restriction, payment lifetime, partial top-up payments and network commission. Settlement currency, network restriction and network commission are unset by default and change nothing until you set them. The other two do take effect on upgrade: earlier versions sent no lifetime or top-up instruction at all and left both to your Cryptomus account, whereas 2.0.0 always asks for a payment lifetime of 3600 seconds (1 hour) and turns Allow partial top-up payments on, matching Cryptomus's own defaults. Set them on the Manage page if you want something else. This release also replaces the plain payment button your clients saw with a panel showing the amount due and a live expiry countdown, and fixes the callback handling issues listed in the changelog - after upgrading, notifications are credited to the client the payment was raised for.
• 1.1.0: Adds a Mock API setting for testing and demos, and starts logging every Cryptomus call under Tools > Logs > Gateway. It also begins verifying the signature on payment notifications from Cryptomus, so make sure the Payment API Key saved in Blesta belongs to the same merchant as your Merchant UUID. If you are upgrading from 1.0.0, open the gateway settings once after upgrading and click Update Settings to confirm both credentials are stored correctly.

Using Cryptomus

For your staff

The gateway settings page

Go to Settings > Company > Payment Gateways, stay on the Installed tab, and click Manage next to Cryptomus. Every setting has a ? tooltip next to its label if you want the short version on the page itself.

• Merchant UUID and Payment API Key are your Cryptomus credentials. Both are required, and both must belong to the same merchant.
• Settlement currency decides what happens to the coin your customer pays with. Leave it on "No conversion (settle in the coin paid)" to keep whatever they sent, or choose "USDT (Tether)" or "USDC (USD Coin)" to have Cryptomus convert every incoming payment as it arrives.
• Restrict network limits payments to one blockchain. Leave it on "Any network (customer chooses)" to let the customer decide at checkout, or pick "Tron (TRC-20)", "Ethereum (ERC-20)", "BNB Smart Chain (BEP-20)", "Polygon" or "TON".
• Network commission chooses who absorbs the commission Cryptomus charges on each payment: "Merchant pays the commission" or "Customer pays the commission".
• Payment lifetime (seconds) is how long a generated payment link stays payable. It accepts a whole number from 300 to 43200, which is 5 minutes to 12 hours, and defaults to 3600 (1 hour). Enter anything outside that range and the page refuses to save, telling you "Payment lifetime must be a whole number of seconds between 300 and 43200."
• Allow partial top-up payments is on by default. It lets a customer who underpays send the difference rather than losing the payment.
• Mock API switches the gateway to built-in sample responses for testing and demos. Leave it off on a live install.

Below these is Blesta's own Accepted Currencies section, where you tick which of your configured currencies this gateway may be offered for. Click Update Settings to save.

Checking what Cryptomus sent and received

Every call the gateway makes is logged. Go to Tools > Logs and open the Gateway tab. Cryptomus entries are listed by name and date; click one to expand it and you will see the Input and Output rows for that call, each with its data and a success status. This is the first place to look if a payment did not turn up.

Seeing the payment land

Once Cryptomus confirms a payment, the gateway records a transaction against the paying client and applies it to the invoices that payment was raised for. You will see it on the client's profile under their transactions, and the invoice balance updates on its own. No manual reconciliation is needed.

For your clients

Choosing Cryptomus at checkout

Your client opens an invoice in their client area and starts a payment. On the Make Payment page, Cryptomus appears in the Other Payment Options list as a selectable option alongside your other non-merchant gateways. They select it and click Review and Confirm.

The Cryptomus payment panel

Blesta then shows the Cryptomus panel, which tells the client everything they need before they leave your site:

• a short instruction line explaining they can pay with their preferred cryptocurrency
• Amount due, formatted in your billing currency exactly as Blesta formats it elsewhere, for example "$25.50 USD"
• Payment link expires in, a live countdown that ticks down in real time towards the payment lifetime you configured
• a Pay With Cryptomus button

Clicking the button takes them to Cryptomus's hosted checkout, where they choose the cryptocurrency and network they want to pay with and send the payment. Which coins are offered there is governed by your Cryptomus account and by the network restriction you set in Blesta.

Coming back after paying

After paying, the client is returned to your Blesta client area and shown a "Thank You!" page confirming their payment is being processed. The invoice is settled a moment later, when Cryptomus confirms the payment to Blesta directly.

Good to know

• The invoice is settled by Cryptomus's confirmation, not by the client returning to your site. That is deliberate: it means a payment still gets recorded even if the client closes the tab, and it means nothing is recorded on the strength of a browser redirect alone. Expect a short gap between the client seeing the thank-you page and the invoice showing as paid.
• Every notification is verified before it is trusted. A notification that arrives with a body is only accepted if it carries a valid Cryptomus signature; whatever it says, the gateway then asks Cryptomus directly what the payment's status, amount and currency actually are, and records only that. Who the payment gets credited to is taken from the payment Cryptomus holds, not from the notification, so a forged notification cannot move a payment onto another client's account.
• Overpayments settle the invoice in full. The transaction is recorded at the amount you invoiced, and any surplus the payer sent stays in your Cryptomus balance for you to deal with there.
• Refunds are not issued from Blesta. A crypto refund needs a payout to an address the payer gives you, so it is done from your Cryptomus dashboard. Blesta's refund action reports that refunds are unsupported for this gateway.
• Expired payment links. If the countdown runs out before the client pays, the panel shows "Expired". The client simply starts the payment again from the invoice to get a fresh link.
• Mock API is for testing and demos only. With it ticked no payment reaches Cryptomus and no real money moves, so make sure it is off before you take live payments.