Skip to main content
When PCI Booking makes an outbound call on your behalf — processing a payment through a PSP, relaying a request to a third party, or forwarding data to your own API — the request originates from PCI Booking’s infrastructure. Some third parties require these addresses to be whitelisted before they’ll accept traffic; without it, you’ll typically see a 401, 403, or a generic “not allowed from there” style rejection at the third party.

​
Current IP Addresses

This is the current list of IP addresses PCI Booking uses for outbound calls. This list may change — contact support@pcibooking.net to confirm the current list before relying on it for a whitelist configuration, especially for a production integration.

​
When You Need This

  • Configuring a PSP’s firewall/whitelist so PCI Booking can reach their API through the Universal Payment Gateway.
  • Setting up Token Replacement in Response or Tokenization on Request, where PCI Booking relays requests to your own API and third parties may whitelist PCI Booking as the caller.
  • Any third-party integration that rejects requests until PCI Booking’s origin is explicitly allowed.