Skip to main content
If this is your first integration, the recommended reading order is:
  1. Quickstart
  2. Merchant Access
  3. Authentication
  4. Notification
  5. The guide and API Reference for your target product flow

Merchant Onboarding and App Configuration

Base URL

All API paths in this documentation must be combined with the base URL to form the full request URL.

Create and Configure an App

Follow these steps to set up your application in the GatePay Merchant Portal:

Configuration Credentials

After completing app configuration, you will receive the following credentials: Important: Any API that uses asynchronous notifications requires a valid callback URL to be configured; otherwise, notifications cannot be delivered. For details on how to verify incoming callbacks, see Authentication and Security.

Common Request Headers

For most non-institution APIs, requests commonly use the following headers: For full header, signing, and verification details, refer to the Authentication and Security guide.

SDK Support

The latest official SDK and client repositories are maintained under the Gate GitHub organization: https://github.com/gate The currently public multi-language SDK / client resources include: Use the Gate GitHub organization page as the source of truth for the latest repository list. If a specific flow does not yet have a ready-made SDK wrapper, you can still integrate directly through the REST APIs documented here.

Supported Payment Networks and Currencies

Blockchain Networks and Supported Cryptocurrencies

The following networks and tokens are supported for address-based payments:

Supported Currencies for Other Payment Channels

The following cryptocurrencies and digital assets are supported across other payment methods: BTC, USDT, USD, GT, ETH, EOS, DOGE, DOT, SHIB, LTC, ADA, BCH, FIL, ZEC, BNB, UNI, XRP, STEPG, SUPE, LION, FROG

Next Steps

  • If you want to run the first end-to-end flow quickly, start with Quickstart
  • For authentication details and request signing, see Authentication and Security
  • For payment API integration, refer to your specific payment flow documentation
  • For error handling and best practices, consult the error codes and troubleshooting guide