Services
Page
ENStart a conversation
Services
Page
Lazy Ants · Web3 · Payments

Crypto Payment Gateway DevelopmentYour own crypto payment gateway, live in 30 days, developed for your product.

For fintechs, PSPs, exchanges and operators that need a payment product of their own instead of a connection to someone else's. Deployed in 30 days from the platform our team has run in production for five years, on your infrastructure or ours, then developed for your checkout, your merchants and your rules. A demo and a technical call first, free.
Your gateway · configured forNorthwind, an iGaming operator
pay.northwind.io
Northwind PayDeposit
Deposit100.00 USDT
TronEthereumPolygon
Pay 100.00 USDT
Fee
0.8% per deposit
Settlement
Hourly · USDT
Custody
Custodial
Runs on
Their cloud

Illustration · the same gateway, three clients

The gateway you would own is the one our team has run for five years.

Every deployment starts from the production platform behind CPAY, built and operated by our team, with real merchants and real money since before most gateway studios existed. You do not pay for the year of development that is already done. The numbers below are what that record looks like.

5+ years
In production under on-chain finality
50+ merchants
Onboarded on the platform
4M+
Transactions processed
CPAY.

Crypto payment and wallet infrastructure, built and operated by our team

CheckoutAPIPayoutsAdmin
Live system · real merchants, real users
Case study

CPAY: the payment platform your gateway is deployed from

  • Merchants integrate checkout and charge flows through the API; payments, refunds and internal transfers run in one system
  • Payment flows were designed so that no completed payment needs a manual correction
  • No emergency intervention in a completed payment has been needed since launch
Read the case study
Running in production today
  • Hosted checkout and API
  • Payouts and mass payouts
  • Recurring billing and subscriptions
  • 8 networks live
Running in production today
  • Hosted checkout and API
  • Payouts and mass payouts
  • Recurring billing and subscriptions
  • 8 networks live
What you get in 30 days

One gateway, seven parts. Six on day 30, the seventh when you need it.

The deployment is a product your team runs from day one. The numbered parts are layers of the same system, from the infrastructure up to your merchants' screens. Integration into the product you already run is the only optional one, scoped after the call.

7
Your existing productOptional · scoped after the call
2
Merchant dashboard
3
Checkout
120.00 USDT
4
Wallets
5
API and webhooks
POST /paymentspayment.confirmedpayout.sent
6
Administration panel
1
Infrastructure setupYour cloud or ours · nodes · signing · monitoring · backups

One system, seven layers · the numbers match the list

  1. 1
    Infrastructure setupYour cloud or ours: nodes, signing, monitoring, backups, access control. The base everything else runs on.
  2. 2
    Merchant dashboardPayments, payouts, refunds and exports for every merchant you onboard, under your brand.
  3. 3
    CheckoutA hosted payment page under your domain, or your own built on the API. The customer pays in the asset and network they choose.
  4. 4
    WalletsMerchant and treasury wallets with roles and limits, custodial or non-custodial, with conversion into your treasury asset by rule.
  5. 5
    API and webhooksThe API your product and plugins talk to, and signed webhooks for every state change, with retries, so an order never waits on a person.
  6. 6
    Administration panelMerchants, fees, limits, assets and networks, set by your team. You decide what you charge.
  7. 7
    Integration into your existing productOptionalThe gateway inside the product you already run: deposits credited to balances, orders marked paid, your records. Scoped after the call as development.
Three ways to take it

Three ways to take it

The difference is where the line falls between what you run and what we run.

SaaS

Fastest to launch

Brand and UX
Gateway app
Hosting
Chain nodes

SDK

Maximum control

Brand and UX
Gateway app
Hosting
Chain nodes

On-premise

Everything yours

Brand and UX
Gateway app
Hosting
Chain nodes
You run itWe run it
Developed for your vertical

The deployment is the same. What we develop on top of it depends on who you are.

Six kinds of business take this gateway. Each gets the parts its product needs after day 30, priced fixed per phase, with acceptance criteria.

Payments

PSP or payment provider

Crypto as one more rail for the merchants you already have: onboarding with your KYB steps, fee tiers, settlement to your ledger.

Merchant onboardingFee tiersSettlement
Trading

Exchange or fintech

Deposits credited to the user's balance, withdrawals through the same rails, limits per tier and approval above them.

BalancesLimits per tierFiat hand-off
Operators

iGaming or betting

A deposit page inside the product, bonus and limit rules applied at deposit, affiliate payouts in bulk, refunds with approval.

Deposit pageBonus rulesAffiliate payouts
Platforms

Marketplace

Buyers pay, sellers get paid out from one balance, with an approval step on your side and one report finance can file.

Seller payoutsEscrow by ruleReconciliation
Banking

Neobank or wallet app

Crypto in and out of the account your users already have, with address screening and the data your reporting needs built in.

Account railsScreeningReporting
Resellers

SaaS or payment reseller

Sell crypto payments to your own customers from a reseller admin, with your margin on every merchant and your name on every screen.

Reseller adminYour marginYour brand

A demo, one call, thirty days, then your product

The first payment lands in staging before anything goes live. Both teams see what the gateway really is before it is accepted, and the development after day 30 is priced phase by phase.

  1. Demo and technical call

    Free. You see the platform working; we look at what your gateway must do on day 30, where it runs, who holds the money and what comes after. You leave with the deployment plan and a fixed price.

  2. Deployment · 30 days

    Brand and domain, networks, merchants, the admin in your team's hands. The first payment is accepted in staging against criteria both sides signed; then it goes live.

  3. Development · by phase

    The vertical work from block 04: onboarding flows, ledgers, limits, payouts, the integrations your product needs. Each phase fixed, with acceptance criteria.

  4. Run

    Monitoring, the runbook and the people who answer when a network looks wrong. Support of the custom part under an SLA, on a subscription.

What it costs

Crypto Payment Gateway Development

30 daysDeployment · fixed after the call
Per phaseDevelopment · acceptance criteria

What moves the price

  • Your infrastructure, or ours as SaaS
  • Networks switched on
  • Hosted checkout, your own, or both
  • How much of the vertical work after day 30
Want the brand without owning it? White Label Gateway

What it costs

Crypto Payment Gateway Development

30 daysDeployment · fixed after the call
Per phaseDevelopment · acceptance criteria

What moves the price

  • Your infrastructure, or ours as SaaS
  • Networks switched on
  • Hosted checkout, your own, or both
  • How much of the vertical work after day 30
Want the brand without owning it? White Label Gateway
Scope

Networks, rails and custody. Where our part ends.

Scope is measured in networks, rails and custody modes. Where the gateway runs and who holds the money are decided on the call, because moving either later is a project of its own.

Where it runs

Your infrastructure

The gateway deployed in your environment: your cloud, your keys, your access control. We deploy it, hand over the admin and the runbook, and support the custom part.

Where it runs

Ours, as SaaS

The same platform on infrastructure our team operates, with your admin, your fees and your merchants. The fastest route in, and the one to choose if you do not want to run servers.

Custody

Custodial

Payments settle into accounts the gateway operates; merchants withdraw when they want. Simplest to run, and usually a licence question for you.

Custody

Non-custodial

Payments settle to wallets whose keys you or your merchants hold. Nobody else can move the money, and recovery is a design you get right before launch.

Where our part ends

We do not hold a licence or decide your legal status.Your lawyers decide what you may offer and where. We build the gateway so it enforces that, and we say on the call where the line is in your market.
Your merchants' KYC and KYB decisions are yours.The gateway collects, routes and enforces; the decision to onboard a merchant stays with your team.
We prepare systems for audit. We are not an audit firm.A third-party security audit is a separate engagement, never included in the deployment price.
We do not replace your bank.Converting crypto to fiat goes through your own exchange or banking partner; the gateway connects the settlement to it.
Networks are a decision, not a default.Every extra network is another way to pay on the wrong one. We switch on the ones your merchants' customers use.

Crypto payment gateway questions, answered

What product and payment teams ask before building a gateway. If yours is not here, ask on the call.

What is crypto payment gateway development?
Building a payment product of your own: the checkout and API your merchants integrate, the admin where you set fees and limits, the rails that confirm payments on each network, conversion, reconciliation, webhooks, and the runbook for the day a network stalls. We do it by deploying the platform our team has run for five years and then developing it for your product, instead of writing a gateway from scratch.
Why 30 days, when studios quote a year?
Because the year has already happened. The platform exists, runs in production with real merchants and has settled over four million transactions. The thirty days go on your brand, your networks, your merchants and the first payment in staging. What a studio would build from scratch, you deploy; what makes the gateway yours in the details comes after, phase by phase.
What do I own after day 30?
It depends on how you take it. Deployed on your infrastructure, you own the running gateway: the platform, its admin, the keys and the access to your environment, with the runbook to operate it. Deployed as SaaS on ours, you own the gateway as a product: your admin, your merchants, your fees and your data, with our team operating the servers. We settle which on the call, because moving between them later is a project of its own.
White label or my own gateway?
The white label is the same platform under your brand, run by our team, for a setup fee, a monthly fee and 0.1% per transaction. Choose it if you want to sell crypto payments without owning a payment product. Choose your own gateway if the gateway is your product: you want it on your infrastructure, developed for your vertical, with no percentage going to us. We will tell you which one fits before you sign anything.
Which coins and networks are supported?
The major coins and stablecoins on eight networks today, with new assets added on request. Which networks you switch on is a decision: every extra network is another way for a customer to pay on the wrong one. We go through the list, with fees per network, on the call.
Who holds the money?
Your choice. Custodial: payments settle into accounts the gateway operates and merchants withdraw when they want, which is usually a licence question for you. Non-custodial: payments settle to wallets whose keys you or your merchants hold. Both are supported; we settle it on the call.
What happens when a network stalls?
The runbook decides before anyone is paged: the pay page stops offering the slow network, merchants are told, pending payments keep their reference and are confirmed when the chain catches up, and the gateway returns the network to the list when it is healthy again. You see every step in the admin. Degraded mode is part of the deployment, never an add-on.
What does it cost?
The deployment is a fixed price, agreed after the demo and the call, for the thirty days. The development after day 30 is priced phase by phase, each with acceptance criteria. There is no percentage of your payments going to us. Running the gateway on our infrastructure as SaaS carries a subscription; running it on yours carries support of the custom part under an SLA.
Do you handle compliance?
We build what your lawyers decide. Address screening, limits per tier, approval steps, jurisdiction rules and the data your reporting needs are built into the gateway; the licence, the legal status and the decision to onboard a merchant stay with you.
How long does the development after day 30 take?
It depends on how much of your product the gateway has to become part of, so we do not quote a number before the call. What we do promise: the thirty days hold for the deployment, each development phase comes with its own dates and acceptance criteria, and the gateway is live and taking payments while the phases run.

Tell us what your gateway must do

Who your merchants or users are, where the money should land, and whether it runs on your infrastructure or ours. If the white label is the better fit, we will say so on the first call.

Crypto Payment Gateway Development Company · Live in 30 Days