📄️ Introduction
Mini App Integration
📄️ Step 1: ApplyFabricToken
In order to establish communication with the SuperApp API fabric, you must first get a fabric token. For this purpose, you need to apply for a fabric token using the applyFabricToken service.
📄️ Step 2:AuthToken
This is for system's that use auto Login functionality. The request for this need to originate from within the SuperApp as it requires the access_token which is generated from with the SuperApp via function call from the H5. For more information check the demo provided
📄️ Step 3: RequestCreateOrder
This API is used to create an order for the purchase of an item. It will return a prepay ID, which helps you checkout. To create an order, you must first obtain a token from the applyFabricToken method and set it in the header before you can place an order request.
📄️ Step 5: Notify
After the completion of the payment on the SuperApp, the payment notification (callback) will be sent to the end point that you passed on the createOrder request notify_url parameter in a post method. This endpoint must be whitelisted and configured on the SuperApp server in order to be sent properly.
📄️ Step 4: queryOrder
The Query Order interface can be used to query a payment in the event of an unsuccessful payment notification.
📄️ Additionally: RequestSignatureProcess
On the above requests, we are using a request signature to ensure the authenticity of the data being sent through a network. For this purpose, we require RSA key pairs to sign and verify a request body. Here is a step-by-step guide on how to do a request body signature when sending a request to the payment server.