GoUrl vs Apirone

Same model, opposite fee placement#

GoUrl states that no customer money is kept on its servers and that payments are forwarded automatically to the merchant's own addresses. Apirone settles to a merchant-controlled wallet on the same principle.

One charges 1.5% when the payment arrives. The other charges nothing then and a fixed amount when funds move out, which behaves very differently across withdrawal sizes.

A fixed withdrawal fee costs the same on a small withdrawal as on a large one, so it punishes frequent sweeps and rewards patience. A percentage on acceptance is indifferent to both.

Fourteen coins named against three networks#

One card enumerates every asset: Bitcoin, Bitcoin Cash, Bitcoin SV, Litecoin, Dash, Dogecoin, Speedcoin, Reddcoin, Potcoin, Vertcoin, Feathercoin, Peercoin, UniversalCurrency and MonetaryUnit.

The other publishes no count and names Bitcoin, Litecoin and Dogecoin. Three named networks is a floor rather than a list, and coverage has to be confirmed by asking.

An exact enumeration is worth crediting even when its contents are dated. A merchant can check the fourteen against their own customers in a minute, which is not possible on the other side.

Neither list contains a stablecoin#

This is the line that decides the pair for most readers. No Tether, no USDC, no Ethereum and no Tron on either card, and stablecoins are what the majority of crypto payments now are.

Both are coherent products for a customer base holding Bitcoin or Litecoin, which does exist and is smaller every year.

If your customers pay in dollars-on-chain, this comparison is academic and the USDT list is the page to read instead.

Plugins favour one side clearly#

WooCommerce, Magento, OpenCart and VirtueMart on one card; WooCommerce plus a shelf of WordPress add-ons and ten client libraries on the other.

VirtueMart appears nowhere else in this index, which makes one of these the only supported option for a Joomla store. That is a narrow advantage and an absolute one where it applies.

The library-heavy side is aimed at developers rather than shop owners: PHP, Laravel, Python, Java, C#, Node and ASP.NET are covered, and most mainstream storefronts are not.

Verification is stated on one card#

One publishes simple registration with no verification process, as a selling point. The other records merchant verification as undisclosed after checking.

For a non-custodial forwarder the stated absence is internally consistent: there is no balance to safeguard, so there is less for a verification file to protect.

It suits merchants refused elsewhere and businesses that will not queue for onboarding. What a merchant gives up alongside the paperwork is covered in the verification guide.

Both companies are named, in different places#

Delta Consultants Ltd, registered in the Commonwealth of Dominica under number 11755, against an Estonian operator with a stated founding year of 2017.

Publishing the entity and its number is more than most cards in this index manage, and the offshore registration matters less here than it would for a custodial provider.

That is the practical upside of the shared model. Neither company holds a merchant balance, so the exposure is one settlement rather than an accumulated position.

Fiat settlement exists on neither#

One documents fiat settlement as absent and the other leaves it unpublished. Either way a merchant receives crypto and converts elsewhere.

That follows from the shared non-custodial design rather than from any decision either could reverse, and fighting it means choosing the wrong tool rather than negotiating harder.

A business that needs euros or dollars in a bank account should treat this pair as informational and start from the custodial providers instead.

The economics of an old product#

Both cards read as products built for a market that has moved. Proof-of-work coin lists, WordPress plugins and forwarding to your own address describe crypto payments as they were understood some years ago.

That is not a criticism of either. Neither has broken, both still do what they say, and a merchant whose requirements have not changed either is well served.

It does mean neither is likely to gain a stablecoin rail soon. Treat the current asset lists as the durable answer rather than as a starting point.

What to ask each of them#

To the free-acceptance provider: the enumerated asset list, since the public pages do not give one and the answer may make the comparison unnecessary in either direction.

To the flat-rate provider: whether the fee applies to the forwarded amount or the invoiced amount, since forwarding costs a network fee that has to come from somewhere.

To both: what happens when a payment arrives after the invoice expires, which on a forwarding model is a more common event than merchants expect.

Where this pair actually lands#

A Joomla or Magento store taking Bitcoin and Litecoin, withdrawing occasionally, takes the free-acceptance card and pays a fixed amount a few times a year.

A WordPress site or a developer-built checkout that wants no verification and an enumerated asset list takes the flat 1.5% card and knows precisely what it is buying.

Anyone whose customers hold stablecoins should close this page. Neither card can accept them and no other line on either one compensates for that.

Refunds are your job on both#

Without a provider balance there is nothing to refund from. A refund on either card is a payment you construct and sign yourself, from the wallet holding the funds, at whatever the rate is that day.

That is workable and it needs a written process before the first refund rather than during it, including who holds the key that signs it and what the accounting entry looks like.

The price move between sale and refund lands on the merchant in both cases, which is the part small stores discover late and the part the refunds guide exists to cover.