Banks, payments and partners

A fixed IP for banks, payments and partners

Banking portals, payment providers and partners often only accept connections from IP addresses you register with them. Give them your TunnelYard gateway's IP once, and keep it when your office, ISP or line changes.

Finance officeCisco · 10.20.0.0/24Bank portalallows your IPPaymentsallows your IPPartner SFTPallows your IPYour gateway203.0.113.10static IPsame IP when you moveIPsec tunnelinternet, from 203.0.113.10

Connects to standard IPsec firewalls and routers

Why finance and operations teams use a TunnelYard IP

Register one address, once

Partners ask for your IP up front, and changing it can mean a support ticket and days of waiting. The gateway's IP stays the same while the gateway runs.

Dedicated to your company

Each gateway is a dedicated server with its own static IPv4, so the address you register is only ever used by your offices.

The country you need

38 locations in 20 countries today, so your traffic can leave from the country your bank or partner expects.

How it works

Up and running in four steps

  1. 1

    Launch a gateway

    Choose a location close to your office or your partner. It's ready in 10–15 minutes with its own static public IPv4.

  2. 2

    Connect the office

    Add a tunnel for the office that needs access and export the config for its firewall.

  3. 3

    Register the IP

    Give the gateway's IP to your bank, payment provider or partner for their allow-list.

  4. 4

    Stay connected

    Get an alert when the tunnel has been down for 2 minutes, and keep traffic and uptime history for every tunnel.

Features you'll use

Built for this job

All features

Control what goes out

Allow and deny rules by tunnel, subnet, protocol and port on Business and Enterprise, so only the systems that need a partner reach it.

Uptime history

Traffic and uptime per tunnel: 7 days on Starter, 90 on Business and 365 on Enterprise.

Configs for your firewall

Export a ready-to-paste config for Cisco, Fortinet, Palo Alto, Juniper, MikroTik, pfSense and more.

FAQ

Questions about bank and partner access

Why do banks and partners ask for a fixed IP?

Banking portals, payment providers, partner APIs and SFTP servers often accept connections only from IP addresses you have registered with them. A fixed IP lets them tell your company's traffic apart from everyone else's.

What happens to the IP if we change ISP or move office?

Nothing. You update the office's new public IP in the tunnel; the gateway's static IP stays the same, so there is nothing to re-register with your bank or partners.

Can partners connect to us through the gateway?

No. TunnelYard carries your offices' outbound traffic. Inbound connections and port forwarding are not offered, so it can't publish a server or SFTP site of your own.

Can we choose the country the IP is in?

Yes. You choose from 38 locations in 20 countries today, across North America, South America, Europe, the Middle East, Asia, Oceania and Africa. The list can change as locations are added.

Can we limit what goes through the gateway?

Yes. Every plan blocks P2P and BitTorrent if you choose. Business and Enterprise add allow and deny rules by tunnel, subnet, protocol and port; the first match wins. Enterprise also logs rule hits and keeps hit counters.

Which firewalls can connect?

Anything that speaks IPsec with IKEv2 and pre-shared keys, including Cisco, Fortinet, Palo Alto Networks, Juniper, MikroTik, pfSense, OPNsense, Ubiquiti and OpenWrt. TunnelYard exports a ready-made config for each of them.

Get a static IP for your office

Launch a gateway, connect your firewall, and allow-list one IP today.