Payment results
Event Group | Event Identification |
---|---|
appsubscription | appsubscription/paid |
When the merchant subscribe to the Product in the application , the platform will push relevant subscription payment results information to developers
Request Headers
- X-Shopline-Topic string requiredEvent operation identificationExample:
orders/edited
- X-Shopline-Hmac-Sha256 string requiredSignatureExample:
XWmrwMey6OsLMeiZKwP4FppHH3cmAiiJJAweH5Jo4bM=
- X-Shopline-Shop-Domain string requiredShop domainExample:
shophub.myshopline.com
- X-Shopline-Shop-Id string requiredShop IDExample:
1610418123456
- X-Shopline-Merchant-Id string requiredMerchant IDExample:
2000001234
- X-Shopline-API-Version string requiredVersionExample:
v20210901
- X-Shopline-Webhook-Id string requiredMessage IDExample:
b54557e48a5fbf7d70bcd043
Request Body
- appkey stringApply unique logo
- bizOrderNo stringBusiness order number
- handle stringStore unique logo
- secondChannelId stringSecondary channel id
- status integerPayment Status, with enumerated values:
- 200 - Payment Successful
- 300 - Payment Cancelled
- 400 - Payment Failed
- subId stringCreated the order number generated during the subscription
- subTime longPayment time
Response
After receiving a webhook notification from SHOPLINE, you must respond with the following format:
HTTP/1.1 200 OK
For more information about how to subscribe to webhooks and webhook response rules, refer to Webhook overview.
Was this article helpful to you?