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 requestbin.com 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:

Create a TEST or LIVE payment, then check your RequestBin data. It should look something like this:

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:

In the "Choose app & event" section, select Catch Hook:

Select Continue, and skip the Set up trigger section.

Continue to Test Trigger, and copy the Webhook URL provided by Zapier:

Go back to edit your payment form, and under the section Actions After Submit, ensure you have HTTP Request selected:

In the HTTP Request settings, paste in your Zapier Webhook URL:

Run a TEST or LIVE payment on the payment form.

Then, click Test Trigger in the Zapier Dashboard:

The resulting data will look something like this:

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.

Last updated