Integrating Paddle

To connect Paddle as your payment provider, you will need to enter your Vendor IDVendor Auth Code and also configure your Webhook settings.

Accesing your Vendor ID and Vendor Auth Code:

Your Paddle Vendor ID and Vendor Auth Code can be found by heading to Authentication area within Developer Tools (whilst logged into Paddle). From here you'll see your Vendor ID listed near the top. To access your Vendor Auth Code, either click the "Reveal Auth Code" button against an existing auth code, or create a new one.

Take both the Vendor ID and Vendor Auth Code generated here and enter them into your Paddle setup form within OnboardFlow.

Setting up Webhooks:

Once configured, Webhooks allow Paddle to send key subscription data to OnboardFlow as needed. Setting them up is a two-step process. First, head to the Webhooks area within Developer Tools (whilst logged into Paddle) and in the "URL for receiving webhook alerts" text box, paste in your unique Webhook URL provided to you on the OnboardFlow Paddle setup form. This will typically be something equivelant to https://gateway.onboardflow.com/webhooks/XXXXXXX/paddle/

Next, we need to tick the events that we want Paddle to send OnboardFlow notifications about. Under the Subscriptions section, please tick the Webhook checkboxes next to Subscription CreatedSubscription Updated and Subscription Cancelled. Once done, don't forget to press the Save button.

Finally, you'll need to add your Paddle Public Key. The Public Key is required to validate all inbound Webhook requests. You can find your Paddle Public Key by heading to the Public key Area within Developer Tools (whilst logged into Paddle).

Your webhook is now setup in Paddle. 

What if I already have a Webhook setup within Paddle?

Currently, Paddle has a restriction whereby only one webhook destination can be set up at once. If you already have a Webhook destination setup then you have three options:

  1. Replace your existing Webhook URL with the OnboardFlow one (but only do this if you can afford to lose the original Webhook connection)
  2. Listen out for the webhook response on the original webhook destination and then forward each event to your OnboardFlow webhook URL
  3. Assuming you maintain your existing (non OnboardFlow) Webhook URL, it should be possible for us to fetch each Webhook request sent to that destination manually (via their API). To use this option, we will need to activate an option on your account. Please contact us if you'd like us to activate this option.  
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.