Triple-A vs BVNK

One publishes a rate and one does not#

Triple-A publishes 1% on processing. BVNK publishes nothing on processing, conversion or the fee side at all.

What the second card does publish is the payout side: network fee estimates passed through, with internal transfers and wallet custody free. That is useful and it is not the number a merchant came for.

A published one percent that can be compared beats an unpublished rate that has to be extracted, even when the extracted rate turns out lower. This index scores what a reader can check.

Both ask for business and personal checks#

Business and personal verification is published on both cards, which is the most demanding requirement in this index and the most predictable.

For an enterprise buyer that is unremarkable and expected. For anyone hoping to be live this afternoon, both cards are closed before the rate is discussed.

It also means neither is competing on onboarding speed, which frees them to compete on treasury mechanics instead, and that is where the interesting differences sit.

A named jurisdiction against none#

One is based in Singapore and says so. The other records its jurisdiction as not stated on its public pages, despite requiring the most demanding verification here.

That asymmetry is worth naming. A provider that asks a merchant for incorporation documents and ownership details might reasonably publish its own.

Both date from the same era — 2018 and 2021 — and neither is a long-established name. Operating history is not what either is selling.

Four assets against an unpublished count#

One publishes four assets across Ethereum, Bitcoin, Tron and Solana. The other names Bitcoin, Ethereum and Tron and publishes no count.

Four is the narrowest published figure among the general processors here, and it is consistent with a business built for stablecoin treasury flows rather than for consumer checkout.

Both include Tron, which carries the largest share of consumer stablecoin volume, so the mainstream rail is covered on either side.

One plugin against zero#

WooCommerce and an API on one side, an API alone on the other. Neither is aimed at a storefront and one has at least made the gesture.

For a WordPress business the difference is an install against a build. For a treasury operation the plugin is irrelevant and the API documentation is the whole evaluation.

Neither card lets a developer judge that API from public pages, which is a shared weakness rather than a distinguishing one.

Fiat settlement and mass payouts on both#

Both document settlement into bank currency and both document bulk payouts. That overlap is why this pair is comparable: same verification bar, same treasury shape, same two core products.

White label, recurring billing and point of sale are recorded as unpublished on both. Neither is selling a checkout experience.

Hosted invoicing splits them, documented on one card and unpublished on the other, which is a small line and the only product difference of substance.

Sixty-eight percent disclosure on each#

Both publish thirteen of the nineteen fields this index tracks, which puts them level and mid-table. The fields differ: one withholds the fee side, the other withholds asset detail and product surface.

Level disclosure with different gaps is a useful reminder that a single percentage hides what is missing. Read the blanks rather than the number.

The missing processing rate on one side is the single most consequential blank on either card, because everything else can be worked around and a price cannot.

How the totals separate#

Cost does most of the work, as it usually does when one card publishes a rate and the other does not. Onboarding scores low on both, because business and personal verification is a real barrier and the method reports it as one.

Support is the one criterion where the unpublished-rate card scores higher, reflecting better-documented operational behaviour around network fees and custody.

Neither total is high. These are two providers that answer a narrow set of questions well and leave the rest to a sales conversation.

What to ask each of them#

To the unpriced provider: 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 skip.

To the priced provider: the enumerated asset list and the payout cost, both recorded as unpublished after checking.

To both: how long verification takes in weeks rather than in document names, and which verticals are refused before the file is opened.

Where this pair actually lands#

A business that wants a published number and a named jurisdiction takes the Singapore card, pays one percent, and gets a WooCommerce path into the bargain.

A treasury operation moving stablecoins in volume, with procurement behind it, takes the other and accepts that every figure arrives by email.

A small merchant should take neither. Both require the heaviest verification in this index, and the reward for passing it is an enterprise relationship rather than a cheap checkout.

What a treasury buyer checks that a merchant does not#

Settlement timing, cut-off windows and which regulated institution holds the balance overnight. None of that appears on either card and all of it decides whether a finance function can use the provider.

Both publish that network costs are handled predictably, which is the closest either comes to an operational commitment. It is a good sign and it is not a service level.

Ask for the settlement schedule in writing, including what happens on a weekend and at a month end. Those are the two moments a payments relationship is actually tested.