Development Guide
Purpose
This guide provides technical implementation details for merchants integrating Trusty Pay payment solutions, including Native Payment (QR Code Payment) and App Payment (Merchant App Embedded Payment). It is tailored for R&D engineers (Android/iOS/Backend) responsible for payment integration, covering full-link processes from order creation to payment result verification.
Scope
1. Supported Payment Modes: Native Payment (merchant-generated QR code), App Payment (jump to Trusty Pay App)
2. Supported Platforms: Android (Kotlin/Java), iOS (Swift/Objective-C), Backend (unified for all languages)
3. Core Dependencies: Trusty Pay Unified Order API, Query Order API, Callback Notification Mechanism
Pre-Integration Checklist
Before development, ensure the following prerequisites are met:
| Check Item | Requirement |
|---|---|
| Merchant Account | Completed Trusty Pay merchant registration and real-name authentication. |
| Technical Credentials | Obtained Merchant ID (mch_id), API Key (api_key) from Trusty Merchant Background. |
| Environment Preparation | Distinguished production/UAT environments (API addresses and URL schemes differ) |
| Permission Configuration | Android/iOS App has relevant permissions (e.g., URL scheme registration, App jump permission). |
| Network Requirements | Backend server can access Trusty Pay API gateway (whitelist configuration if needed). |
Core Concepts & Glossary
| Check Item | Requirement |
|---|---|
| Unified Order API | Core interface for initiating payment requests, returns appUrl (jump link/QR code source URL) after successful call. |
| Query Order API | Interface for polling order status (used when callback notification is not received). |
| appUrl | Trusty Pay-generated jump link, valid for 30 minutes (configurable via API parameter). |
| notifyUrl | Merchant-provided callback address for receiving asynchronous payment result notifications. |
| frontUrl | Return address after payment completion (for In-App Payment, used to jump back to merchant App). |
| mch_id | Unique merchant identifier, obtained from Trusty Merchant Background. |
| api_key | Merchant API signature key, used for request/response signature verification (kept confidential). |
| URL Scheme | Protocol for App jump (production: jl-app; UAT: jl-app-uat). |