Required Development Parameters
Last updated: 2025-04-03 11:36:38
Before starting development in the standard merchant mode, the following development required parameters need to be prepared:
Parameter | Description |
mchid | Merchant ID (mchid) is the unique identifier for the merchant in the superapp's payment. All payment-related API calls must include this parameter for the superapp's payment to verify the merchant's identity. This ID is provided to the merchant upon successful registration. For details, see Mini Program Payment. |
serial_no | Merchant certificate serial number. |
appid | A unique identifier applied for on Super App as a Service (SAS). To use the superapp's payment, this ID must be bound to the merchant ID. Refer to the platform's merchant ID binding process for details. |
APIv3 key | The superapp's payment uses the APIv3 key to encrypt callback information. Merchants must decrypt the encrypted callback data using this key. Set up the APIv3 key before integration. |
Merchant API certificate | Used to generate request signatures with the private key when initiating APIv3 requests. |
Superapp's payment public key | Used to verify signatures on APIv3 responses and encrypt sensitive information (e.g., names, ID numbers) for transmission. |
The superapp needs to enable the following features:
1. Enable merchants to complete the onboarding process and provide them with mchid (merchant ID), serial_no (merchant certificate serial number), and merchant API certificate.
2. Provide a feature for merchants to set up the APIV3 key.
3. Allow merchants to request and get the superapp's payment public key.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback