Introduction
ChainPay is a powerful, secure, and reliable unified payment solution designed for modern enterprises and developers. It provides:
- Aggregated Payment Platform: Supports multiple web2 and web3 payment methods
- Simple API Interface: Easy-to-use RESTful APIs for seamless integration
- Diverse Payment Channels: Multiple payment options to meet various business needs
- Enterprise-grade Security: Advanced security measures to protect transactions
- Developer-friendly: Comprehensive documentation and SDK support
api host
prod: https://api.chainpays.org test: - contact us for test env
Getting Started
You must first register as a customer. Apply for an app in the backend. Get your app ID, public key, and private key.
Unified Request Header
Request Header
Parameter Name | Type | Required | Description |
---|---|---|---|
App-Id | string | yes | your appid |
Content-Type | string | yes | application/json |
🔐 Security Assurance
Signature Verification Mechanism
ChainPay adopts the industry-standard SHA256withRSA signature algorithm to ensure the authenticity and integrity of each request:
- Parameter Sorting: Sort by ASCII dictionary order
- String Concatenation: Concatenate parameters using standard format
- RSA Signature: Sign using merchant private key
- Base64 Encoding: Encode the signature result
Multi-layer Security Protection
- 🔑 Mutual Authentication: Merchant private key signature + server public key verification
- ⏰ Timestamp Verification: Prevents replay attacks
- 🎲 Random Number Mechanism: Ensures request uniqueness
- 🛡️ HTTPS Transmission: End-to-end encrypted transmission
- 📝 Request Logging: Complete operation audit logs
Fund Security
- Real-time Risk Control: Intelligent risk identification and interception
- Hierarchical Authorization: Multi-level permission management
- Fund Monitoring: 24/7 fund flow monitoring
- Compliance Assurance: Complies with regulatory requirements in various regions
🛠️ How to Integrate
Step 1: Obtain Integration Credentials
Contact our business team to obtain the following information:
- Merchant Application ID (
app-id
) - Merchant Private Key (for signing)
- Merchant Public Key (for verification)
- Server Public Key (for server signature verification)
- Test environment address
Step 2: Environment Preparation
Technical Requirements
- Server environment supporting HTTPS
- Ability to process JSON format data
- Support for RSA encryption algorithm
- Callback receiving capability