Apa vs BTCPay Server
BTCPay Server is a self-hosted, open-source, Bitcoin-focused payment server — you run it and own every part of the stack. Apa is a hosted, non-custodial, multi-chain checkout with built-in routing and stablecoin settlement, with nothing for you to operate.
Where they differ
Both keep custody with the merchant. BTCPay does it by having you run the server and focus on Bitcoin; Apa does it as a hosted multi-chain service.
Non-custodial and hosted. Funds settle to your wallet; Apa holds nothing.
Non-custodial and self-hosted. Funds settle to a wallet you control on your own server.
0% direct, 1.5% routed. No fee to run anything.
No software fee; you bear your own hosting and on-chain costs.
Apa's built-in routing across assets and chains.
Bitcoin-focused, with Lightning and some altcoin plugins; not a cross-chain router.
Any supported pay asset settles to your chosen receive asset, e.g. USDC.
Primarily BTC and Lightning; assets depend on installed plugins.
Fully hosted checkout and payment links, nothing to deploy.
Checkout you host and brand yourself on your own instance.
REST API, sessions and webhooks, managed for you.
Full Greenfield API on a server you operate and maintain.
Not self-hosted; Apa runs it.
Self-hosted and open source — you run and maintain the server.
Comparison reflects how each product is positioned and may change as either evolves. Verify current details with the BTCPay Server project directly.
Multi-chain checkout, nothing to self-host
Create your first payment link or API checkout in minutes. Direct payments are free, routed conversions are flat, and Apa never holds your funds.