Servers & Network
Server domains and IP addresses by environment for EzAuth integration. Refer to the information below when configuring your firewall.
EZAuth Bank Transfer supports both a checkout (UI) method and a direct API method. After the customer completes authentication through the checkout, your server calls the payment capture API.
Checkout
| Environment | Domain | IP Address | Protocol |
|---|---|---|---|
| Sandbox | tbezauth.settlebank.co.kr | 211.236.228.34 | HTTPS(TCP/443) |
| Production | ezauth.settlebank.co.kr | 61.252.169.45 (Primary) 14.34.14.39 (Secondary) | HTTPS(TCP/443) |
API
| Environment | Domain | IP Address | Protocol |
|---|---|---|---|
| Sandbox | tbezauthapi.settlebank.co.kr | 211.236.228.36 | HTTPS(TCP/443) |
| Production | ezauthapi.settlebank.co.kr | 61.252.169.45 (Primary) 14.34.14.39 (Secondary) | HTTPS(TCP/8081) |
NOTE
Production Port Number
The production environment uses port 8081. Configure your firewall to allow outbound HTTPS(TCP/8081).
NOTE
IDC Redundancy
• The Hecto Financial EZAuth system is deployed across a Primary and a Secondary data center.
• If the Primary center fails, traffic switches to the Secondary automatically, so allow both Primary and Secondary production IPs in your firewall.
• Connect via DNS lookup (recommended); the switch is handled automatically. Pinning IPs in a hosts file will prevent failover.
