CryptoProcessing Review: Fees, Checkout and Account Limits
CryptoProcessing offers a merchant checkout, conversion and payouts, but whether you can use it comes first. Its Estonian company isn't taking new clients or expanding existing services while its authorisation application is pending, and its Lithuanian company has suspended all crypto services, including transactions. We wouldn't build a new checkout around an approval you're only assuming. If you already have an eligible account, ask about the full price, whether your customers' wallets work, how refunds run and how you get usable money out. The advertised 1.5% ceiling answers none of those.

Useful payment tools, but a big availability problem. Don't commit to a new integration while the relevant company can't onboard you. If you're already a merchant, get your contract, the full charges, the withdrawal conditions and the support terms clear before you route more revenue through it.
- Existing, eligible merchants reviewing the checkout and balances they already use
- Businesses whose approved payment methods and bank payouts match their customers and bills
- New clients of the paused Estonian or suspended Lithuanian company
- Merchants needing an unconditional USD or GBP bank payout
- Businesses assuming every advertised feature or price is available to their account
These figures use 1.5%, the advertised ceiling, as a comparison number and leave out costs nobody has quoted; the fee section below lists them. The euro and asset counts come from the documentation and depend on your approval. The rating is an old, small snapshot, so don't lean on it.
On 14 October 2026 we read the provider's legal, product, operational and software pages and the alternatives' own documents, all listed below. For the company's own account of its 2023 theft and the FBI attribution, we rely on what earlier reviewers read, because our later attempts to open them failed. We haven't opened an account, installed a plugin, sent a payment, measured support or confirmed a merchant agreement.
Can you open a CryptoProcessing merchant account?
Don't assume you can. The Estonian company, Dream Finance OÜ, has paused new clients, accounts and agreements, and the Lithuanian one has suspended all crypto services, including transactions. OÜ also says it won't expand existing services, and its current notice gives no date for opening new accounts.[1]
If you're already a merchant and want to add a payment method, currency or business line, check that your agreement covers it before you pay for development. The notice's qualified continuity wording gives no guarantee of access to any particular balance or feature.
Estonia's FIU explained the transition in its 30 June 2026 notice: providers awaiting authorisation must restrict activity, and firms without authorisation can't take new EEA clients or open new accounts there. That's general context, not a decision on this firm's application.[4]
- Money Services Business registration (FinCEN), Dream Finance US LLCUS31000313808665Claimed, not checked
- Money Services Business registration claim (FINTRAC), Dream Finance Processing Inc.; hub N300000209 conflicts with Canada Terms C100000308, neither independently register-matchedCAN300000209Claimed, not checked
- MiCA CASP application under review, Dream Finance OÜ; company says no decision and no new clients/accounts/agreements or service expansionEE (Finantsinspektsioon)Claimed, not checked
- Dream Finance UAB: all crypto services temporarily suspended, including transactions, new clients and agreements; current legal notice is undatedLTClaimed, not checked
| Licence | Jurisdiction | Number | Register check |
|---|---|---|---|
| Money Services Business registration (FinCEN), Dream Finance US LLC | US | 31000313808665 | Claimed, not checked |
| Money Services Business registration claim (FINTRAC), Dream Finance Processing Inc.; hub N300000209 conflicts with Canada Terms C100000308, neither independently register-matched | CA | N300000209 | Claimed, not checked |
| MiCA CASP application under review, Dream Finance OÜ; company says no decision and no new clients/accounts/agreements or service expansion | EE (Finantsinspektsioon) | — | Claimed, not checked |
| Dream Finance UAB: all crypto services temporarily suspended, including transactions, new clients and agreements; current legal notice is undated | LT | — | Claimed, not checked |
The Canadian documents disagree on one detail. The hub gives N300000209 for Dream Finance Processing Inc., while its Canada Terms give C100000308 for the same named company, and neither has been matched to a register. The US and Canadian companies aren't a way around another company's restrictions, so ask which agreement would cover your company and activity.[2]
A company existing, being allowed to offer a service, a product being available today and your own account being approved are four different questions, and no single document answers all four. This is general information, not legal advice.
Is this the same product as CoinsPaid Enterprise or Console?
CryptoProcessing is the merchant gateway; Enterprise and Console are different infrastructure products. CryptoProcessing's 14 July 2026 announcement describes independent companies with a shared brand history. That's the company's own account of the split, and we haven't verified who owns each one.[7]
For your shop, the difference is practical: accepting payments for your own goods is a different project from running a payment business for other merchants. Enterprise expects its customer to use its own licence and brand.[35] Console describes keys and signing in the customer's own environment, with its Payments Engine still labelled coming soon.[36] Neither gives a CryptoProcessing merchant account those controls or permissions.
| Your requirement | The relevant question |
|---|---|
| Accept customers' payments for your own goods | Which CryptoProcessing company can take you on now? |
| Run a branded payment business for other merchants | Which Enterprise agreement, plus your own permissions, would cover it? |
| Keep keys and signing in your infrastructure | Which Console modules are available and who operates them? |
| Know where this shop's revenue sits | What do this merchant account's custody and withdrawal terms say? |
How much does CryptoProcessing charge?
CryptoProcessing advertises "under 1.5%" and "1.5% or less" but doesn't publish a full merchant rate card. Your price comes from an offer you agree. The marketing page promises personalised pricing without giving a volume ladder you could apply to your own sales.[8]
Our calculator uses the 1.5% ceiling as a comparison figure, not a quote. It leaves out minimum commissions, network fees, conversion costs and bank or refund charges, and a cost with no price listed isn't a free one.
CryptoProcessing by CoinsPaidLowest estimate$150$150 1.50%
Published rate estimates only. Provider minimums, network, conversion, bank and account charges may be extra.
At 1.5%, $10,000 in sales costs $150, or $1.50 on each of 100 orders averaging $100, before those other costs. Your own offer could use a different rate.
A percentage-only fee doesn't change with order size, but real minimum charges can make small orders dearer than this flat 1.5% curve suggests.
The fee calculator guide explains what models like these leave out before you compare gateways.
What does the 1.5% leave out?
Conversion, per-operation minimums and getting money out each have their own prices, and a missing number isn't a saving.
OÜ's terms list standard exchange charges of 1% for buying or selling crypto against fiat and 0.8% for crypto-to-crypto exchange, with individually agreed terms taking priority. They leave open whether an automatically converted customer payment picks up an extra 1%, so don't treat conversion as free.[5]
The deposit documentation describes percentage charges with fixed or variable minimums. Some rows have a €0.10 floor, and Bitcoin uses a table that depends on the network. Those are deposit charges, not your payment-request tariff.[17] Fiat deposits and withdrawals can also carry percentages and minimums that depend on the method; these appear in the account rather than in a full public bank schedule.[11]
Ask for one itemised example that covers a normal payment, its conversion, your withdrawal and a refund. Your own withdrawal is a different thing from paying a supplier or a batch of recipients. Our processor selection guide shows how to compare offers like for like.
Which coins and networks can customers use?
The global documentation groups 14 assets, and the API table has 24 asset-and-network rows, which aren't 24 different coins. Which exact token and network are enabled depends on your account, so don't go by a logo or an older plugin description.[10]
For stablecoins, the listed pairs include USDC on Arbitrum, Base, BNB Smart Chain, Ethereum, Polygon and Solana; EURC on Base, Ethereum and Solana; and USDG on Ethereum and Solana. USDT isn't in that global inventory.
EURS is mentioned in marketing and legal documents, but we couldn't confirm it in the global inventory.
| Asset | Networks |
|---|---|
| USDC | Arbitrum, Base, BNB Smart Chain, Ethereum, Polygon, Solana |
| USDG | Ethereum, Solana |
| EURC | Base, Ethereum, Solana |
| EURS | Not stated |
If your customers hold USDT on TRON, offering TRX on Tron doesn't help, because they're different assets. Asking buyers to exchange first may add cost and lose you orders, so find out what your regular customers hold before deciding the menu is broad enough.
Three things need to stay distinct in your checkout demo: the invoice's price currency, the asset the buyer sends and the balance you receive.
Can you withdraw USD, GBP or euros to a bank?
The global documentation gives EUR full bank top-up and withdrawal support, while its other 31 fiat currencies are virtual balances. Seeing USD or GBP in the dashboard therefore doesn't mean you can withdraw in that currency.[9]
That matters if you pay dollar invoices. A dollar balance can help with pricing or bookkeeping and still leave conversion and a bank transfer to sort out, so don't forecast bank proceeds from marketing about a broad fiat menu. The global documents are silent on which bank currencies the US or Canadian companies have enabled.
- 01
Identify the account
Find out which company signed your agreement and what service it covers.
- 02
Name the receiving currency
Ask which balance can reach your own bank and what conversion comes before it.
- 03
Price and time the transfer
Get the method, minimum amount, minimum fee, bank charges and expected arrival.
- 04
Allow for review
Find out who answers document requests and what happens to access while a transfer is checked.
The fiat-withdrawal guide says a bank reference letter is required before the first withdrawal if you haven't already supplied one, and it publishes no bank-arrival schedule.[21] So don't plan payroll around a payment confirmation alone: your bank, the account's approval and any review can still hold things up after the customer's order looks paid.
If you need a different way to get paid out, the CoinGate fee guide shows why a withdrawal floor and a minimum transfer fee are two different charges.
Will the plugin work with your shop?
CryptoProcessing publishes guides for six ecommerce platforms, and each one requires an active merchant account, so a plugin can't get around the availability limits.
The WordPress directory now calls the package CryptoProcessing and lists version 1.0.14, with a changelog dated 9 October 2026. It shows 10+ active installations, WordPress 6.1 or newer, PHP 8.3 or newer and testing up to WordPress 7.1.3. The changelog's brief security-fix note leaves out what the vulnerability was, and for currencies, trust the current asset inventory over the listing's older claims.[14]
| Platform guide | What to find out |
|---|---|
| WooCommerce on WordPress | Whether the renamed package works with your checkout version and updates orders correctly |
| Drupal | Which payment module is maintained, and whether it works with your site |
| Joomla with VirtueMart | It's a VirtueMart extension, not a general Joomla checkout |
| Magento | Which marketplace or archive package it is, and which Magento release it supports |
| OpenCart | The archive comes from support, so ask about the version and who handles updates |
| PrestaShop | The module comes from support, so ask about compatible versions and environment settings |
Ask your developer for a maintenance estimate as well as installation time, and who owns updates. If your next shop upgrade changes checkout, or an order stays unpaid after the money arrives, someone has to investigate, with access to the transaction records and a way to fix the order without charging or shipping twice. A short installation guide doesn't price that ongoing work.
CryptoProcessing's developer article describes a sandbox with its own credentials. We haven't accessed it or verified that your account can get those credentials.[33] A Shopify mention in the marketing is no sign of a maintained Shopify package.
How does a payment become a paid order?
A payment request gives the customer a checkout link, and your shop then needs a reliable confirmation and the amount that arrived. The integration guide supports a hosted link, a QR code or an embedded checkout, and spells out the difference between the amount requested and the amount paid.[20]
You don't need to read code to set the acceptance rule. Ask your developer to demo a normal payment, an expired request, a short payment, a refund and a repeated notification, with whoever answers customers and whoever keeps the books watching, so you agree what the order screen, customer balance and accounts should show in each case.
Short payments make this concrete. The documentation's default rejects and refunds a short payment, minus a fee. A merchant can instead allow a percentage tolerance, a euro cap or both. In the documentation's 2%/€10 example, €98 is accepted against a €100 request, but a €1,000 request needs €990 because of the cap.[19] How much shortfall to accept is a business decision, not just an integration setting.
A callback needs testing too. The documentation tells developers to verify each callback's signature and recognise duplicates. A second notification mustn't send another parcel or credit the customer's balance twice.[13] A successful browser return alone is no confirmation of payment.
Recurring invoices need their own demo. The API product page advertises them, but that isn't permission to debit a customer's wallet unattended, and we couldn't confirm that a full renewal scheduler or a commercial white-label package exists.[26] If you sell subscriptions, spell out what happens each month and what the customer has to do again.
What checks and custody conditions affect the money?
Business approval and later payment checks are part of the service, so plan for them in your cash flow. KYB is a check on your business, which is a different matter from whether customers can pay from a crypto wallet. The US AML policy describes identity, beneficial-owner, geography and risk checks, with extra scrutiny where required.[34]
Customer information can affect checkout too. The EU documentation asks for names and birth dates for individuals, or company name and registration country for companies, and if that information isn't already on file, a form can appear before the payment address is shown.[18] Ask what your customers will see; the checkout shouldn't be advertised as anonymous.
The gateway is custodial: OÜ's terms say the provider manages keys and may pool assets in wallets while tracking balances individually.[5] Console's customer-key model doesn't apply to this merchant account, and a balance here isn't money already credited to your bank.
The US terms permit compliance holds and delayed withdrawals without a fixed release deadline. They require you to report an error or unauthorised transaction immediately and no later than seven calendar days. That's a reporting window and carries no promise to resolve the problem within a week.[6]
A reserve policy and a transaction hold are different things. We couldn't confirm an insured balance, a fixed reserve schedule or a guaranteed release time. Decide who watches for notices and supplies documents, and keep enough other money on hand for bills if a payment or withdrawal goes under review.
iGaming and forex appear in the product marketing, but nothing there approves every operator, player market or regulated activity, and we couldn't confirm adult or VPN acceptance. Describe your real activity and the permissions it needs before you consider a provider, and don't read a missing list of prohibited activities as "nothing is restricted". Our high-risk merchant guide covers how to judge it.
Can you refund a customer or pay a batch of recipients?
The documentation covers refunds, but the customer may have steps to complete and the amount returned can be lower after charges. Automatic returns for late, short or excess payments work differently from merchant-initiated ones, and either way the refund goes back in the asset and network the payment used, with an emailed form for the customer's destination.[12]
Your support policy should explain those steps without promising a free or instant return. The US terms require available refundable amounts and meeting fee and minimum conditions, and fees already charged aren't generally returned, subject to legal or written exceptions.[6] Each company has its own table, so don't merge them into one refund floor.
If a $100 order is cancelled and the customer asks for $100 back, the original fee isn't necessarily reversed and the return may carry a network cost, so get the refund quote before promising what reaches their wallet. Keep enough available balance for permitted refunds, and have someone follow up when the customer doesn't reply to the email.
Mass payouts are a different operation from taking payments. The product page allows up to 100 transactions in one CSV file and lists its own charges and network mining costs as two items. Its claims of minutes-long processing and round-the-clock support are the provider's promises, not our measurements.[22] Don't apply that timing to a bank withdrawal, or that fee to receiving a customer's invoice.
- 01
Check the permitted purpose
Make sure your account and agreement allow these recipients and this activity.
- 02
Review the batch totals
Look at recipient amounts, fees and network costs as three lines before you approve anything.
- 03
Follow each recipient
Track each recipient as paid, pending or failed; a submitted file can still leave some recipients unpaid.
How much confidence should you put in support and the score?
Support availability is a promise to be reachable, and the score is a comparison of inputs we collected. Neither shows that your next problem will be fixed quickly.
The support offer includes account management and email, and the mass-payout page also describes live chat and 24/7 assistance. A first-response target says nothing about when money becomes usable, so ask which channel handles a held transfer, an order error or an urgent refund.
Current public reviews don't support a merchant success rate. The old CryptoProcessing rating snapshot rested on one review, and the related CoinsPaid profile covers a different brand history. We don't have a refreshed aggregate or a current uptime reading, so an old star figure or a status-page link is no payout guarantee.
Security history needs care too. CoinsPaid's own account describes a July 22, 2023 theft of $37.3 million and says customer funds were unaffected. The FBI's August 22 release attributes a $37 million CoinsPaid theft to DPRK TraderTraitor actors but dates it June 22. Neither tells you about today's contracting company's liability, compensation or reliability, and we haven't confirmed a second 2024 incident from a company original.
Reviews draw on dated documents and calculations. Scores reflect recorded inputs; account approval, full costs and service performance need separate checks. We haven't opened merchant accounts or made test payments. How we score
The formula doesn't score historical incidents or decide whether a new account can open, and unknown extra costs stay outside its arithmetic. Our ranking methodology explains why a useful comparison can still leave the big questions open.
What are the practical pros and cons?
The tools could save an existing eligible merchant from building payment handling from scratch, but account availability and receiving costs with no listed price are big limits. The pros describe what the documents say it can do, not a recommendation to start an account that isn't currently available.
- Payment requests with hosted, QR and embedded checkout options
- Documentation covers amount matching, short-payment choices and duplicate notifications
- Six platform guides and a currently listed WordPress package
- Full and partial refunds, in the asset and network the customer paid with
- A euro bank payout for accounts approved for it
- OÜ has paused new clients, accounts, agreements and service expansion, and UAB has suspended all crypto services
- The 1.5% ceiling isn't a full merchant quote or a volume ladder
- USD and GBP are virtual balances, not direct bank withdrawals
- The Canadian registration numbers conflict, and neither has been matched to a register
- Minimums, conversion, bank charges and refund conditions can change the final bill
- This review has no measurement of current reputation, uptime, account access or software compatibility
Which alternatives should you investigate?
Pick an alternative to fit your company, your activity and how you need to be paid. These three suit different merchants, and none of them is a way around verification, licensing or sanctions obligations.
For an ordinary US or Canadian retailer, BitPay is worth a look: its country guide accepts merchant applications there while pausing new EEA, UK and Australian onboarding.[23] Its merchant terms still require approval and treat prohibited and restricted businesses differently, so that suggestion doesn't cover gambling, forex or adult activity.[37] The BitPay review goes into what it quotes for getting paid out.
For an ordinary retailer in a listed country such as Germany, CoinGate is a candidate. Its current list includes Germany and Canada but not the US.[24] Its account terms require eligibility and checks, so your owners, activity and bank still need approval. The CoinGate review explains its merchant product.
For a lawful Bitcoin merchant with people who can manage hosting and wallet security, BTCPay Server is a different model: self-hosted invoicing that pays straight into the merchant's wallet, with no processor subscription or transaction charge. Hosting, network transfers, support and any conversion still cost money or work, and plugins or outside services have their own eligibility conditions.[25] You'd still need a bank account, and your business obligations stay with you.
The list below orders the three by our scoring formula, not by whether you'd be eligible. Its fee figures leave out the extra costs, so get an approved offer and a payout method before you compare totals.
- 1
CoinGateWorth a look for a retailer in a country it supports today
81/1001%- Its country list includes Germany and Canada
- Merchant checkout and business balances
- The US isn't on its list, and your activity and bank still need approval
- 3
BitPayWorth a look for an ordinary US or Canadian retailer
73/1002% + $0.25- Takes merchant applications in the US and Canada
- A dedicated product for selling your own goods
- You still need approval and activity checks, and new EEA, UK and Australian onboarding is paused
- 12
BTCPay ServerFor a lawful Bitcoin merchant that can operate its own setup
57/1000%- Payments go straight to your wallet in its non-custodial setup
- No processor subscription or transaction charge
- Hosting, wallet security, support and any conversion service are yours to run or arrange
What evidence matters before you decide?
Let the current restrictions and your agreement decide whether more integration work makes sense.
Show the evidence log (10 checks)+
| Checked | What we checked | Finding | Source |
|---|---|---|---|
| 2026-10-14 | Company availability | OÜ has paused new accounts and expansion, and UAB has suspended all crypto services, including transactions. | CryptoProcessing legal hub |
| 2026-10-14 | Canadian registration | The Canada Terms give C100000308 and the hub gives N300000209, and neither has been matched to a register. | Canada Terms |
| 2026-10-14 | Advertised fee | The advertised 1.5% is a ceiling, and we found no full public merchant quote or volume ladder. | Accept crypto |
| 2026-10-14 | Exchange charges | OÜ's terms list a 1% fiat exchange charge and 0.8% for crypto exchange. It's unclear whether that stacks on automatic conversion. | OÜ Terms |
| 2026-10-14 | Receiving currencies | Euros have full bank support, while 31 other currencies are virtual. What your account gets depends on approval. | Supported currencies |
| 2026-10-14 | Software listing | WordPress lists version 1.0.14 with a 9 October changelog. Its compatibility details aren't an install test. | WordPress directory |
| 2026-10-14 | Payment matching | The requested and received amounts can differ, so your records should use the amount that arrived. | Payment-request integration |
| 2026-10-14 | Customer returns | Automatic and manual refunds go back in the asset and network the payment arrived in, with conditions and charges. | Refund guide |
| 2026-10-14 | Sandbox | The documentation describes a test environment. We haven't accessed or tested it. | Developer article |
| 2026-10-14 | Other products | Console's customer-held keys and its coming-soon Payments Engine don't describe the merchant account. | Console product page |
CryptoProcessing review FAQ
Can a new EU merchant sign up now?
Is 1.5% the complete CryptoProcessing fee?
Does the 1% exchange charge always come on top of the fee?
Can I withdraw a USD or GBP balance directly?
Does CryptoProcessing accept USDT on TRON?
Can customers get full or partial refunds?
Is there a WooCommerce plugin and a sandbox?
Is the merchant gateway non-custodial?
Does a high score mean it's available or safe for me?
Which alternative should an ordinary shop consider?
Change log: 14 October 2026, first published review of the merchant product, covering availability limits, cost examples at the 1.5% ceiling, current software details and the checkout and refund conditions.
Sources
40
Numbers in square brackets in the text link to these sources.
- CryptoProcessing legal hub: operator availability and registration claims · Checked 2026-10-14
- Dream Finance Processing Inc. Canada Terms, updated 17 July 2026 · Checked 2026-10-14
- Dream Finance UAB Terms and current suspension notice · Checked 2026-10-14
- Estonian FIU transition notice, 30 June 2026 · Checked 2026-10-14
- Dream Finance OÜ General Service Conditions, updated 17 July 2026 · Checked 2026-10-14
- Dream Finance US LLC Terms, updated 25 September 2026 · Checked 2026-10-14
- CryptoProcessing independence announcement, 14 July 2026 · Checked 2026-10-14
- CryptoProcessing merchant payment pricing and product page · Checked 2026-10-14
- Supported currencies: assets, EUR and virtual balances · Checked 2026-10-14
- API currency codes and payment-request network names · Checked 2026-10-14
- Fiat operation fees and account-specific minimum charges · Checked 2026-10-14
- Payment request refunds: customer steps and original payment network · Checked 2026-10-14
- Callbacks: authentication, retries and repeated notifications · Checked 2026-10-14
- CryptoProcessing WordPress listing: version 1.0.14 and compatibility metadata · Checked 2026-10-14
- Operational documentation: restricted activity notice · Checked 2026-10-14
- Company MiCA application update, 30 June 2026 · Checked 2026-10-14
- Crypto deposit fees: separate operations and static or dynamic minimums · Checked 2026-10-14
- Payer and recipient information in EU-scoped documentation · Checked 2026-10-14
- Payment requests: underpayment tolerance and default refunds · Checked 2026-10-14
- Payment-request integration: checkout and amount received · Checked 2026-10-14
- Fiat withdrawal guide and bank reference letter · Checked 2026-10-14
- Mass payouts: file limit, processing costs, mining and support claims · Checked 2026-10-14
- BitPay supported onboarding countries, updated 3 October 2026 · Checked 2026-10-14
- CoinGate supported countries · Checked 2026-10-14
- BTCPay Server General FAQ: direct receipt and operating responsibilities · Checked 2026-10-14
- CryptoProcessing API product page: recurring invoice marketing · Checked 2026-10-14
- WordPress integration guide: active merchant account requirement · Checked 2026-10-14
- Joomla integration guide: VirtueMart and account requirement · Checked 2026-10-14
- Magento integration guide: marketplace and archive paths · Checked 2026-10-14
- OpenCart integration guide: support-distributed archive · Checked 2026-10-14
- Drupal integration guide: account and payment module · Checked 2026-10-14
- PrestaShop integration guide: archive and sandbox setting · Checked 2026-10-14
- Developer integration article: published sandbox, 29 June 2026 · Checked 2026-10-14
- Dream Finance US LLC AML policy, updated 12 December 2025 · Checked 2026-10-14
- Coinspaid Enterprise: infrastructure under the customer's licence · Checked 2026-10-14
- Coinspaid Console: client key control and coming-soon Payments Engine · Checked 2026-10-14
- BitPay merchant acceptance terms, effective 1 April 2026 · Checked 2026-10-14
- CoinGate general terms, effective 1 January 2026 · Checked 2026-10-14
- CoinsPaid's historical incident account: earlier successful reading · Checked 2026-10-14
- FBI historical attribution, 22 August 2023: earlier successful reading · Checked 2026-10-14
