Payment Page Documentation
Main siteDemoRoadmapGet support
  • Welcome 👋
  • Getting Started
    • Quick Setup
    • Troubleshooting
  • Pricing Options
    • Plan & Pricing Options
    • Subscription & Currency Filters
    • Custom Payment Amounts
    • Setup Fee
  • Styling Options
    • Style & Design Options
  • Supported Payment Gateways
    • Stripe
      • Stripe Webhook Configuration
      • Credit + Debit Cards
      • SEPA Direct Debit
      • Google Pay
      • Apple Pay
      • Microsoft Pay
      • Alipay
      • WeChat Pay
    • PayPal
      • PayPal Setup
      • PayPal Webhook Configuration
      • Credit + Debit Cards
      • Pay Later
      • Venmo
      • Bancontact
      • BLIK
      • eps
      • giropay
      • iDEAL
      • Mercado Pago
      • MyBank
      • Przelewy24 (P24)
      • SOFORT
  • Features
    • Prefill Form Fields (query strings)
    • Form Actions on Submit
      • Confirmation Email
      • Redirect
      • Dynamic Message
      • HTTP Requests
  • FAQs
    • How can I sign up for BETA versions?
    • What's the total cost of using the plugin?
    • How do I add Gaucho Plugins to my Stripe team?
  • Advanced Configuration
    • REST API
    • Hooks & Filters
    • PHP Versions Supported (7.1+)
    • Known Plugin Conflicts
  • Changelog
    • Changelog
Powered by GitBook
On this page
  • Testing HTTP Requests via RequestBin
  • Testing HTTP Requests via Zapier

Was this helpful?

  1. Features
  2. Form Actions on Submit

HTTP Requests

Send data to an external URL when the form fields are submitted.

PreviousDynamic MessageNextHow can I sign up for BETA versions?

Last updated 1 month ago

Was this helpful?

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:

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.

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.

Create a new Zap in your .

Zapier Dashboard
Prefill Form Fields (query strings)
requestbin.com
RequestBin Endpoint URL
HTTP Request Settings in Payment Page with RequestBin URL
HTTP Request Data in RequestBin
Creating a Zapier Zap with Webhooks by Zapier
Webhooks by Zapier Catch Hook Trigger
Testing a Webhook Trigger in Zapier - Copy Webhook URL
Payment Page Actions After Submit Settings
HTTP Request Settings in Payment Page with Zapier Webhook URL
Test Trigger Button in Zapier Dashboard
Zapier Webhook Data from Payment Page Plugin