Integration Prerequisites
This guide covers the prerequisites and essential information you need to know before integrating the Easy Cash Direct Debit (Open Banking) API.
Credentials by Environment
The Sandbox and Production environments are separate, each using distinct Merchant IDs and keys.
| Environment | Merchant ID | Auth Key | Purpose |
|---|---|---|---|
| Sandbox | Shared test Merchant ID | Shared test key | Development and testing (no actual transfers occur) |
| Production | Merchant-specific ID | Merchant-specific key | Live service (actual transfers occur) |
Merchant-Specific Key Issuance (Post-Contract)
After signing a contract with Hecto Financial, you will receive the following credentials for use in the Production environment.
| Item | Description |
|---|---|
| Merchant ID (mchtId) | Unique merchant identifier |
| Hash generation key | Key for generating hashes to prevent tampering (SHA-256) |
| Encryption key | Key for protecting personal and sensitive data (AES-256) |
Issuance via sales representative
Where to Find Your Keys
You can look up your issued keys on the merchant admin site. The merchant admin site URL and account are provided by your sales representative.
- In the left menu of the merchant admin site, select [Master Store Information] → [Basic Information].
- Check the hash generation key (license) and encryption key in the [License & Encryption key information] section at the top of the Basic Information page.
Access inquiries
Server Integration Environment
For server domains, IP addresses, and firewall settings, see Servers & Network.
Development Environment Requirements
Easy Cash Direct Debit integration requires a backend server.
| Component | Role |
|---|---|
| Backend (required) | Hash generation, personal data encryption, payment processing, result verification |
| Frontend | Identity verification screen invocation (if applicable) |
Backend server is required
Encryption, Decryption, and Tamper Prevention
Easy Cash Direct Debit uses two layers of security to protect data.
Personal and Sensitive Data Encryption
| Item | Details |
|---|---|
| Algorithm | AES-256 / ECB / PKCS5Padding |
| Encoding | Base64 encoding |
| Data to encrypt | Contact name, phone number, mobile number, email, account holder name, account number, etc. |
| Sandbox key | pgSettle30y739r82jtd709yOfZ2yK5K (32 bytes) |
| Production key | Issued separately after contract |
Tamper Prevention Algorithm
| Item | Details |
|---|---|
| Algorithm | SHA-256 |
| Encoding | Hex encoding |
| Sandbox key | ST1009281328226982205 (21 bytes) |
| Production key | Issued separately after contract |
| Generation method | Combine parameters → SHA-256 hash → Hex conversion |
Hash verification is mandatory
Important Notes
Production Environment Testing
Production environment testing
API Request Guidelines
- POST method only — All APIs support POST only
- JSON format — Both requests and responses use application/json;charset=UTF-8
- Special character restrictions — The following characters cannot be transmitted:
:,&,?,',new line,<,> - Parameter validation — Missing required fields, hash mismatch, or parameter length violations return an error response
{
"outStatCd": "0031",
"outRsltCd": "ST09",
"outRsltMsg": "Invalid request message"
}
Response Parameters May Change
Response parameters may change
Network and Protocol Requirements
- TLS 1.2 or higher required — HTTPS (port 443) only
- Timeout — API response timeout is 30 seconds
- Firewall settings — Allow both Primary and Secondary Production IPs
- Avoid hardcoding IPs — Hardcoding IPs in the hosts file prevents automatic IDC center failover
Next Steps
Step-by-step guides
Open Banking Integration Flow
End-to-end flow and implementation guide: ARS authentication → account enrollment → payment
Account Management
Account enrollment, Open Banking account enrollment, service withdrawal
Payment / Remittance
Direct debit payment, void/refund, remittance
Fund Return Claim
Fund return claim request and status check
