헥토파이낸셜 개발자센터
ProductsProducts
Payment Gateway
Cards, bank & digital wallets
My Bank Pay
Open banking debit
Easy Cash Payment
Stored-account payments
White-Label Payments
White-label checkout
Cash Receipt
Firm Banking
VAN Virtual Account
Prepaid Wallet
Integrate with LLMs
MCP server & AI chatbot
API & SDKAPI & SDK
Payment Gateway
Cards, bank & digital wallets
My Bank Pay
Open banking debit
Easy Cash Payment
Stored-account payments
White-Label Payments
White-label checkout
Cash Receipt
Firm Banking
VAN Virtual Account
Prepaid Wallet
블로그Blog
Service Status
Payment Gateway
My Bank Pay
Easy Cash Payment
White-Label Payments
Cash Receipt
Firm Banking
VAN Virtual Account
Prepaid Wallet
Integrate with LLMs
MCP 서버 및 AI 챗봇
Payment Gateway
My Bank Pay
Easy Cash Payment
White-Label Payments
Cash Receipt
Firm Banking
VAN Virtual Account
Prepaid Wallet
Blog
Technical blog & news
Service Status
Incidents and scheduled maintenance
Getting StartedCredit CardVirtual Account010 Virtual AccountBank TransferMobile PaymentGift CardPoint DamoaDigital Wallets
My Bank Pay
Firm BankingOpen Banking
White-Label Payments
Cash Receipt
Firm Banking
VAN Virtual Account
Prepaid Wallet
Getting StartedCredit CardVirtual Account010 Virtual AccountBank TransferMobile PaymentGift CardPoint DamoaDigital Wallets
My Bank Pay
Firm BankingOpen Banking
White-Label Payments
Cash Receipt
Firm Banking
VAN Virtual Account
Prepaid Wallet
ProductsPayment GatewayMobile Payment

Mobile Payment

Mobile payment is a micropayment method where payment is processed through a mobile carrier, and the payment amount is added to the following month's mobile phone bill.
Even customers without credit cards can pay as long as they have a mobile phone, making it especially suitable for digital content payments.

Hecto Financial supports SKT, KT, LGU+, and MVNO carriers, and offers not only standard micropayments but also recurring payments (monthly auto) for subscription services.

NOTE

Key flow for mobile payments. Buyer selects carrier → Authentication (SMS, PASS, ARS) → Carrier approval → Payment complete (added to next month's bill).

Learn About Payment Methods

Hecto Financial offers various mobile payment methods you can choose based on your service needs.

Standard PaymentCheckout ✓API ✗

A standard micropayment method where the buyer selects a carrier and completes authentication in the checkout window, and the payment amount is added to the following month's mobile phone bill.

  • Can only be used via checkout integration.
  • Suitable for digital content services as customers without credit cards can also make payments.
Recurring Payment (Monthly Auto)Checkout ✓API ✓

A subscription-type payment method that is charged automatically every month. For the 1st payment, the customer authenticates directly in the checkout window; from the 2nd payment onward, the merchant server automatically charges using the issued billKey.

  • 1st payment: Customer authenticates directly in checkout → billKey issued
  • 2nd payment and beyond: Merchant server calls the auto-approval API using the billKey
  • A dedicated merchant ID for recurring payments is required.
  • Continuous monthly payments are required; if payment fails, the billKey must be re-issued.
NOTE
Recurring payment dates must be processed within ±3 days of the previous month's payment date. Continuous monthly payments are required; if payment fails, the billKey must be re-issued.
Authentication/Approval SeparationCheckout ✓API ✓

A method that separates customer authentication from actual approval processing. The approval API is called after authentication is complete.

  • No payment occurs at the authentication stage.
  • The merchant calls the approval API at the required time to finalize payment.
  • Suitable for cases requiring intermediate processing such as inventory checks or order validation.

Learn About the Payment Flow

Checkout Integration

When the merchant's webpage calls the Hecto Financial checkout window, the buyer selects a carrier and proceeds with payment via SMS authentication. The payment amount is added to the following month's mobile phone bill.

Buyer
Merchant
Hecto Financial
Carrier
11. Select mobile payment from order form
1. Select mobile payment from order form
22. Launch checkout (JS SDK)
2. Launch checkout (JS SDK)
33. Display checkout window (carrier selection)
3. Display checkout window (carrier selection)
44. Enter phone number and SMS authentication
4. Enter phone number and SMS authentication
55. Request approval
5. Request approval
66. Return approval result
6. Return approval result
77. Result notification (notiUrl)
7. Result notification (notiUrl)

Step Details

  1. 1Payment Request : The buyer selects mobile payment from the order form.
  2. 2Launch Checkout : The merchant calls the JavaScript SDK (SETTLE_PG.pay) to open the checkout window.
  3. 3Select Carrier : The buyer selects their carrier.
  4. 4Authentication : The buyer enters their phone number and confirms authentication (SMS, PASS, ARS).
  5. 5Approval Request : Hecto Financial requests payment approval from the carrier.
  6. 6Approval Result : The carrier returns the approval result.
  7. 7Result Notification : Hecto Financial delivers the payment result to the merchant server's notiUrl.
Make sure to implement notiUrl. notiUrl is required for checkout integration. Even if the buyer closes the checkout window midway or exits the browser, payment results can be reliably received via notiUrl.

Checkout vs. Direct API

ItemCheckout IntegrationDirect API Integration
When UsedStandard payment, 1st recurring payment2nd recurring payment and beyond
Payment UIHecto Financial checkout windowNo checkout window (server-to-server communication)
Customer AuthenticationAuthentication required (SMS, PASS, ARS)No authentication required (uses billKey)

API Integration (Recurring Payment from 2nd charge)

This method uses the billKey issued during the 1st payment to directly call the payment API from the merchant server. From the 2nd charge onward, payments are processed automatically using the billKey.

Merchant
Hecto Financial
Carrier
11. Call recurring payment API (with billKey)
1. Call recurring payment API (with billKey)
22. Payment request
2. Payment request
33. Return payment result
3. Return payment result
44. API response
4. API response

Step Details

  1. 1API Call : The merchant server calls the recurring payment approval API with the billKey.
  2. 2Payment Request : Hecto Financial requests payment from the carrier.
  3. 3Payment Result : The carrier returns the payment result.
  4. 4API Response : Hecto Financial responds to the merchant server with the payment result.
NOTE
notiUrl is not required for API integration. This is because payment results can be received directly via the API response.

Cancellation and Refunds

CategoryProcessing MethodAvailability
Same-month CancellationCancellation APIWithin the payment month (M month), from the 1st to the last day
Refund after Following MonthRefund APIWithin 1 year of the refund period

Distinguish between cancellation and refund. The processing method for mobile payments differs between the payment month (M month) and subsequent months. Incorrect API calls may cause processing failures.

Pre-Integration Checklist

Before starting mobile payment integration, it is helpful to confirm the following items in advance.

Merchant ID Related

  • Standard payment and recurring payment use separate merchant IDs. Please request a dedicated recurring payment merchant ID from your sales representative.
  • Merchant IDs differ between sandbox and production environments. Testing in the production environment will incur actual charges, so please make sure to use the sandbox.

Other Notes

  • Recurring payment requires continuous monthly charges. If payment fails, the billKey must be deleted and re-issued.
    (However, merchants with exceptions negotiated with the sales team are not subject to this restriction.)
  • Invalid mobile recurring payment keys will be deleted the following year.
  • Recurring payment dates must be processed within ±3 days of the previous month's payment date.

Policy Related

  • Cancellation period: Until the last day of the payment month (M month); Refund period: 1 year
  • Amount limits may apply depending on carrier policies.
  • For recurring payments, charges must be processed within ±3 days of the previous month's payment date.

Sales / Screening Related

  • Carrier screening criteria vary by business type, such as digital content or physical goods.
  • Sales inquiry:

Mobile Payment Developer Documentation

📱

Mobile Payment API

Standard payment and monthly auto 1st charge request

🔄

Monthly Auto Payment API (2nd charge+)

Recurring approval request using BillKey

↩️

Mobile Payment Cancellation API

Same-month payment cancellation request

💬

Need technical support?

Code Samples

HectoFinancial GitHub