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.
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.
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.
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.
각 단계 상세
- 1Payment Request : The customer selects a payment method on the order form and clicks the "Pay" button.
- 2Launch Checkout : The merchant calls the Hecto Financial JavaScript SDK (SETTLE_PG.pay) to launch checkout.
- 3Checkout Displayed : The card information entry screen appears to the customer.
- 4Authentication : The customer enters card information and completes identity verification via the card issuer app or password.
- 5Authorization Request : Hecto Financial sends a payment authorization request to the card issuer.
- 6Authorization Result : The card issuer returns the authorization result to Hecto Financial.
- 7Result Notification : Hecto Financial delivers the payment result to the merchant server's notiUrl.
결제창 vs API 비교
| 항목 | 결제창 연동 | API 연동 |
|---|---|---|
| Card Data Handling | Managed by Hecto Financial | Collected directly by the merchant |
| Payment UI | Hosted checkout by Hecto Financial | Merchant can design their own UI |
| Supported Payment Methods | Authenticated, non-authenticated, legacy-authenticated | Non-authenticated, legacy-authenticated, BillKey |
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)
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.
| Category | Description |
|---|---|
| Full Cancellation | Cancels the entire payment amount. Processed immediately as an authorization reversal. |
| Partial Cancellation | Cancels only part of the payment amount. Processed as a partial capture cancellation, which typically takes 3 to 5 business days. |
| Cancellation Deadline | Cancellation requests can be made within 1 year of the payment date. |
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:
Need technical support?
Code Samples
HectoFinancial GitHub