The operational layer between crypto and your business.
Accept crypto payments, track every transaction and move funds — through one platform and one API.
1% per transaction · no setup fee · 7 coins across 4 networks
- 14:22Northwind Supply · Order #104281,250.00 USDTFinished
- 13:04Hollis & Grey · Invoice INV-22910.00412 BTCFinished
- 12:51Payment link · Annual plan0.0261 ETHConfirming
- 11:38POS · Counter 2300.00 USDCFinished
- 10:02Checkout · Order #1041942.00 TONWaiting
- 09:15Checkout · Order #1041188.00 LTCExpired
MPC custody
No single private key
Policy-controlled payouts
Allowlists and approvals
Signed webhooks
HMAC-SHA256 on every event
Role-based access
Per-area team permissions
One payment, end to end
No manual reconciliation, no watching a block explorer. Every step is visible to you while it happens.
- Customer$1,250.00
Checks out on your site, link or terminal
- Address issuedUSDT · Tron
A fresh address, held in MPC custody
- On-chain1,250 USDT
Transfer detected the moment it lands
- Confirmedpayment.updated
Signed webhook delivered to your backend
- Your balance+$1,250.00
Credited, reconciled and ready to pay out
Take a payment anywhere you sell
One payment engine behind your checkout, links, invoices, subscriptions, donation pages and an in-person terminal. All no-code to launch.
7 coins across 4 networks
Priced live in your base currency.
Stablecoins
USDT and USDC on the networks your customers use.
Bitcoin and its family
BTC, Litecoin and Dogecoin on their own chains.
Ethereum and EVM
ETH, BNB, POL and ERC-20 tokens.
Everything else
Solana, TON, Tron, XRP, Cardano, Polkadot, NEAR.
Every transaction in one ledger
Partial and late payments are recorded individually, so the numbers reconcile.
- Live balances per coin
- Every payment with its on-chain hash
- Reports in Excel, CSV or PDF
- Team access with per-area permissions
| Date | Payment | Amount | Value | Status |
|---|---|---|---|---|
| 10 Aug 14:22 | pay_8f2c14 | $1,250.00 | Finished | |
| 10 Aug 13:04 | pay_7b1990 | $480.00 | Finished | |
| 10 Aug 12:51 | pay_6a0473 | $96.40 | Confirming | |
| 10 Aug 11:38 | pay_5c2210 | $300.00 | Finished | |
| 10 Aug 09:15 | pay_4d8801 | $— | Expired |
Move funds under a policy,
not a password
Every outgoing transfer passes a policy engine before it is signed. A stolen password moves nothing.
- Requested14:22 · by finance@northwind.co
- Policy checkDestination on allowlist
- Approval1 of 2 signers · awaiting second
- BroadcastSigned and sent on-chain
One API for payments, balances and events
Bearer auth, JSON over HTTPS, predictable errors. Create a payment in one request; the webhook tells you when it is done. Base URL https://kaskade.com/api/v1
Create a payment
curl -X POST https://kaskade.com/api/v1/payments \
-H "Authorization: Bearer ks_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"priceUsd": 250,
"payCurrency": "usdttrc20",
"orderId": "ORDER-10428"
}'Verify the webhook
import crypto from "crypto";
app.post("/webhooks/kaskade", (req, res) => {
const signature = req.headers["x-kaskade-signature"];
const expected = crypto
.createHmac("sha256", process.env.KASKADE_WEBHOOK_SECRET)
.update(req.rawBody) // the exact bytes we sent
.digest("hex");
if (signature !== expected) return res.status(401).end();
const { payment } = JSON.parse(req.rawBody);
if (payment.status === "finished") {
// fulfil the order
}
res.status(200).end();
});| POST | /payments | Create a payment |
| GET | /payments | List your payments |
| GET | /payments/:id | Retrieve a payment (live status) |
| GET | /currencies | Coins you can accept |
| GET | /rates/estimate | Live conversion estimate |
Keys are issued per merchant and can be rotated at any time. Requests may also be HMAC-signed end to end when you need it.
Security controls are part of the payment architecture, not an afterthought
The controls, stated precisely enough to audit.
MPC custody
Payment addresses are generated inside multi-party computation custody. The private key is never assembled in one place — including on our servers.
Policy-governed withdrawals
Funds move in freely. They only leave through a policy engine: allowlisted destinations, amount thresholds, multi-signer approval.
Signed webhooks
Every event carries an HMAC-SHA256 signature over the raw body in x-kaskade-signature. Verify it before you trust a confirmation.
Encrypted at rest
Service credentials and API secrets are sealed with AES-256-GCM under a key held only in the server environment.
Role-based access
Invite finance, support and engineering with per-area permissions. Nobody gets more of the account than their job needs.
Isolated balances
Each merchant's funds and reporting are tracked separately, never pooled into one undifferentiated float.
Plus the network fee, which is charged to the customer — not deducted from what you receive. No setup fee, no monthly fee, no minimum.
- Every payment tool included — checkout, links, invoices, POS, subscriptions, donations
- 7 coins across 4 networks
- Full REST API, signed webhooks and per-merchant API keys
- Reporting and exports
- Team members with role-based permissions
Why Kaskade exists
Accepting crypto isn't the difficult part. Operating it is.
Kaskade connects on-chain payments to the controls a business actually needs: reconciliation, reporting, custody, governed payouts and developer infrastructure.
Kaskade Payment Solution Inc.
Torre Advanced Building, 1st FloorCalle Ricardo Arias, Bella VistaPanama City, Postal Code 08230Republic of PanamaQuestions we get asked
How do merchants receive their money?
Payments settle in the coin the customer paid, credited to your balance and tracked per merchant. Funds leave only through the withdrawal policy — allowlisted destinations and signer approval.
Which coins can customers pay with?
7 coins across 4 networks, including USDT and USDC on Tron, Ethereum and Solana. You decide which of them your checkout offers.
How long does a payment take to confirm?
As long as the network does. We detect the transfer the moment it appears on-chain, mark the payment confirming, and send a signed webhook when it reaches final confirmation.
What happens if a customer underpays or pays late?
Every deposit against a payment is recorded separately, so partial and late payments are visible and reconcilable rather than silently lost.



