Plisio vs Apa: Custodial Gateway vs Non-Custodial Checkout

Plisio is a hosted crypto payment gateway. A customer pays in one of the supported cryptocurrencies, and Plisio credits that payment automatically to your Plisio account. From there you withdraw to an external wallet or use Plisio's mass-payout feature to send crypto out. The model is familiar to anyone who has used a traditional processor: money lands in a platform account first, and you move it from there.

Apa is a non-custodial checkout. A customer pays on-chain and the funds settle directly to a wallet you already control — there is no Plisio-style account balance in the middle. Apa is the rail between customer and wallet, not a place funds accumulate, so there is no 'withdraw from platform' step at all.

The defining contrast is custody. Plisio holds your proceeds until you withdraw them; Apa never holds them. Everything else in this comparison follows from that.

Plisio is explicitly custodial for its gateway product. Customer payments are credited to your Plisio account balance, and Plisio describes its security posture in custodial terms — stating that around 90% of funds are stored in cold wallets, with the remainder in hot storage for operational needs. That cold-storage practice is a reasonable custodial security measure, but the key fact is that Plisio holds the funds: between the customer paying and you withdrawing, your money sits in Plisio's custody.

Plisio does also offer a separate non-custodial wallet product that is free to use, but the payment gateway itself — the merchant acceptance flow — runs through the custodial balance model.

Apa is non-custodial by design. Funds settle directly to your own wallet and Apa never holds a balance. There is no cold-wallet-versus-hot-wallet question because Apa is never holding your proceeds in the first place. For merchants who want to eliminate platform custody risk entirely, that is the central structural difference between the two.

Plisio has solid multi-chain coverage: 19 cryptocurrencies across 12 blockchains, per its documentation as of early 2026. The native coins include Bitcoin, Ethereum, Ethereum Classic, Tron, Litecoin, Dash, Dogecoin, Zcash, Bitcoin Cash, Monero, and BNB Smart Chain. On the stablecoin and token side it supports USDT, USDC, TUSD, and SHIB as ERC-20 on Ethereum; USDT and BUSD as BEP-20 on BNB Smart Chain; and USDT and BTT as TRC-20 on Tron. That is a broad menu, notably including privacy coins like Monero and Zcash that many gateways avoid.

Settlement, however, is custodial and crypto-only. Payments are credited to your Plisio balance, and there is no built-in fiat or bank-transfer settlement — you withdraw crypto, or push crypto out via mass payouts. If you want fiat, you handle that off-platform.

Apa supports nine assets — BTC, ETH, SOL, USDC, USDT, POL, BNB, AVAX, and TRX — across roughly ten chains including Bitcoin, Ethereum, Solana, Base, Polygon, BNB Chain, Avalanche, and Tron. Crucially, Apa's settlement is non-custodial and on-chain: the payment lands directly in your wallet in the asset and chain you chose, with no balance to withdraw from. Plisio casts a wider net of coins; Apa delivers directly to your wallet without holding anything.

Plisio's pricing is tiered and clearly published. Its Gateway/API plan charges 0.5% per transaction — a genuinely low headline rate. Its White Label plan, which removes Plisio branding and allows custom invoice design, charges 1.5% per transaction. Its standalone non-custodial wallet product is free. So the representative merchant number, for the standard hosted gateway, is 0.5% as of early 2026.

That 0.5% is one of the lowest headline rates in the space and sits well under the roughly 2.9%-plus-fixed fee of card networks. The trade-off for that low rate is the custodial model described above: your funds route through Plisio's balance.

Apa charges a flat 1.5% that is final and all-in, dropping to 0% for direct same-asset settlements, and delivers it non-custodially. Here the all-in framing changes the picture: Plisio's 0.5% is a headline rate, not the full cost of getting money into your own wallet. Because Plisio credits payments to your custodial balance first, actually consolidating those funds to a single external wallet adds an on-chain network fee (and any relevant conversion) on top of the 0.5% — a step Apa does not have because it settles straight to your wallet in one on-chain transaction with no withdrawal fee. So the fair comparison is not 0.5% versus 1.5% in isolation; it is Plisio's headline-plus-withdrawal-plus-custody against Apa's single all-in 1.5% (0% direct) with the funds never leaving your control.

With Plisio, proceeds accumulate as crypto in your platform balance. You then withdraw to your own wallet, or use Plisio's mass-payout feature to send crypto to many recipients at once — a genuinely useful tool for payroll, affiliate payouts, or supplier settlement. What Plisio does not offer is built-in fiat conversion or bank settlement; the payout world is crypto, and volatility management is on you unless you accept a stablecoin like USDT or USDC directly.

Apa approaches payout differently by decoupling pay-in from payout. A customer can pay in BTC while you receive USDC on the chain you choose, so you get stablecoin settlement directly, on-chain, without a platform balance in between. You nominate your payout asset and chain once and every payment arrives that way.

Both let you land in a stablecoin if you want to avoid volatility. The difference is the path: Plisio credits the stablecoin to your custodial balance to be withdrawn later, while Apa settles it straight to your wallet as the payment confirms.

Both products inherit the finality of on-chain crypto. Payments confirmed on-chain are irreversible, so there are no chargebacks in the card-network sense — a customer cannot claw back a settled crypto payment through a dispute. This is one of the core reasons merchants adopt crypto acceptance in the first place, and it applies to Plisio and Apa alike.

Plisio's documentation does not call out chargebacks as a distinct marketed feature, but the underlying property holds: on-chain payments credited to your balance are final. Apa states it plainly — confirmed on-chain payments are final and there are no chargebacks.

The subtle difference sits with custody rather than finality. With Apa, finality means the money is irreversibly in your wallet. With Plisio, finality means the money is irreversibly credited to your Plisio balance — final, but still one withdrawal step away from being under your sole control.

Plisio has a mature integration surface aimed at e-commerce. It offers hosted crypto invoices, a developer API, payment buttons for donations or simple payments, a White Label option for custom and unbranded invoices, and a wide set of ready-made plugins for popular CMS and e-commerce platforms. For a merchant on WooCommerce, OpenCart, or similar, Plisio's plugin library makes setup straightforward, and its mass-payout API is a differentiator for businesses that need to send crypto as well as receive it.

Apa's integration set covers the core jobs: a hosted checkout, shareable payment links, and a developer API with webhooks. It is focused on getting payments in cleanly rather than offering a large plugin catalog.

The decisive difference is deployment. Plisio is a hosted gateway with no published self-hosted or open-source option — you run on Plisio's platform. Apa is self-hostable, so a team that wants to run the checkout inside its own infrastructure, for control or data residency, can do so. If self-hosting matters to you, Plisio cannot provide it and Apa can.

Plisio is a strong fit for merchants who prioritize a very low headline fee, want the widest possible coin menu — including privacy coins like Monero and Zcash — and value features like mass payouts and a deep library of e-commerce plugins. If you are comfortable with a custodial balance model in exchange for 0.5% on the API plan and easy plugin-based setup, Plisio delivers a lot for the price.

Apa is the better fit for merchants who want to eliminate custody risk entirely: non-custodial settlement straight to their wallet, no platform balance to withdraw from, pay-in decoupled from payout so a customer can pay one asset while they receive another, and the option to self-host. Apa trades Plisio's longer coin list for a tighter, non-custodial model on the most-used chains and assets.

In short: choose Plisio if you want the lowest headline fee, the broadest coin support, and custodial convenience with mass payouts; choose Apa if you want non-custodial, on-chain settlement to your own wallet and the ability to self-host.

Getting started with Apa is quick precisely because there is no custodial account to fund and no balance to reconcile. You connect the wallet you want to receive into and choose your default payout asset and chain — for example USDC on Base for stable, on-chain settlement, or BTC on Bitcoin if you prefer to stay in Bitcoin.

From there you choose how to collect: a hosted checkout for your storefront, shareable payment links for one-off or social sales, or the API with webhooks for a custom flow. Because pay-in is decoupled from payout, customers can pay in any of Apa's nine assets while you consistently receive the single asset you nominated — no withdrawal step, because the funds were never held by Apa.

And because Apa is self-hostable, teams that want full control can run it inside their own infrastructure rather than depending on a hosted gateway. Whether hosted or self-hosted, every payment settles on-chain, directly to your wallet, with no chargebacks and no platform balance in between.