We Installed Crypto Payment Plugins on Three Shop Platforms

Most merchants integrate crypto payments through a plugin rather than an API. We tested plugins on three common shop platforms. For the tests below we used a licensed crypto payment processor as the reference, because it publishes the figures we were measuring against.

Installation

Between eight minutes and two hours.

The fast cases were official plugins maintained by the payment provider. The slow one was a community plugin last updated eighteen months earlier, which required a compatibility fix.

Check who maintains the plugin and when it was last updated. That predicts the experience better than any feature list.

Configuration gaps

Plugins expose a subset of what the provider’s API supports.

Underpayment tolerance: configurable in one plugin of three, despite being supported by all three providers.

Confirmation thresholds by amount: not configurable in any plugin, though two providers support it. All three plugins applied a flat policy.

Payment window: configurable in two.

Network selection per asset: exposed in one, meaning the other two accepted whatever the provider defaulted to.

The gap between provider capability and plugin capability is where most of the operational friction sat.

Order status handling

All three updated order status on successful payment correctly.

Partial payment: one handled it, marking the order partially paid. Two ignored it, leaving the order unpaid with funds received.

Payment after expiry: one handled it. Two left the order unpaid with the funds credited to the merchant balance, requiring manual matching.

Those two cases together accounted for most of the manual work during testing.

Refunds through the plugin

One supported refunds from the order screen. Two required logging into the provider’s dashboard, which means the refund is not recorded against the order automatically. At company scale the measurement changes, and a provider serving law firms and corporate services is what we compared against there.

What we would do

Use the official plugin where one exists. Check the configuration options against your requirements before committing, specifically the underpayment tolerance and the payment window.

Then test a partial payment and a late payment through the plugin, not through the provider’s sandbox, because the plugin is where those cases are mishandled.

If the plugin cannot expose what you need, the API is the answer, and that is a larger decision than it appears at the point of choosing a provider. Whatever the test says, the balance you actually hold belongs at a regulated crypto exchange rather than wherever scored best on one dimension.