Skip to main content

Overview

Overview​

Morph Payments is a stablecoin payment API for merchants. You create a payment resource, share a checkout URL, and receive settled funds on-chain — across multiple chains and tokens — while Morph handles the payer-facing checkout, on-chain confirmation, and event notifications.

Every request is authenticated with an API Key over a single production gateway, and every response uses one common envelope so success and errors are handled the same way everywhere.

What you can do today​

  • Collect payments — create a Payment Link (a shareable checkout URL for a fixed amount) or an Invoice (a payment link plus payer details, a due date, and optional line items). Your customer completes payment on a Hosted Checkout page.
  • Let payers choose how they pay — accept payment across the chains and tokens in the Paying currencies catalog while you settle into a receiving chain and token you control.
  • Query supported currencies — read the live Receiving and Paying currencies catalogs to drive the values you send when creating a payment.
  • Track payouts and balance — page through your payout history and read the real-time on-chain balance of your receiving wallet.
  • React to order events — receive signed webhooks for the success, failed, and expired order lifecycle, with built-in retries and idempotency.

How it works​

  1. Create a Payment Link or Invoice with the receiving chain, token, and address you want to settle into.
  2. Share the returned checkout URL. Your customer pays with any supported paying currency on the Hosted Checkout page.
  3. Confirm the payment: Morph watches the chain and finalizes the order.
  4. Get notified through a signed webhook when the order reaches success, failed, or expired.

Before you start​

  • Base URL — all API requests go to a single production gateway:
https://pay-openapi.morph.network
  • Credentials — apply for an APIKey / APISecret at account.morph.network, then configure your receiving wallets there.
  • Authentication — every request is signed with HMAC-SHA256. See Authentication for headers, the signing scheme, and code examples.
note

Business success or failure is determined by the error_code field in the response body (error_code == 0 means success), not by the HTTP status code alone. See Error Codes for the full list.

Next steps​