The Compatibility API lets an existing merchant integration keep its provider SDK and request format while switching traffic to PawPayments. In most integrations, the merchant changes only the provider base URL:Documentation Index
Fetch the complete documentation index at: https://docs.pawpayments.com/llms.txt
Use this file to discover all available pages before exploring further.
| Provider SDK | Paw base URL |
|---|---|
| Cryptomus | https://api.pawpayments.com/compat/cryptomus/v1 |
| Heleket | https://api.pawpayments.com/compat/heleket/v1 |
| NowPayments | https://api.pawpayments.com/compat/nowpayments/v1 |
api_key for request signing. Cryptomus and Heleket SDKs send the Paw merchant ID as the merchant header and sign with api_key. NowPayments SDKs continue to send x-api-key.
Webhooks
Invoices created through a compatibility route automatically use that provider’s webhook format:| Created through | Webhook format |
|---|---|
/compat/cryptomus/v1 | Cryptomus IPN body with sign in JSON |
/compat/heleket/v1 | Heleket-compatible IPN body with sign in JSON |
/compat/nowpayments/v1 | NowPayments IPN body with x-nowpayments-sig header |
| Native API | Native format by default, or the invoice-level webhook_format override |
501 NOT_SUPPORTED.