Skip to main content

Non-custodial crypto payment infrastructure

Accept crypto.Keep custody.

Accept BTC, BCH and XMR directly to your own wallet. Manatee handles blockchain monitoring, payment detection and webhooks — without ever taking custody of your funds.

Public beta · Test and mainnet credentials · No spend keys · No custody

Explore
Direct wallet settlementCustomer payments use your receiving addresses
Managed infrastructureNodes, monitoring, and delivery operated for you
API-firstDocumented REST endpoints and lifecycle states
Signed webhooksHMAC-authenticated payment events

Direct wallet settlement

Your customers pay you. Not us.

Your money never passes through Manatee. Customers pay addresses controlled by your wallet while Manatee operates the infrastructure required to detect payments, track confirmations and notify your application.

Funds
CustomerMerchant wallet

BTC, BCH or XMR moves directly between the customer and an address controlled by you.

Infrastructure
ManateeDetectionConfirmationsWebhook

Manatee observes and reports payment state. It is never in the path of the funds.

You keep custody. We keep the infrastructure running.

Payment lifecycle

From API request to verified order state.

Your order system owns customer, fulfillment, and refund decisions. Manatee reports the matching on-chain payment state.

  1. 01

    Create payment

    Your backend creates one payment for one order.

  2. 02

    Present details

    Show the address, amount, QR code, and expiry.

  3. 03

    Customer pays

    The customer broadcasts a transaction on the selected network.

  4. 04

    Detect

    Manatee matches the transaction to the payment.

  5. 05

    Track

    Confirmations advance against your configured threshold.

  6. 06

    Deliver

    Manatee sends the corresponding signed webhook event.

  7. 07

    Update order

    Your backend verifies the event and applies its policy.

Concrete delivery contract

Verify the event before changing the order.

Each delivery includes a timestamp, event ID, and HMAC-SHA256 signature. Verify the raw body, enforce a timestamp window, and process every event ID idempotently.

Read the verification guide
payment.confirmed verified
{
  "version": "1",
  "type": "payment.confirmed",
  "data": {
    "payment_id": "pay_abc123",
    "asset": "btc",
    "network": "testnet",
    "txid": "a1b2c3d4…",
    "address": "tb1q…7px4",
    "amount_sats": 84730,
    "received_sats": 84730,
    "confirmations": 3,
    "webhook_url": "https://shop.example/webhooks/btc"
  }
}

Supported assets

One API. Multiple networks. Your wallets.

Bitcoin, Bitcoin Cash and Monero are available for mainnet and test-network integrations through one consistent payment lifecycle.

Why Manatee

Crypto payments without the infrastructure burden.

Running non-custodial payment infrastructure means operating blockchain nodes, monitoring transactions, tracking confirmations, handling retries and delivering reliable payment events. Manatee handles that infrastructure while your business keeps control of the funds.

Developer friendly

A straightforward API designed for real application and commerce workflows across BTC, BCH, and XMR.

Explore the API

Direct settlement

Payments go directly from your customer to your wallet.

Wallet setup

Reliable payment events

Track payment detection and confirmations through signed webhooks.

Verify webhooks

Managed infrastructure

No blockchain nodes or payment listeners to operate yourself.

Status model

Non-custodial

Manatee never receives your private spend keys or controls your funds.

Idempotency

Predictable pricing

Pay for infrastructure—not a percentage of your sales.

Pricing

Why Manatee exists

Self-custody without another infrastructure stack.

Self-hosting gives you maximum infrastructure control. Manatee is for teams that want to keep financial custody without operating the payment infrastructure themselves. Manatee offers a different trade-off.

Manatee manages the payment infrastructure.You keep control of the funds.

Managed provider

Custodial payment provider

  • Infrastructure is operated for the merchant
  • The provider may control funds or settlement
  • Minimal infrastructure responsibility
Self-hosted

BTCPay Server

  • Full self-custody and infrastructure control
  • The merchant operates the payment stack
  • A strong fit for experienced self-hosters
Managed, non-custodial

Manatee

  • Payment infrastructure is operated for you
  • BTC, BCH, and XMR settle to merchant-controlled addresses
  • No payment server for the merchant to maintain

Self-custody without self-hosting the payment infrastructure. BTCPay Server is a strong choice when you want to operate the entire payment stack yourself. Manatee is designed for teams that want the custody benefits without maintaining that infrastructure. Read the detailed comparison.

WooCommerce

Add crypto payments to WooCommerce in minutes.

Connect your Manatee account, configure your receiving wallets and start accepting non-custodial crypto payments directly into your wallets.

  • Direct wallet settlement
  • Automatic payment status updates
  • Signed webhook verification
  • Fiat-priced products
  • Bitcoin
  • Bitcoin Cash
  • Monero

One Pay with crypto method lets customers choose BTC, BCH, or XMR. The plugin creates payment instructions, verifies signed events, and updates the WooCommerce order from confirmed Manatee state.

API integration

From API key to payment in minutes.

Create a payment, show the returned payment details to your customer and let Manatee handle blockchain monitoring and payment status updates.

1Create paymentPOST /v1/<asset>/payments
2Customer pays

Directly to your merchant-controlled wallet.

3Manatee notifies

Verify signed detected and confirmed events.

Read the API documentation

WooCommerce and API

Start with a plugin or build your own checkout.

The public beta API and published WooCommerce plugin support BTC, BCH and XMR. Shopware 6 and Magento 2 remain separate beta integrations distributed on request.

REST APIPublic beta

For custom products and checkout flows

Create BTC, BCH, or XMR payments with documented JSON endpoints, explicit lifecycle states, and signed webhook events.

WooCommercePublished plugin

For WordPress stores

Install from WordPress.org, configure Test or Live mode, and accept BTC, BCH or XMR with verified payment state attached to the order.

Shopware 6Beta

For Shopware 6.7 stores

Evaluate server-side payment creation, signed webhook handling, and Shopware transaction-state mapping before marketplace distribution.

Magento 2Beta

For Magento Open Source 2.4.8

Test checkout instructions, payment metadata, confirmation-driven invoicing, and cancellation edge cases in your store.

Use cases

Built for businesses that actually want to hold crypto.

Manatee fits server-side integrations and stores that can keep payment records, verify signed events, and apply their own fulfillment policy.

Online stores

Accept crypto without routing customer funds through a custodial payment processor.

SaaS & software

Accept crypto for licenses, credits and digital purchases through a simple payment API.

Hosting & infrastructure

Accept global crypto payments while settlement remains directly in your own wallet.

Developers

Add on-chain payments without maintaining blockchain nodes, listeners and confirmation tracking.

Security and production readiness

Evaluate the complete payment flow during beta.

Manatee is part of your payment infrastructure, but it is not your wallet. You trust the service to report payment state and deliver events—not to hold or move merchant funds.

Manatee can

  • Create payment requests through the API
  • Allocate receive addresses from configured read-only wallet information
  • Monitor matching on-chain transactions
  • Track the configured confirmation threshold
  • Deliver timestamped, HMAC-signed webhook events

Manatee cannot

  • Spend assets received by your wallet
  • Withdraw or transfer your funds
  • Access your wallet seed phrase or private spend keys
  • Issue refunds or make fulfillment decisions

Operational transparency

What happens if Manatee goes offline?

Your funds remain in your wallet.

Transactions already broadcast to BTC, BCH, or XMR remain on their respective networks independent of Manatee.

During an outage

New payment creation, transaction detection, status updates, or webhook delivery can be temporarily unavailable.

What does not change

Manatee does not gain custody of funds already received by merchant-controlled addresses.

Prepare for reconciliation

Store the payment ID, address, amount, and merchant reference with the order. After recovery, query payment state rather than assuming an interrupted checkout was unpaid.

Read the reconciliation guide

Built and operated in Germany

An independent project with a documented infrastructure boundary.

Manatee's backend is hosted in Germany. The static public website and security edge use Cloudflare's global network. BTC and BCH use public receive data; XMR uses an encrypted private view key. Manatee never needs a wallet seed phrase or private spend key.

Evaluate Manatee

A clear path from evaluation to production.

Start free during beta, simulate the full payment lifecycle without moving funds, then follow the production checklist when your integration is ready.

Pricing

€0 during beta

Billing is not active during beta. Future plans will use a predictable flat rate rather than a percentage of sales.

View pricing and limits
Interactive demo

Try BTC, BCH and XMR checkout states

Explore pending, detected, confirmed, underpaid and expired outcomes without an account or real funds.

Open checkout demo
Production readiness

Launch with explicit checks

Validate wallet isolation, webhook verification, reconciliation, monitoring and recovery before accepting real payments.

Read the production guide

Public beta

Test the complete payment flow before mainnet.

Usage is intentionally limited while integrations, infrastructure, and operational processes are validated. Configure dedicated BTC, BCH or XMR wallets and verify the complete payment and webhook lifecycle.