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.

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
22. Launch checkout (JS SDK)
33. Display checkout window (carrier selection)
44. Enter phone number and SMS authentication
55. Request approval
66. Return approval result
77. Result notification (notiUrl)

각 단계 상세

  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.

결제창 vs API 비교

항목결제창 연동API 연동
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)

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:
💬

Need technical support?