Servers & Network
Server domains and IP addresses by environment for PG integration. Refer to the information below when configuring your firewall.
The Checkout method calls the checkout page via SDK or HTML Form, while the API method calls the API directly from the server in JSON format. The webhook server is a server that sends payment results from Hecto Financial to your server after a transaction is completed.
Checkout
| Environment | Domain | IP Address | Protocol |
|---|---|---|---|
| Sandbox | tbnpg.settlebank.co.kr | 61.252.169.51 | HTTPS(TCP/443) |
| Production | npg.settlebank.co.kr | 14.34.14.25 (Primary) 61.252.169.58 (Secondary) | HTTPS(TCP/443) |
API
| Environment | Domain | IP Address | Protocol |
|---|---|---|---|
| Sandbox | tbgw.settlebank.co.kr | 61.252.169.42 | HTTPS(TCP/443) |
| Production | gw.settlebank.co.kr | 14.34.14.21 (Primary) 61.252.169.53 (Secondary) | HTTPS(TCP/443) |
Webhook
| Environment | IP Address | Protocol |
|---|---|---|
| Sandbox | 61.252.169.22 | HTTPS(TCP/443) |
| Production | 14.34.14.23 (Primary) 61.252.169.24 (Secondary) | HTTPS(TCP/443) |
NOTE
High Availability (Dual IDC)
• The Hecto Financial PG system is configured in dual data centers with a Primary and Secondary center.
• In the event of a Primary center failure, automatic failover to the Secondary occurs, so both Primary and Secondary IPs for the production environment must be allowed through the firewall.
• DNS Lookup connection is recommended — this is handled automatically during center failover (hosts file pinning will prevent failover)
Allow Webhook Server IPs in Your Firewall
All webhook server IPs must be allowed for Inbound access through your firewall. Both the Primary and Secondary IPs must be allowed; if either is missing, webhooks sent from that center may not be received.
