Skip to Contact an Expert Skip to Main Content
cardpointe logo
Developer Docs
Statuspage
Search Icon
Support
hamburger-menu
    Developer Docs
    Statuspage
  • Support
  1. CardPointe Integrated Payments
  2. CardPointe Integrated Terminal
  3. Allowing CardPointe Integrated Terminal Network Connections
  • Allowing CardPointe Integrated Terminal Network Connections
    • Overview
    • Frequently Asked Questions
    • On This Page

      Overview
      • CardPointe Integrated Terminal Connections
      • CardPointe Gateway Connections
    • On This Page

      Frequently Asked Questions

Overview 

 

If your application is running in a highly-restricted network environment, you might need to allow outbound traffic between your network and the CardPointe servers to to allow your terminals or application to connect to the necessary services.

 

If your network configuration includes firewall rules to restrict traffic, ensure that you allow outbound (egress) traffic to the following IP address ranges:

  • 167.16.248.0/24
  • 167.16.249.0/24
  • 198.62.137.0/24
  • 198.62.138.0/24
  • 206.201.62.0/24
  • 206.201.63.0/24

The following topics describe the addresses used by each CardPointe Integrated Terminal and CardPointe Gateway resource in greater detail.

As a best practice, all application configurations should only reference the fully-qualified domain name (FQDN) of the CardPointe Integrated Terminal or CardPointe Gateway services, instead of hard-coding IP addresses. This approach mitigates the need for changes when services migrate between data center locations, and preserves backwards compatibility during future updates.

CardPointe Integrated Terminal Connections

The following table applies to all CardPointe Integrated Terminal users, including those using an integrated CardPointe Integrated Terminal solution as well as merchants using CardPointe Integrated Terminal devices with the CardPointe Virtual Terminal. 

Destination NamePortDescriptionEnvironmentProtocol
bolt.cardpointe.com443CardPointe Integrated Terminal API ConnectionPRODTCP
bolt-terminal.cardpointe.com443CardPointe Integrated Terminal Gateway ConnectionPRODTCP
bolt-uat.cardpointe.com

443

CardPointe Integrated Terminal API ConnectionUATTCP
bolt-terminal-uat.cardpointe.com443CardPointe Integrated Terminal Gateway ConnectionUATTCP
tms.cardconnect.com

443

Terminal Management Service (TMS)
PRODTCP

CardPointe Gateway Connections

The following table provides the CardPointe Gateway IP addresses used to access the CardPointe Gateway by an integrated application as well as by a CardPointe Integrated Terminal. 

 

For merchants integrated to the CardPointe Gateway or CardPointe Integrated Terminal solution, your connection is configured for a particular Gateway site (for example, "fts" or "boltgw.).  Refer to the exact URL that you were provided by our Integration Delivery Team or your software vendor to ensure that you are allowing the necessary network connections. 

In the following table, <sitename> refers to the host parameter of the URL that you connect to (for example, fts.cardconnect.com, or boltgw.cardconnect.com).

Destination NameDestination AddressPortDescriptionEnvironmentProtocol
<sitename>-uat.cardconnect.com
  • 167.16.248.0/24
  • 167.16.249.0/24
  • 198.62.138.0/24
  • 206.201.63.0/24
443CardPointe Gateway
UATTCP
<sitename>.cardconnect.com
  • 167.16.248.0/24
  • 167.16.249.0/24
  • 198.62.138.0/24
  • 206.201.63.0/24
443CardPointe Gateway

PROD

TCP

Frequently Asked Questions 

Most firewalls block or restrict traffic to limit access to only necessary users and services. If you restrict traffic in your environment, you must add the IP address ranges in this guide to your list of trusted IP addresses to allow traffic to and from the required services.

A firewall is a part of a computer or network that is designed to block unauthorized access while permitting outward communication.

  • Ingress traffic originates outside of a business' routers and travels to a destination inside of the business' network.
    • Example: An authorization response from the CardPointe Gateway travels across the internet to the business' network and is delivered to the merchant's system.
  • Egress traffic begins inside of a business' network and travels through its routers to a destination outside of the network.
    • Example: An API call from the merchant's system travels from the business' network to the internet and is delivered to the CardPointe Gateway.

Site Selector