Skip to main content
Gcashier Pay gives your business a single integration point for the full cross-border payment lifecycle — from merchant onboarding and virtual account collection to FX trading, international remittance, and withdrawals. Every request is encrypted end-to-end using AES and RSA, and all asynchronous events are delivered via webhook callbacks to your platform.

Quickstart

Make your first API call in minutes — set up keys, encrypt a request, and verify the response.

Authentication

Learn how RSA keys and AES session encryption work together to secure every API call.

API Reference

Full reference for all 40+ endpoints across merchant access, collection, FX, payments, and accounting.

Guides

Step-by-step walkthroughs for onboarding, collection, currency exchange, and international transfers.

What You Can Build

Collections

Open virtual accounts and receive payments from customers worldwide.

FX & Exchange

Get real-time quotes and execute currency conversions programmatically.

International Transfers

Send cross-border remittances to beneficiaries in supported countries.

RMB Payments

Initiate domestic CNY payments to Chinese bank accounts.

Payouts

Withdraw settled funds to your linked bank account.

Accounting

Query account balances and full transaction history in real time.

How It Works

1

Onboard your merchant account

Submit your merchant KYC details via sp1101. Gcashier Pay reviews your application and activates your account.
2

Exchange RSA public keys

Generate a 2048-bit RSA key pair, share your public key with Gcashier Pay, and receive Gcashier Pay’s public key in return. These keys secure every API message.
3

Integrate and test

Use the sandbox environment to test your integration with mock endpoints. Validate encryption, signing, and webhook delivery.
4

Go live

Provide your production server IP, exchange production RSA keys, and switch your base URL to the production environment.
All API requests use HTTPS 1.2 with JSON payloads. Messages are AES-encrypted and RSA-signed — see Encryption & Signing for the full specification.