HTTP Requests

Send data to an external URL when the form fields are submitted.
Ensure Webhooks are configured correctly in order for HTTP Requests to process properly.
Send your payment confirmation details to any external URL as an HTTP Request upon payment confirmation. This is perfect for SaaS platforms or mobile apps that want to utilize an external payment platform while retaining all the relevant details of their customer and the payment.

Testing HTTP Requests via RequestBin

Go to and create a Bin by registering for a free account or creating a public bin.
Copy your RequestBin endpoint URL into the Payment Page HTTP Request Settings:
RequestBin Endpoint URL
HTTP Request Settings in Payment Page with RequestBin URL
Create a TEST or LIVE payment, then check your RequestBin data. It should look something like this:
HTTP Request Data in RequestBin

Testing HTTP Requests via Zapier

The HTTP Request can be tested with the Zapier Webhooks mechanism for free by following the steps below.
Create a new Zap in your Zapier Dashboard.
For your Trigger, select Webhooks by Zapier. While it's a Premium Zapier feature, it can be tested for free:
Creating a Zapier Zap with Webhooks by Zapier
In the "Choose app & event" section, select Catch Hook:
Webhooks by Zapier Catch Hook Trigger
Select Continue, and skip the Set up trigger section.
Continue to Test Trigger, and copy the Webhook URL provided by Zapier:
Testing a Webhook Trigger in Zapier - Copy Webhook URL
Go back to edit your payment form, and under the section Actions After Submit, ensure you have HTTP Request selected:
Payment Page Actions After Submit Settings
In the HTTP Request settings, paste in your Zapier Webhook URL:
HTTP Request Settings in Payment Page with Zapier Webhook URL
Run a TEST or LIVE payment on the payment form.
Then, click Test Trigger in the Zapier Dashboard:
Test Trigger Button in Zapier Dashboard
The resulting data will look something like this:
Zapier Webhook Data from Payment Page Plugin
Then, you can automate anything you want with Zapier apps or build your own custom functionality based on the data provided.
Custom form fields will be passed individually. Query strings that aren't matched to any custom form fields will also be included in the HTTP Request details.