An open source crypto payment gateway gives your team the code for free. It does not give you the servers, the blockchain nodes, the wallet keys, or the conversion to fiat. Those stay with your team to run, patch, and reconcile for as long as the checkout takes payments.

EukaPay is a hosted gateway registered with FINTRAC, for a team that wants stablecoin or crypto acceptance without operating that stack. Its API creates invoices and sends the payer to a hosted payment page, and the account settles in fiat or crypto. This guide compares that route with three open source projects on licensing and registration, who runs the servers, and where the money lands.

EukaPay is a hosted gateway, so it is not one of the projects below. Each of these is software your team deploys and runs.

The project describes BTCPay Server as a self-hosted, open-source cryptocurrency payment processor that is free, with 0% fees and no third party. You can launch it on a cloud server, on your own hardware, or on an existing shared host. Payments arrive in the wallet you connect. Its Greenfield API manages stores, invoices, and users.

On GitHub, Bitcart is described as a free, open-source, self-hosted payment processor for BTC, LTC, BCH, XMR, ETH, TRX, USDT, and more. The code is released under the MIT license. Deployment is built on its Docker packaging.

On its GitHub page, SHKeeper is described as an open-source, self-hosted, non-custodial payment processor. It accepts BTC, ETH, LTC, SOL, USDT, USDC, and other assets across several networks. The documented install uses k3s and Helm on a fresh server, and the code is licensed under GPL-3.0.

All three leave the operating work with the team that deploys them. With a hosted EukaPay account, your team does not run gateway software at all.

EukaPay is registered with FINTRAC under registration number M22233887. That registration sits with the company that processes the payment, converts it, and settles fiat to your bank account.

An open source license covers something else. MIT and GPL-3.0 set the terms for using, changing, and sharing the code. They do not name anyone responsible for handling the money.

BTCPay Server's own site states that it is an open-source project, not a company. With a self-hosted gateway, the software is the processor, and software holds no registration. When a finance team, a bank, or an auditor asks who processed a payment, EukaPay gives them a registered company as the answer.

EukaPay hosts its own processing, so this work only applies to a team that picks the open source route.

An open source gateway needs a server to run on and, for most assets, a node or a connection to one. SHKeeper's documented configuration includes full-node settings for the chains it watches. Your team owns uptime and monitoring for those machines.

The operator applies every update. In September 2026, the BTCPay Server homepage carried a critical security notice telling operators to update to the latest version immediately. On a hosted EukaPay account, your team has no gateway server to patch.

The open source projects above receive cryptocurrency. Unless your team adds a separate conversion service, the business can hold crypto between the payment and its sale. EukaPay locks the exchange rate on every conversion by default, on pay-ins and on payouts.

The software is free to download, and BTCPay Server advertises 0% fees. The running work is hosting, node operation, updates, key management, and conversion, and most of it is engineering time. With EukaPay, your team does not host, patch, or run nodes for the gateway.

Refer to the websites for current information.

EukaPay's column is the one with a FINTRAC registration and no gateway server for your team to run. It is also the column that settles in USD, EUR, GBP, or CAD to your bank account. In the other two columns, BTCPay Server and SHKeeper send payments to wallets your team controls. For a team that wants a registered processor, fiat in the bank, and no gateway to patch, EukaPay is the route to take. Our guide on

how to choose a crypto payment gateway

covers the other criteria.

EukaPay's integration follows the same order an open source gateway does. Your code creates a payment request, sends the payer to a page, receives the result, and records it against the order.

With EukaPay, the payment request is an invoice created through the API. The payer completes the transfer on a hosted payment page from their own wallet, so the payer finishes in a browser. EukaPay then sends a webhook:

,

, or

, depending on the sum paid against the invoice.

Each webhook carries an

header. Your server checks it against an HMAC SHA-512 digest of the raw payload, made with your secret key. If a delivery fails, EukaPay retries every 20 minutes for up to 2 hours. Our post on how to

integrate crypto payments

covers the build order, and the

crypto payments API

guide lists the endpoints.

EukaPay's API covers invoices, subscriptions, payouts, balance transfer, and customers. A staging environment uses the same exchange rates as production and accepts testnet cryptocurrencies. The Payout API sends crypto payouts in USDC, USDT, ETH, or BTC, one payout per request. The full reference is in the

API documentation

.

One EukaPay account gives you instant crypto-to-fiat conversion at a locked exchange rate to remove your exposure to crypto price swings, support for most major cryptocurrencies like BTC, ETH, LTC, SOL, USDC, USDT, and settlement in USD, EUR, GBP, and CAD to your bank account. A crypto payment confirms on-chain, so protection against chargebacks is a property of the payment method.

For a team that wants a FINTRAC-registered processor instead of running servers, nodes, and keys, EukaPay is the recommendation. Start in staging, build the invoice and webhook flow, and move to production once verification is complete.

Create an account at

app.eukapay.com/signup

, complete verification, and provide your legal business information to generate an API key. The

API documentation

covers invoices, webhooks, and the staging environment.

Is EukaPay a regulated crypto payment gateway?

EukaPay is registered with FINTRAC under registration number M22233887.

Does an open source license make a crypto payment gateway regulated?

No. An open source license sets the terms for using and sharing the code. It does not register anyone to process payments.

Do I need to run a server to use EukaPay?

Not a gateway server. Your backend creates invoices and receives webhooks, and EukaPay hosts the payment page.

How do I know a crypto payment is complete?

EukaPay sends a

webhook when the sum of payments for the invoice matches the requested amount.

Can I receive fiat instead of crypto?

Yes. You choose fiat or crypto settlement, and fiat settles in USD, EUR, GBP, or CAD to your bank account.

Crypto payment gateway open source or hosted: which takes less engineering?

A hosted gateway usually does, because there is no gateway server or node to operate. With EukaPay, the core work is the invoice call and the webhook handler.