Manatee Documentation
Use these docs to test Manatee without direct support. Start with a testnet API key, create a payment, receive signed webhook events, and move to mainnet only after your checkout flow is verified.
Start here
| Goal | Read this |
|---|---|
| Create your first test payment | Quickstart |
| Understand API keys and endpoints | API and authentication |
| Look up exact OpenAPI schemas | API Reference |
| Test before going live | Testing and live mode |
| Process webhook events safely | Webhooks |
| Verify signatures and prevent replay | Security |
| Map payment state to orders | Status model |
| Prepare a WooCommerce store | WooCommerce setup |
| Prepare for Shopware | Shopware setup |
Developer path
- Create a beta account and get a testnet API key.
- Read API and authentication.
- Follow the Quickstart to create a test payment.
- Send a test webhook to your endpoint.
- Verify webhook signatures using the Security guide.
- Handle payment statuses in your own order system.
- Use the generated API Reference for exact request fields, response schemas, and error codes.
Store owner path
If you are evaluating Manatee for an online store, start with the integration overview:
Manatee is non-custodial. Customer payments go directly to wallet addresses you control. Manatee monitors payment status and sends signed events; it does not hold funds, provide a wallet, custody fiat balances, exchange funds, or send refunds.
Troubleshooting
| Problem | Where to look |
|---|---|
| Invalid API key | API and authentication |
| Webhook failed | Webhooks |
| Payment expired | Status model |
| Underpayment | Status model |
| Overpayment | Status model |
| Missing confirmations | Status model |
| Plugin cannot connect | WooCommerce setup |
OpenAPI reference
The generated OpenAPI documentation remains available at API Reference. Use it whenever you need exact endpoint paths, request and response fields, enum values, error responses, or schema details.