

Gateway settings with usage, environment, protected API credentials, BTC/BCH/XMR controls, confirmations, and expiry.
Manatee adds a non-custodial crypto payment gateway to WooCommerce. Customers choose Bitcoin (BTC), Bitcoin Cash (BCH), or Monero (XMR) within one “Pay with crypto” checkout method. The plugin creates an asset-scoped payment, shows the returned address, exact amount, wallet URI, and local QR code, then updates the order from signed webhook events. Test mode combines BTC/BCH Testnet4 with XMR Stagenet, and XMR is offered only after the selected environment reports a ready view-only receive wallet.
Manatee is non-custodial. The plugin does not hold customer funds, request wallet seeds or spending keys, or run blockchain node logic inside WordPress. BTC, BCH, and XMR are available on their test networks and mainnet. The plugin receives only XMR readiness state, never an address or view key, before displaying it to customers.
The plugin is built for merchants and developers who want to accept supported on-chain crypto payments while keeping checkout, order metadata, and webhook handling inside WordPress.
fiat_amount and fiat_currency./v1/btc/payments, /v1/bch/payments, or /v1/xmr/payments route.Before accepting payments, configure the gateway in WooCommerce > Settings > Payments > Crypto via Manatee:
https://api.manatee-api.io unless Manatee support tells you otherwise.The settings header shows remaining monthly confirmed mainnet payments and active webhook monitors by network. “Save, refresh and test connection” persists changed settings before sending a read-only GET /v1/usage request.
The API key and webhook secret fields include reveal controls so an authorized WooCommerce administrator can verify the entered values before saving.
Use Test mode with one Test Manatee API key and webhook secret. That credential selects BTC/BCH Testnet4 and XMR Stagenet. Enable each asset only after configuring its receive wallet and wait until the XMR readiness check succeeds. A locally database-re-scoped Regtest credential can likewise be shared by all three assets.
When switching to Live mode, use a mainnet Manatee API key, review the webhook secret, confirm that the webhook URL is reachable from the public internet, and test a low-value payment before opening the payment method to customers.
When a customer selects BTC, BCH, or XMR, the plugin sends the WooCommerce fiat amount, currency, webhook URL, required confirmation count, expiry window, underpayment tolerance, and order reference to the corresponding Manatee API route. For XMR, the plugin first reads a minimal API-key-scoped readiness result; it does not receive a view key or wallet address from that check.
The WooCommerce order stores asset, network, Manatee payment ID, payment address, pricing metadata, environment mode, status, transaction ID, confirmations, and expiry. BTC/BCH amounts are stored in satoshis; XMR amounts are stored exactly in piconero.
Webhook events are verified with the X-Manatee-Signature, X-Manatee-Timestamp, and X-Manatee-Event-Id headers before order mutation.
This plugin connects to the Manatee Payment API to create and verify non-custodial BTC, BCH, and XMR payments for WooCommerce orders.
When a customer chooses an asset, the plugin sends the order amount, currency, webhook URL, required confirmations, expiry, tolerance, and reference to the asset-specific API route. The API returns asset, network, payment ID, address, exact atomic amount, exchange-rate metadata, expiry, and status. BTC/BCH use satoshis; XMR uses piconero.
The settings screen sends a briefly cached read-only usage request, and the merchant can refresh it with the connection-test action. When a pending order is cancelled, the plugin may send an asset-scoped cancellation request. Manatee sends signed webhook events back to update the order after detection or confirmation.
This service is provided by Manatee.
Privacy Policy: https://manatee-api.io/privacy-policy