Easy Cash Payment (Firm Banking)

Easy Cash Payment (Firm Banking) is a service that processes payments using the user's bank account, and can be integrated into your system via API for payment, authentication, account management, refunds, and more. Users register their bank account through bank account authentication, and payments are made from that account — a typical flow of identity verification → account registration → payment → transaction management.

Unlike card payments, there is no card number entry process, and after account registration, payments are made through a relatively simple procedure. From a business perspective, Easy Cash Payment APIs can be used as a convenient payment method across a wide range of services including subscriptions, platforms, and content services.

The Easy Cash Payment (Firm Banking) service provided by Hecto Financial can be used as a "payment platform" that offers payment-related features in API form — unlike a simple bank transfer.

NOTE

Easy Cash Payment (Firm Banking) core flow. Identity verification → Account registration → Call withdrawal approval API → Immediate withdrawal from customer's account.

Payment Methods

Key Features

A service that directly withdraws funds from the customer's account via the merchant's bank network (firm banking). Supports multiple authentication methods including mobile SMS, ARS, and 1-KRW micro-deposit, and can handle payments, recurring billing, and remittances with just an account — no card required.

Multiple identity verification options: Supports mobile phone SMS/APP authentication, ARS automated response authentication, and 1-KRW micro-deposit authentication.
Real-time withdrawal: Funds are immediately withdrawn from the registered account and settled.
Recurring payment support: Issue a recurring payment key for subscriptions, membership fees, rental fees, and other repeat payments.
Remittance: Funds such as refunds and reward payments can be sent from the merchant's account to the customer's account.

Payment Flow

Easy Cash Payment (Firm Banking) provides all features via API. (No checkout UI)
During account registration, multiple APIs are called in sequence: identity verification, account holder confirmation, ARS/1-KRW authentication, and more.

Account Registration Flow

The process by which a customer registers an account to use for payments. Proceeds in the order: identity verification → account holder confirmation → account ownership verification (ARS/1-KRW) → account registration.

Customer

Merchant

Hecto Financial

Bank

11. Account registration request

1. Account registration request

22. Mobile identity verification request

2. Mobile identity verification request

33. Send verification code

3. Send verification code

44. Enter verification code

4. Enter verification code

55. Confirm identity verification

5. Confirm identity verification

66. Account holder name inquiry

6. Account holder name inquiry

77. ARS/1-KRW account ownership verification

7. ARS/1-KRW account ownership verification

88. ARS phone call or 1-KRW micro-deposit

8. ARS phone call or 1-KRW micro-deposit

99. Account registration request

9. Account registration request

1010. Account registration response

10. Account registration response

각 단계 상세

1Account registration request : The customer requests to register a payment account at the merchant.
2Mobile identity verification request : The merchant requests mobile identity verification from Hecto Financial.
3Send verification code : Hecto Financial sends a verification code to the customer.
4Enter verification code : The customer enters the received verification code at the merchant.
5Confirm identity verification : The merchant calls the identity verification confirmation API with Hecto Financial.
6Account holder name inquiry : The account holder name inquiry API is called to verify the account owner.
7Account ownership verification request : Account ownership is verified via ARS authentication or 1-KRW micro-deposit.
8ARS call or 1-KRW micro-deposit : For ARS, a call is placed to the customer's phone; for 1-KRW, a small amount is deposited into the customer's account.
9Account registration request : Once all authentication is complete, the merchant calls the account registration API.
10Account registration response : The account registration result and custAcntKey are returned in the response.

It is recommended to complete all authentication steps in order for account registration. Identity verification → Account holder confirmation → Account ownership verification → Account registration The authentication result from each step is used in the next step. * ARS/1-KRW authentication can be replaced by the merchant's own authentication method for account registration consent documentation. For details regarding account registration consent documentation, please consult with the relevant business representative.

Pre-Integration Checklist

Before starting integration, we recommend reviewing the following items.

Production Environment Testing Notice

Any costs incurred from testing in the production environment are borne by the merchant. All testing must be completed in the sandbox before using the production environment.

Request/Response method

Only POST requests are supported.
Request header: Content-Type: application/json; charset=UTF-8
Response format: JSON

IDC redundancy configuration

The Hecto Financial system is configured with IDC center redundancy.
Connection via DNS Lookup is recommended; fixed hosts file configuration is not recommended.
Please allow both Primary and Secondary IP addresses in your firewall.

Developer Documentation

Getting Started

Server environment, key information, security setup

Identity Verification

Mobile phone / ARS / 1-KRW deposit authentication

Account Management

Account registration and deregistration

Payment

Withdrawal approval and cancellation/refund

Need technical support?

Code Samples

HectoFinancial GitHub