Grateful Merchants API

• Name: Grateful Merchants API
• URL: https://docs.exodus.com/grateful
• Category: stablecoin merchant checkout API / hosted payment-link infrastructure / WooCommerce-ready commerce middleware
• Tags: ethereum-ecosystem
• Summary: Grateful Merchants API is hosted stablecoin checkout middleware. The useful part is the merchant control plane — payment-request creation, hosted checkout URLs, deposit-address generation, webhook-confirmed status changes, and WooCommerce wiring — not a payment rail, wallet standard, or serious platform anchor.
• What it does:
  • Lets merchants create payment requests and receive a checkout URL that can be shown to customers or embedded in merchant flows
  • Exposes a base API at https://merchant.grateful.me/api secured with an x-api-key from the merchant dashboard
  • Supports payment creation, payment retrieval, payment configuration, and status-check endpoints in the documented API reference
  • Supports USDC, USDT, and DAI across several EVM networks including Arbitrum, Base, Optimism, Polygon, and BSC, with token-by-network differences documented in the overview
  • Sends webhook notifications when payment status changes so merchants can react to confirmations asynchronously
  • Offers a native WooCommerce integration for WordPress merchants who want a lower-code route to stablecoin acceptance
• Key claims:
  • The overview says the API provides a seamless way to manage payments and highlights instant payments, multiple stablecoins, multi-chain support, webhook notifications, and WooCommerce integration
  • The overview’s supported-token matrix lists USDC on Arbitrum, Base, Optimism, Polygon, and BSC; USDT on Arbitrum, Base, Polygon, and BSC; and DAI on Arbitrum, Base, Optimism, and Polygon
  • The API reference says all requests should be sent to https://merchant.grateful.me/api and authenticated with an x-api-key from the merchant dashboard
  • The same API reference documents a payment flow of create → redirect → configure → pay → confirm, which is strong evidence that Grateful is operating a hosted merchant-checkout control plane rather than a simple static invoice generator
  • The Exodus llms.txt index says POST /payments/new creates a new payment request, the configure-payment endpoint selects token and chain and generates a deposit address, and the WooCommerce integration installs a plugin so merchants can accept crypto payments in WordPress
• Whitepaper: No canonical standalone Grateful Merchants API whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the Exodus docs overview, API reference, and machine-readable docs index, while some deeper Grateful subpages were fetch-hostile during retrieval; see ../whitepapers/grateful-merchants-api-primary-sources-2026-05-04.md.
• Sources:
  • https://docs.exodus.com/grateful
  • https://docs.exodus.com/raw/grateful
  • https://docs.exodus.com/raw/grateful/api-reference
  • https://docs.exodus.com/llms.txt
  • https://docs.exodus.com/grateful/api-reference/create-payment
  • https://docs.exodus.com/grateful/api-reference/payment-status
  • https://docs.exodus.com/grateful/integrations/woocommerce

Internal linkages

• Best upward comparison points: coinflow and bridge-xyz.

Control surface

• Authority sits in supported token-and-chain policy, hosted checkout behavior, deposit-address generation, webhook reliability, and how much of the merchant flow depends on Grateful-managed status and redirect handling.

• It is merchant checkout middleware, not a base payment rail.

• Last reviewed: 2026-05-31 UTC