Integration Setup

This guide covers the prerequisites and basic information you need before integrating the Cash Receipt API.

Environment Credentials

The Sandbox and Production environments are completely separate, each using distinct Merchant IDs.

Environment	Merchant ID	Purpose
Sandbox	Shared test Merchant ID	Development and testing (no actual NTS submission)
Production	Merchant-specific ID	Live service (actual NTS submission)

Merchant-Specific Key Issuance (Post-Contract)

After signing a contract with Hecto Financial, the following credentials are issued for use in the Production environment.

Item	Description
Merchant ID (mid)	Unique merchant identifier (10 characters)

Server Integration Environment

Server Addresses and Network Information

The Cash Receipt API uses two domains. Most APIs use the primary domain, while certain inquiry APIs use domain2.

API (domain)

Used for registration, void, and status inquiry APIs.

Environment	Domain	IP Address	Protocol
Sandbox	tcash.settlebank.co.kr	61.252.169.42	HTTPS(TCP/443)
Production	cash.settlebank.co.kr	14.34.14.21 (Main) 61.252.169.53 (DR)	HTTPS(TCP/443)

API (domain2)

Used for the issuance error list inquiry and reprocessing result list inquiry APIs.

Environment	Domain	IP Address	Protocol
Sandbox	tb-nspay.settlebank.co.kr	61.252.169.42	HTTPS(TCP/443)
Production	nspay.settlebank.co.kr	14.34.14.21 (Main) 61.252.169.53 (DR)	HTTPS(TCP/443)

NOTE

IDC Redundancy Configuration

• The Hecto Financial PG system operates with Main and DR (Disaster Recovery) data centers for redundancy. • In the event of a Main center failure, traffic automatically switches to DR. Allow both Main and DR IPs in your firewall rules for the Production environment. • DNS Lookup connection is recommended — failover is handled automatically.

Development Requirements

Cash Receipt API integration is server-to-server only.

Component	Role
Backend (required)	Call the cash receipt register/void/inquiry APIs

NOTE

Server-Only API

Cash Receipt APIs are called exclusively from the backend server. Do not call them directly from the frontend.

API Integration Specifications

The Cash Receipt API does not use additional encryption; parameters are submitted in standard form format.

Item	Detail
Encoding	UTF-8
Method	GET or POST
Data format	application/x-www-form-urlencoded

Processing Model

Cash receipt registration uses a D+1 batch processing model.

Step	Description
Register/Void	Approval number issued immediately upon API call
NTS Submission	Prior day records submitted in batch at 00:00 on D+1
Error Inquiry	Available after 13:00 on D+1

NOTE

Detailed Processing Flow

For the detailed step-by-step flow from registration to error reprocessing, refer to the Full Integration Flow document.

Important Notes

Production Environment Testing

Production environment testing caution: Testing in the Production environment will transmit actual data to the NTS. Always complete testing in the Sandbox environment first.

Handling Incorrectly Registered Data

Incorrectly registered data in Production must be corrected via a void request. There is no way to delete records.

API Request Guidelines

Use GET or POST method.
UTF-8 encoding is required.
Use only the parameters defined in the integration specification.
Do not use special characters or HTML tags.

Browser and Protocol Requirements

HTTPS is required.
Ensures secure encrypted communication.

Auto-Reprocessing Merchants

Hecto Financial offers an auto-reprocessing service.

Type	Description
Auto-reprocessing merchant	When an error occurs, Hecto Financial automatically generates reprocessing data and resubmits to the NTS
Standard merchant	When an error occurs, the merchant must manually call the reprocessing registration API

NOTE