Notification

The customer can configure to receive updates at different stages of the
QR Code generation process and transaction status. There are three options for
settings:

1. After generating a QR Code.
2. After paying a deposit via QR Code.
3. Requested withdrawal status (success or failure).

Customer may provide separate webhook URLs for each event or a single
URL that receives all updates.

Configuration Example

Body example:

body

{
    "id": "ID_TRANSACTION",
    "type": "deposit OR withdraw",
    "action": "Action status",
    "partner_id": "Free string that must be sent to Pay2Free along with the URL. This ID exists so that the partner can identify which Merchant the transaction is from.”
}

---

Client URL: Url to be provided by the customer
HTTP Method: POST

Deposit:

• action > (status)

1. requested: QRCode generation

cURL

curl --location 'https://{YOUR_URL}.com/deposit' \
--header 'Content-Type: application/json' \
--data '{
          "id": "125346",
          "type": "deposit",
          "action": "requested",
          "partner_id": "4589556"
}'

2. updated: Change in QRCode (Payment Received)

cURL

curl --location 'https://{YOUR_URL}.com/deposit' \
--header 'Content-Type: application/json' \
--data '{
          "id": "125346",
          "type": "deposit",
          "action": "updated",
          "partner_id": "4589556"
}'

---

Withdraw:

• action > (status)

1. updated: Change in withdrawal status (Withdrawal made successful)

cURL

curl --location 'https://{YOUR_URL}.com/withdraw' \
--header 'Content-Type: application/json' \
--data '{
          "id": "658975",
          "type": "withdraw",
          "action": "updated",
          "partner_id": "356896"
}'

1. updated: Change in withdrawal status (Withdrawal failed)

cURL

curl --location 'https://{YOUR_URL}.com/withdraw' \
--header 'Content-Type: application/json' \
--data '{
          "id": "658975",
          "type": "withdraw",
          "action": "updated",
          "partner_id": "356896"
}'