헥토파이낸셜 개발자센터
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 GatewayCredit Card

Credit Card Payment

Credit card payment is a method where customers pay for goods or services using a card issued by their card company. It accounts for the largest share of online payment methods and is a familiar and convenient payment method for both customers and merchants.

Instead of physically inserting or tapping a card online, payments are processed by entering card information or authenticating via the card issuer app.
Once payment is complete, the card issuer pays the merchant, and the customer is billed on their next billing date.

This document provides a step-by-step guide to how credit card payment works, what payment methods are available, and what you should know when integrating.

NOTE

The core flow of card payment. Customer submits payment request → Cardholder authentication → Card authorization → Payment complete. This flow is fundamentally the same regardless of the payment method.

Payment Methods Overview

Hecto Financial offers a variety of credit card payment methods so you can choose the one that fits your service.

Authenticated PaymentCheckout ✓API ✗

The most common payment method. The customer authenticates themselves via the card issuer app (ISP, app card, etc.) or password, and then the payment is authorized.

  • Provides the highest level of security because it goes through the card issuer's own authentication.
  • Well suited for typical online shopping mall and service payments.
  • Available only through checkout integration.
Non-authenticated Payment (KEY-IN)Checkout ✓API ✓

A method where payment is completed by entering just two pieces of information: card number and expiration date.

  • Allows simple payment without a separate card issuer app authentication.
  • Helps increase payment conversion rates by skipping the authentication step.
  • Supports both checkout and API integration.
Legacy-authenticated Payment (KEY-IN enhanced)Checkout ✓API ✓

A method with one additional layer of security compared to non-authenticated payment. In addition to card number and expiration date, it requires the date of birth and the first two digits of the PIN — a total of four pieces of information.

  • Provides higher security than non-authenticated payment while still allowing payment without installing a card issuer app.
  • Supports both checkout and API integration.
BillKey Payment (Recurring Billing)Checkout ✗API ✓

Used when repeat billing is needed, such as for subscription services or recurring deliveries. Card information is entered only once, a unique identifier called a BillKey is issued, and subsequent payments can be requested using only the BillKey.

  • Customers do not need to re-enter card information each time, making it convenient.
  • Merchants can automatically execute payments at any desired time.
  • Available only through API integration.
  • A separate Merchant ID for BillKey payments may need to be issued.
NOTE
The BillKey's validity period is the same as the associated card's expiration date. When the card expires, the BillKey can no longer be used, so please manage both the BillKey and expiration date together.
Separate Auth & CaptureCheckout ✓API ✓

A method that separates customer authentication from the actual authorization. After authentication is complete, the developer calls the authorization API separately.

  • No payment is generated at the authentication stage.
  • The merchant calls the authorization API at the desired time to complete the final payment.

Payment Flow Overview

Checkout Integration

When the merchant's webpage calls the Hecto Financial checkout, the customer enters payment information and completes authentication directly in checkout. Once payment is complete, Hecto Financial delivers the result to the merchant server.

Buyer
Merchant
Hecto Financial
Issuer
11. Payment request on order page
1. Payment request on order page
22. Launch checkout
2. Launch checkout
33. Display checkout
3. Display checkout
44. Enter card info & authenticate
4. Enter card info & authenticate
55. Request authorization
5. Request authorization
66. Return authorization result
6. Return authorization result
77. Notify result (notiUrl)
7. Notify result (notiUrl)

Step Details

  1. 1Payment Request : The customer selects a payment method on the order form and clicks the "Pay" button.
  2. 2Launch Checkout : The merchant calls the Hecto Financial JavaScript SDK (SETTLE_PG.pay) to launch checkout.
  3. 3Checkout Displayed : The card information entry screen appears to the customer.
  4. 4Authentication : The customer enters card information and completes identity verification via the card issuer app or password.
  5. 5Authorization Request : Hecto Financial sends a payment authorization request to the card issuer.
  6. 6Authorization Result : The card issuer returns the authorization result to Hecto Financial.
  7. 7Result Notification : Hecto Financial delivers the payment result to the merchant server's notiUrl.
Please make sure to implement notiUrl.notiUrl is mandatory for checkout integration. Even if the customer abandons checkout midway or exits the browser, you can reliably receive payment results via notiUrl. Since nextUrl is for display purposes only, actual order processing logic must always be performed in notiUrl.

Checkout vs. Direct API

ItemCheckout IntegrationDirect API Integration
Card Data HandlingManaged by Hecto FinancialCollected directly by the merchant
Payment UIHosted checkout by Hecto FinancialMerchant can design their own UI
Supported Payment MethodsAuthenticated, non-authenticated, legacy-authenticatedNon-authenticated, legacy-authenticated, BillKey

API Integration

A method where payments are processed by calling the Hecto Financial API directly from the merchant server. The merchant collects card information directly without checkout and requests payment via server-to-server communication.

Buyer
Merchant
Hecto Financial
Issuer
11. Enter card info & pay
1. Enter card info & pay
22. Call payment API
2. Call payment API
33. Request authorization
3. Request authorization
44. Return authorization result
4. Return authorization result
55. Return API response
5. Return API response
66. Notify payment result
6. Notify payment result

Step Details

  1. 1Card Information Entry : The customer enters card information on the merchant's own payment screen.
  2. 2API Call : The merchant server calls the Hecto Financial payment API.
  3. 3Authorization Request : Hecto Financial sends a payment authorization request to the card issuer.
  4. 4Authorization Result : The card issuer returns the authorization result.
  5. 5API Response : Hecto Financial returns the payment result to the merchant server.
  6. 6Result Notification : The merchant notifies the customer of the payment completion status.
NOTE
notiUrl is not mandatory for API integration. This is because the payment result can be received directly in the API response. However, implementing notiUrl as well is recommended for handling exceptional situations such as network failures.

BillKey Payment

BillKey payment is a core feature for implementing recurring payments and subscription services. Register a card just once to receive a unique identifier called a BillKey, and all subsequent payments can be executed automatically using only that BillKey.

Buyer
Merchant
Hecto Financial
Card Issuer
11. Request card registration
1. Request card registration
22. Open card registration (BillKey) checkout
2. Open card registration (BillKey) checkout
33. Enter card info in checkout (zero-amount verification)
3. Enter card info in checkout (zero-amount verification)
44. Verify card validity
4. Verify card validity
55. Validation complete
5. Validation complete
66. BillKey issued
6. BillKey issued
77. Call BillKey payment API (at desired time)
7. Call BillKey payment API (at desired time)
88. Payment result response
8. Payment result response

Step Details

  1. 1Card Registration : The customer requests card registration.
  2. 2Open Registration Checkout : The merchant opens the card registration (BillKey issuance) checkout. It runs as a zero-amount verification with no actual charge.
  3. 3Enter Card Information : The customer enters card information in the checkout window.
  4. 4Card Validity Check : Hecto Financial verifies card validity with the card issuer.
  5. 5Validation Complete : The card issuer returns the validation result.
  6. 6BillKey Issued : Hecto Financial delivers the BillKey to the merchant. The merchant stores it for future use.
  7. 7BillKey Payment Call : The merchant uses the BillKey to call the payment API at the desired time.
  8. 8Payment Result Response : Hecto Financial returns the payment result.
NOTE
Here is a real-world example.When making the first payment, register the card (BillKey issuance), and after that, payments are automatically charged each month (BillKey payment).

Mobile Payment Integration

When integrating checkout in a mobile app, you will use a WebView.

Unlike a web browser, the WebView environment requires additional configuration for calling card issuer apps and returning after authentication is complete.

Key items to check:

  • AppScheme registration for calling card issuer apps
  • shouldOverrideUrlLoading function override for calling and returning from external apps
  • Verify WebView configuration differences per OS (Android/iOS)
NOTE

Please refer to the guide below for more details. The WebView Integration Guide provides detailed configuration instructions for Android and iOS.

Credit Card Cancellation

Payment cancellation supports both full cancellation and partial cancellation.

CategoryDescription
Full CancellationCancels the entire payment amount. Processed immediately as an authorization reversal.
Partial CancellationCancels only part of the payment amount. Processed as a partial capture cancellation, which typically takes 3 to 5 business days.
Cancellation DeadlineCancellation requests can be made within 1 year of the payment date.
NOTE

Why isn't partial cancellation processed immediately? Partial cancellation is processed by cancelling a portion of the amount as a capture cancellation while keeping the original authorization intact. It takes a bit longer than a full cancellation because it must go through the card issuer's capture processing procedure.

Pre-Integration Checklist

Before starting credit card payment integration, it is good to confirm the following in advance.

Merchant ID Related

  • Merchant IDs may be separated by payment type, such as authenticated payment, non-authenticated payment, and legacy-authenticated payment. Please confirm the payment methods you will use in advance and discuss with your sales representative.
  • The Merchant IDs for the test environment and production environment are different. Testing in the production environment will incur real charges, so always use the sandbox (testbed).

Other Notes

  • The BillKey validity period for credit card billing is the same as the card's expiration date.
  • Some corporate cards and prepaid cards may not be accepted depending on the business category.

Sales / Review Related

  • For inquiries about business category, review status, and merchant name displayed in the SMS after payment, please contact your sales representative.
  • Sales inquiries:

Credit Card Developer Documentation

💳

Standard Payment API

Basic card payment integration

➕

Card Registration (BillKey) Checkout

Register a card and issue a BillKey with zero-amount verification

🔄

Recurring (BillKey) Payment API

Automatic payment for subscription services

↩️

Cancellation API

Full cancellation and partial cancellation

💬

Need technical support?

Code Samples

HectoFinancial GitHub