Notification Config

Subscribe to a payment result event.

POST /v3/b2b/notification/config

Sample

curl --location --request POST 'https://test2-business-cgi.pingpongx.com/v3/b2b/notification/config' \
--header 'Content-Type: application/json' \
--header 'timestamp: 1637564397860' \
--header 'sign: 4a70672b69b59d24d1ef05b716b1fc1d89e3e87e2b4921cb5847b6230e91c472' \
--header 'app_id: 80242303107221' \
--data-raw '{
    "event_type":"ORDER_STATUS_CHANGED",
    "hook":"http://www.pingpongx.com/callback",
    "app_id":"7520b823877841ac910e7af90d93eb99"
}'

Request Schema

Parameter Type Requried Description
event_type String M Currently there are many types of events that you can subscribe to. ORDER_STATUS_CHANGED,INBOUND_STATUS_CHANGED, RECIPIENT_STATUS_CHANGED
hook string M Specifies the callback address for receiving PingPong payment notifications
app_id string M Provided by PingPong

Response

{
    "code": 0,
    "message": "OK",
    "data": {
        "encrypt_key": "16e9a9360a25465f987e70efef1c8f27",
        "event_name": "ORDER_STATUS_CHANGED",
        "event_type": "ORDER_STATUS_CHANGED",
        "hook": "http://www.pingpongx.com/callback",
        "resource_type": "JSON"
    }
}

Response Schema

Parameter Type Requried Description
encrypt_key string Yes Decryption key of callback information
event_name string Yes Description of the event
event_type string Yes The event that you subscribe to
hook string Yes The address that you set for callback
resource_type string Yes The format of the callback information
Copyright © pingpongx.com 2021 all right reserved,powered by Gitbooklast modified: 2022-07-05 10:08:46

results matching ""

    No results matching ""