Demonstration¶
In this demo, we'll set the Callback URL and the Payment Endpoint, and then retrieve both the callback and webhook JSON responses.
Setting Up the Demo¶
- Set the Callback URL to https://google.com
- Set the Payment Endpoint to a test Webhook provider
Important Note¶
- Make sure to relog on all devices after changing these attributes
Demonstration Video¶
Callback URL Response¶
After setting up the Callback URL, you'll receive a response like this: https://your-callback-url.com?pay_id=12345&user_id=abcdefg&status=success
Webhook JSON Response¶
The Payment Endpoint will receive a webhook with a JSON response similar to this:
json {
"ResponseCode": 1,
"data[pay_id]": 1466,
"data[amount]": 100,
"data[user_id]": "0XXXXX28a-f8c8-416f-ab5e-39fadc7ec910"
}
Key Points¶
- The Callback URL receives a simple GET request with query parameters
- The Payment Endpoint receives a POST request with a JSON payload
- Both responses contain important information about the transaction
- The
pay_id
anduser_id
are present in both responses - The webhook response includes additional details like
transaction_id
andamount
This demonstration shows how SecPaid integrates with your systems through both Callback URLs and Webhooks, providing flexibility in how you receive and process transaction information.