Setup Railz Connect

Railz Connect™ is what your end-users will interact with to link their service providers to your product. It will be embedded directly into your client-facing application for a seamless user experience.

Railz Connect™ will automatically handle all of the back and forth with the service providers, as well as deal with all the different types of authorization flows used by the service providers to protect your end users from unauthorized access.

Let's quickly setup Railz Connect™ to suit your brand and preferences.


Already using our old iFrame version of the widget?

We are planning to deprecate the original Railz widget in the coming months. At this point, we are offering our existing clients the possibility to try out and smoothly transition to the new Railz Connect™.

Setup Railz Connect™

On the dashboard navigate to Connect > Setup.

Railz Connect Setup. Click to Expand.Railz Connect Setup. Click to Expand.

Railz Connect Setup. Click to Expand.

To integrate Railz Connect™ into your website or application, copy the following script and paste it into your website's HTML source code before closing the </body> tag.


The code must be inserted into every page you want to display Railz Connect on. Note that this will not slow down your web pages.

<!-- Insert this div where you want Railz Connect to be initialized -->
<div id="railz-connect"></div>

<!-- Start of Railz Connect script -->
<script src=""></script>
  var widget = new RailzConnect();
    parentElement: document.getElementById('railz-connect'),
    widgetId: 'wid_bf51a64f-1d10-4dab-9e63-7bbbd123edd6'
    // Add additional Railz Connect configuration  paramaters here
<!-- End of Railz Connect script -->


Configure your Railz Connect

You have a variety of design configuration options to fit your brand experience. See Parameters for more details.

IP Whitelisting

You must define which IP addresses can embed Railz Connect™ in their application. In the IP Whitelist, you must add the public IP addresses of all application servers embedding Railz Connect™.


IP Whitelisting

  • If you do not add any IP addresses, your businesses will see the service not available screen .
  • No IP Whitelisting is required for loading Railz Connect in Sandbox Mode.
  • For testing Railz Connect on your local environment with a non-sandbox widgetId, you will need to whitelist your local server IP address. You can setup a local server using a tunnel service like ngrok and whitelisting the ngrok IP. You would need to ping your ngrok URL to get the IP address being used. You might need to whitelist multiple IP addresses depending on your location.
  • IPv6 is currently not supported.
  1. To manage your IP Whitelist navigate to Connect > IP Whitelist from the Dashboard.
  2. Select the Add IP button (to add an IP to the whitelist.
Railz Connect IP Whitelist.  Click to Expand.Railz Connect IP Whitelist.  Click to Expand.

Railz Connect IP Whitelist. Click to Expand.

  1. Enter the IP address you would like to whitelist, enter a Label to easily identify your IP, then select Save changes.
Add IP Address. Click to Expand.Add IP Address. Click to Expand.

Add IP Address. Click to Expand.

Service Not Available Screen

Railz Connect™ will display service not available screen if:

  • You have not whitelisted any IP address in production.
  • You have not configured and enabled any integrations.
  • You have reached your connection limit on a free plan.
Railz Connect Not Available. Click to Expand.Railz Connect Not Available. Click to Expand.

Railz Connect Not Available. Click to Expand.

Preventing Duplicate Accounting Connections

When a user links their accounting service provider account through Railz, a new connection is created. Two connections created for the same set of credentials (account) at the same accounting service provider will be considered a duplicate and will result in the most recent one being invalidated.

Preventing a user from accidentally linking a connection they have already linked can help avoid confusing behaviour in your application and will also prevent you from potentially being billed for both connections.


See Connection Disconnected for more details on subscribing to connection disconnected webhook event.

Did this page help you?