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.
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.
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.
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.
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.
Step Details
- 1Payment Request : The buyer selects mobile payment from the order form.
- 2Launch Checkout : The merchant calls the JavaScript SDK (SETTLE_PG.pay) to open the checkout window.
- 3Select Carrier : The buyer selects their carrier.
- 4Authentication : The buyer enters their phone number and confirms authentication (SMS, PASS, ARS).
- 5Approval Request : Hecto Financial requests payment approval from the carrier.
- 6Approval Result : The carrier returns the approval result.
- 7Result Notification : Hecto Financial delivers the payment result to the merchant server's notiUrl.
Checkout vs. Direct API
| Item | Checkout Integration | Direct API Integration |
|---|---|---|
| When Used | Standard payment, 1st recurring payment | 2nd recurring payment and beyond |
| Payment UI | Hecto Financial checkout window | No checkout window (server-to-server communication) |
| Customer Authentication | Authentication 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.
Step Details
- 1API Call : The merchant server calls the recurring payment approval API with the billKey.
- 2Payment Request : Hecto Financial requests payment from the carrier.
- 3Payment Result : The carrier returns the payment result.
- 4API Response : Hecto Financial responds to the merchant server with the payment result.
Cancellation and Refunds
| Category | Processing Method | Availability |
|---|---|---|
| Same-month Cancellation | Cancellation API | Within the payment month (M month), from the 1st to the last day |
| Refund after Following Month | Refund API | Within 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:
