📄️ Introduction
Subscription payment
📄️ 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: RequestCreateOrder
Create Order is an interface provided to merchants to submit a pre-order with brief transaction information provided, such as a short code, merchant order ID, order amount, etc. In the subscription payment scenario, the mandate information should be submitted. The interface will respond with a prepayId, which is necessary to evoke the checkout page. The contract details will be shown on the checkout page when the pre-order is for a subscription payment business.
📄️ Step 3: Notify/Callback
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 3: QueryMandateDetails
Query mandate contract details by contract id in merchant system.
📄️ Step 4: CreateDisburseOrder
Query mandate contract details by contract id in merchant system.
📄️ 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.