Grateful Merchants API primary sources — 2026-05-04

Project status in this pass

• No canonical standalone Grateful Merchants API whitepaper or litepaper surfaced.
• The clearest current source of truth is the Exodus docs overview, the Grateful API reference, and the Exodus llms.txt index.
• Some deeper Grateful subpages were fetch-hostile in this pass, so several endpoint-level details rely on first-party descriptions exposed through the docs index.
• The project is best understood as merchant stablecoin checkout and notification middleware rather than as a generic wallet feature or a simple plugin.

Primary-source snapshots

1) Grateful overview page

• URL: https://docs.exodus.com/raw/grateful
• Key excerpt:
  • The overview says the API helps businesses manage crypto payments with simplicity, flexibility, and security.
  • It lists instant payments, support for USDC, USDT, and DAI, multi-chain support, webhook notifications, and native WooCommerce integration.
  • It also outlines the high-level flow: create a payment, redirect the customer, let the customer select token and chain, wait for the onchain transfer, and receive confirmation.

2) Supported-token matrix

• URL: https://docs.exodus.com/raw/grateful
• Key excerpt:
  • The matrix lists USDC on Arbitrum, Base, Optimism, Polygon, and BSC.
  • It lists USDT on Arbitrum, Base, Polygon, and BSC.
  • It lists DAI on Arbitrum, Base, Optimism, and Polygon.

3) API reference

• URL: https://docs.exodus.com/raw/grateful/api-reference
• Key excerpt:
  • The docs say all API requests should be made to https://merchant.grateful.me/api.
  • They say authentication is handled with an x-api-key header and point merchants to the dashboard for obtaining the key.
  • The reference documents endpoints for creating a payment, retrieving payment details, configuring token and chain, and checking payment status.

4) Documented payment flow

• URL: https://docs.exodus.com/raw/grateful/api-reference
• Key excerpt:
  • The flow is explicitly documented as create → redirect → configure → pay → confirm.
  • That is strong evidence that Grateful is packaging a full merchant checkout control plane rather than only a passive address generator.

5) llms.txt index — create and configure endpoints

• URL: https://docs.exodus.com/llms.txt
• Key excerpt:
  • The machine-readable index says POST /payments/new creates a new payment request.
  • It says the configure-payment endpoint selects token and chain and generates a deposit address.
  • It also says the payment-status endpoint retrieves the current status of an existing payment.

6) llms.txt index — integrations

• URL: https://docs.exodus.com/llms.txt
• Key excerpt:
  • The index says Grateful has webhook notifications for payment status changes.
  • It also says there is a WooCommerce integration that installs a plugin to accept crypto payments in a WordPress store.

Working conclusion

Grateful Merchants API is best cataloged as merchant stablecoin checkout and commerce middleware. The deciding evidence in this pass was the combination of hosted payment URLs, token-and-chain configuration, deposit-address generation, payment-status tracking, webhook delivery, and native WooCommerce distribution.