CoinsPaid Review: Enterprise, Console and the Merchant Question

Is CoinsPaid a merchant gateway or an infrastructure supplier?

The CoinsPaid website now sells infrastructure, while CryptoProcessing is the one that serves merchant payments. Its homepage offers Enterprise for a branded digital asset business and Console for operations you control in your own environment.^[1] If you just want an order paid, knowing that saves you a long sales conversation about the wrong product.

CoinsPaid's July announcement describes Solutions, CryptoProcessing and Dev as independently owned and operated companies with a shared brand history. That's the company's own account, and we haven't audited who owns what.^[6] CryptoProcessing's own announcement makes the same distinction and names Dev as the engineering business.^[20]

A checkout account and Enterprise aren't interchangeable subscriptions: Enterprise helps you run a service for customers, while a merchant account accepts payments for your own sales. Our CryptoProcessing review covers the merchant product and its current account restrictions.

Who should consider Enterprise?

Enterprise is worth a look when your business already has the permissions and people to sell a payment service. Its target customers include licensed payment institutions, crypto service providers and regulated fintechs. It requires your own licence and describes custody, connectivity, liquidity and compliance tooling run by the supplier.^[2]

In plain English, the supplier provides much of the machinery and you run the business. A PSP still needs an offer merchants want, people to approve customers and someone to answer their questions. Whether your pricing covers those jobs is for you to work out.

The supplier's modernization article says the institution keeps its merchant and treasury relationships while its team uses the operating portals, and it mentions external liquidity providers and custodians as options.^[9] Which of those apply to you depends on your quote.

1. 
   01

   Name the service

   Say who your customers are, what they'll pay for and where you need to serve them.

2. 
   02

   Assign the work

   Decide who handles merchant approval, pricing, funding, customer support and the daily financial records.

3. 
   03

   List what the supplier covers

   Write down which custody, conversion, banking and compliance services the proposal includes.

4. 
   04

   Set the launch conditions

   Get the contract, permissions, operating checks and support terms in place before you send customers through it.

A portal can organise merchant records, but your team still decides who to serve, how to charge and what to tell a customer when a payment needs review. The processor selection guide helps you tell a real payment requirement from a feature wishlist.

When is Console the better fit?

Console is the better conversation when control of your own keys and transactions is central to what you need. Its product page describes deployment inside your environment, modular capabilities and managed blockchain connectivity, and labels the Payments Engine, tokenization and agentic payments as coming soon.^[3] Don't build your launch on an unfinished module.

Control brings work. Who on your team can approve a transfer, restore access and step in when an approver leaves? You'll need recovery and emergency access that works at night, at weekends and through staff changes, and a clear line between what your team does and what stays with the supplier.

The supplier's bank-use article splits the customer-facing financial product from the wallet, monitoring and settlement components underneath.^[12] That split helps you narrow what you buy. If you only need a better view of balances, ask about that module and don't assume you're getting a finished merchant checkout.

Does the Core name resolve the custody question?

No. The public wording isn't consistent enough to choose a custody model from CoinsPaid's Core name. The general FAQ uses Core for provider-managed funds, while the modernization article describes Core with keys and signing staying in the customer's environment.^[4] Only the control terms in your agreement settle who holds the money.

Ask the supplier to draw out your own payment flow. Who creates the receiving wallet? Who can sign a withdrawal? Who can stop it? Who restores access if the usual approver is away? The answers should be the same in the proposal, the security review and the contract.

The infrastructure explainer also uses its own architecture-layer terms and says they aren't the usual scaling-network meaning.^[11] You don't need the supplier's layer names to decide, just a clear account of the work included and the control you keep.

What does CoinsPaid cost?

The public sources we read have no complete Enterprise or Console price list, so we have no verified fee percentage, setup bill, monthly minimum or saving to give you. Leave unknown amounts blank until the supplier quotes them.

A general business-product explainer includes broad percentage and inherited-compliance language in its build-versus-buy comparison.^[13] That isn't an Enterprise offer, and the product's own-licence requirement still applies. Likewise, CryptoProcessing's merchant price says nothing about the infrastructure price, even though the brands share a history.

A quote should cover the operations you described, including the work before launch and the charges that continue in a quiet month, so a low transaction rate doesn't hide the cost of keeping the service running.

Our fee calculator works from published merchant rates, so it can't price this supplier quote, and the ranking methodology explains why gateway scores say nothing about an infrastructure deal.

Which coins, currencies and banks would you get?

You need a written list of assets and banks for the deployment you're being offered. Broad coverage claims say nothing about what your customer can send or what reaches your account.

The PayAdmit announcement shows the problem. It describes PayAdmit's fiat payment tools alongside CoinsPaid's blockchain services, with broad claims about past chain support and fiat conversion.^[16] A partner's payment-method catalogue isn't your approved bank-currency list, and a conversion balance doesn't mean a bank will accept an outgoing transfer in that currency.

For each payment path you plan to use, ask for the exact asset, network, permitted sender, conversion pair, receiving provider and bank currency, plus the minimum amount and all charges. A customer who says they hold dollars could mean a bank balance or a dollar-linked token on any of several networks.

Promise customers a token only when your own agreement lists it, not because it appears in an example, a partner announcement, another product's documentation or a list of merchant gateways.

Which company and permissions should you check?

Start with the company you'd contract with and the service you plan to offer. CoinsPaid's contact page names Coinspaid Solutions OÜ.^[7] The official business register entry, read on 14 October, identifies company 17541786, registered on 30 June 2026; a later reload failed. That identifies the company and nothing more: who signs your contract, whether it holds a financial licence and whether you'd be approved are still open.^[8]

The About page's experience claim describes the team and the business's history, not the age of this particular legal entity.^[5] When you ask about operating history or liability cover, find out whose experience, contract and obligations the answer describes.

On the merchant side, CryptoProcessing's current legal hub pauses new clients, accounts, agreements and expansion at Dream Finance OÜ, and Dream Finance UAB has suspended all crypto services, including transactions.^[17] An infrastructure inquiry isn't a way around those notices.

Its Canadian documents also conflict: the hub gives N300000209, while the Canada Terms give C100000308 for the named merchant company, and we haven't matched either to a register.^[18] Those are claims about the merchant company, not Solutions permissions or a tip to open an account elsewhere.

Estonia's FIU notice explains the transition from July and the restrictions pending authorisation.^[19] It's general context, not a ruling on your Enterprise plans. A qualified adviser can tell you which permissions your company, customers and services need. This is general information, not legal advice.

How much integration and operating work remains?

Plan for launching a business, because the technology won't remove all the work. Enterprise's several-month estimate describes a different project from the generic FAQ's quick plugin and API integrations, and neither is your delivery date.

CoinsPaid's payment-architecture article discusses authenticating requests, tracking operations, verifying notifications and recovering from interrupted work without duplicate payments.^[14] It tells you what to ask, but we haven't seen an Enterprise API reference, confirmed sandbox access or proof that those guarantees are implemented.

Give your developer a short brief: which operations matter, what you need to see in the numbers and what customers should be told when something fails. The supplier can then demonstrate those outcomes in an evaluation it arranges. We haven't obtained access or run any such check.

1. 
   01

   Confirm what's supplied now

   List the modules, environments and assets supplied now, and keep roadmap items off the list.

2. 
   02

   Define the records

   Agree which balance and transaction records you'll rely on and how differences get investigated.

3. 
   03

   Rehearse exceptions

   Test delayed, failed and repeated operations in an agreed evaluation, with clear messages for customers.

4. 
   04

   Name the owner

   Say who maintains the integration, reviews changes and handles urgent support after launch.

CoinsPaid's monitoring article describes distinct payment, compliance, finance and security roles.^[10] A support agent should know whether an order is waiting for payment, a policy review or the bank, and who can do something about it.

Refunds and holds need an agreed process of their own. A final blockchain payment says nothing about who approves a customer return, who supplies the money or what charges apply, and we haven't found Enterprise's contractual refund or release deadlines. Ask about wrong-network payments, unanswered customer requests and a balance under review before promising a free or immediate return.

If your customers run regulated or sensitive businesses, describe the activity accurately. Product marketing aimed at a sector is no approval for every operator or market. Our high-risk merchant guide explains how that check works.

How should you judge security, support and supplier risk?

Judge the proposed controls and commitments together, since neither a marketing claim nor a historical incident alone gives you the present risk. The security evidence, liability terms and support terms need to cover the company and configuration you'd use.

Earlier company material describes a July 22, 2023 theft of $37.3 million and says client funds were unaffected. The FBI's own release attributes a $37 million CoinsPaid theft to DPRK actors but dates it June 22.^[23][24] Neither says anything about today's Solutions contract liability, insurance or compensation. We haven't confirmed a second incident in 2024 from a company original.

Think through the bad day. For support, request a channel for urgent operational problems, a response commitment and a restoration commitment of its own. A quick reply is no sign that a held balance is available. Work out who can escalate, what records they need and how customers get updates.

CoinsPaid's build-or-buy article raises supplier dependence, continuing operation and exit planning.^[15] Ask how you'd get usable data, keep customer records and move to another permitted provider if the relationship ended. Contractual help during the move matters as much as being able to download a file.

Banks have a broader reference point: the Basel Committee's publication sets a baseline for third-party risk, and its companion release says it covers banking and that Committee decisions have no legal force.^[21][22] That's context, not confirmation that CoinsPaid meets a particular bank's requirements, and we haven't reviewed the full linked principles.

What are the practical pros and cons?

The useful part is the choice of operating models. The weakness is how much of the commercial and delivery picture is unverified.

Should you shortlist CoinsPaid or look elsewhere?

Shortlist it if you have an infrastructure requirement you can define and operate, then judge the offer on its terms. If the supplier can't pin down control, what's available now, full costs and contractual responsibilities for that requirement, don't base your launch on a broad product promise.

For your own retail sales, start with merchant reviews such as BitPay and CoinGate, and check their current country, activity and bank conditions. They're a different purchase, and neither review means you'd be approved. The gateway comparison is another place to start, though its scores don't rank an Enterprise or Console proposal.

Which findings should you verify before a decision?

Recheck the dated documents and get the terms for your own deployment. The log shows what the public evidence says. It doesn't certify account access, an operating platform or a finished supplier review.

CoinsPaid review FAQ

Change log: 15 October 2026, rewrote this review around Enterprise and Console in place of merchant checkout.