xMoney vs BVNK

Regulatory disclosure is the product on both#

xMoney names a licensed financial institution supervised by the Bank of Romania for card services, a registered virtual asset provider in Portugal and a licensed one in Estonia for crypto.

BVNK publishes what it requires from merchants — business and personal verification — which is a different kind of disclosure and equally rare in this index.

Between them these two answer the questions a bank asks about a payment provider better than most of the field, and neither answers the question a merchant asks first.

Neither publishes a rate of any kind#

Processing, conversion and payout are unpublished on both cards. That is the widest cost gap available in this index and it appears on the two most institutionally presented providers here.

The two facts are connected. A provider selling through a sales team prices by negotiation, and publishing a number would only anchor a conversation it would rather have privately.

One of the two does publish something adjacent: network fee estimates passed through, with internal transfers and wallet custody free. That is a partial answer and it is more than the other offers.

Six networks against four assets#

One names Bitcoin, Ethereum, Solana, MultiversX, Sui and Dash. The other publishes four assets across Ethereum, Bitcoin, Tron and Solana.

Neither is a broad-coverage product and neither is trying to be. Both are built around stablecoin settlement between businesses rather than around consumer checkout variety.

Tron matters more than its absence from one list suggests, since it carries the largest share of consumer stablecoin volume. A business receiving from retail payers should check that specifically.

Product breadth is the real separation#

One offers payment processing, recurring billing, marketplaces, card issuing, invoices and payment links, with settlement in euros, dollars, lei or stablecoins.

The other is narrower and deeper: stablecoin acceptance and mass payouts with fiat settlement, aimed at treasury flows rather than at storefronts.

A marketplace with sellers to onboard and subscriptions to bill has one obvious choice here. A business moving stablecoins between counterparties at scale has the other.

Verification requirements, stated and unstated#

One card publishes business and personal verification as the requirement. The other records merchant verification as undisclosed after checking, despite operating as a licensed institution.

The stated requirement is more useful even though it asks for more, because a merchant can plan a timeline around it rather than discovering it mid-integration.

Both are regulated entities and both will require a file. The difference is whether you learn that before or after committing engineering time.

Both settle fiat, one names its own tokens#

Payouts in euros, dollars or lei on one side, alongside the provider's own euro, dollar and leu instruments. Fiat settlement on the other side without a comparable token layer.

Issuing your own denominated instruments is a distinctive position and one to understand before relying on it. Establish what backs them and how redemption works before treating them as cash.

For most merchants the plain fiat leg is what matters, and both cards have one. The token layer is an option rather than a requirement on either.

Integrations are an API on both#

Neither names an ecommerce plugin. Both document an API and expect the counterparty to have engineers, which is consistent with who they sell to.

That removes a whole category of merchant from this pair. A shop owner wanting to install something and move on should read the WordPress list instead.

For a platform the API-only shape is neutral information, since the work was going to be a build regardless of what plugins existed.

What to ask each of them#

To both: the processing rate, the conversion spread and the minimum volume that gets a quotation at all. The third question saves the most time and is the one merchants forget to ask.

To the licensed institution: which entity is the counterparty on your contract, since three are named and they sit in three jurisdictions with different supervisors.

To the stablecoin business: what verification takes in weeks rather than in document names, and which verticals are refused outright before the file is opened.

How the scores land#

Both sit in the lower half of this index and neither number reflects product quality, which cannot be assessed from public pages. It reflects what each publishes.

Cost drags both hard, carrying joint-top weight in the method and finding nothing to score. Onboarding separates them, rewarding a published requirement over an unstated one.

A reader who genuinely cannot use cost as a criterion — because a quotation is coming either way — should reweight it downward and read the resulting order instead.

Where this pair actually lands#

A European business needing card and crypto acceptance under one regulated contract, with subscriptions or a marketplace attached, takes the licensed institution and budgets for the sales conversation.

A business moving stablecoins in volume, with a finance function that will read the verification requirements before anything else, takes the infrastructure provider.

A small merchant should take neither. Both are built for organisations that expect procurement, and a business without one will spend weeks getting a number that a published rate would have given in seconds.