010 Virtual Account

A virtual account service based on mobile phone numbers (010-XXXX-XXXX). A deposit-only virtual account in 010 format is issued after verifying the customer's phone ownership.

Supported Payment Methods

Payment Method	Description	Checkout Support	API Support
Checkout Issuance	Virtual account issued after phone ownership verification in the checkout	O	-
API Issuance	Phone verification and virtual account issuance directly via API	-	O

010 Virtual Account Developer Docs

Checkout (UI)

Virtual account issuance via checkout

Phone Verification API

Phone ownership verification request/confirm

Issuance API

Virtual account number issuance

Issuance Cancel

Cancel virtual account before deposit

Understanding Payments

Checkout (UI) Method

In the checkout method, phone ownership verification (S1/S2) and issuance (A4) are handled automatically.

Buyer

Merchant

Hecto Financial

Kbank

11. Checkout call

1. Checkout call

22. Phone ownership verification request (SMS)

2. Phone ownership verification request (SMS)

33. Enter verification code

3. Enter verification code

44. 010 virtual account issuance request

4. 010 virtual account issuance request

55. Virtual account number issued

5. Virtual account number issued

66. Issuance webhook sent (notiUrl)

6. Issuance webhook sent (notiUrl)

77. Issuance result displayed (nextUrl)

7. Issuance result displayed (nextUrl)

88. Customer deposit

8. Customer deposit

99. Deposit confirmed

9. Deposit confirmed

1010. Deposit webhook sent (notiUrl)

10. Deposit webhook sent (notiUrl)

NOTE

Two Webhook (notiUrl) Deliveries

Virtual account transactions deliver two webhooks in total: an issuance webhook (outStatCd: 0051) and a deposit webhook (outStatCd: 0021). Both webhooks must be handled. All DB processing must be performed in notiUrl; use nextUrl only for displaying result screens.

API Method - B2C

If not using the checkout, the merchant server must call the APIs directly in the following order.

Buyer

Merchant Server

Hecto Financial

Kbank

11. Payment request (enter phone number)

1. Payment request (enter phone number)

22. Phone ownership verification request (S1)

2. Phone ownership verification request (S1)

33. SMS verification code sent

3. SMS verification code sent

44. Enter verification code

4. Enter verification code

55. Phone ownership verification confirm (S2)

5. Phone ownership verification confirm (S2)

66. Virtual account issuance request (A4)

6. Virtual account issuance request (A4)

77. Kbank virtual account issuance

7. Kbank virtual account issuance

88. Issuance result

8. Issuance result

99. Issuance webhook sent (notiUrl)

9. Issuance webhook sent (notiUrl)

1010. Customer deposit

10. Customer deposit

1111. Deposit confirmed

11. Deposit confirmed

1212. Deposit webhook sent (notiUrl)

12. Deposit webhook sent (notiUrl)

B2C API Call Order

Step	API	bizType	Description
1	Phone Ownership Verification Request	S1	Send SMS verification code to customer's phone
2	Phone Ownership Verification Confirm	S2	Verify the code entered by the customer
3	Virtual Account Issuance	A4	Issue 010-format virtual account number

NOTE

mchtTrdNo Must Be Identical

The mchtTrdNo (merchant order number) used in S1 (verification request) and A4 (issuance) must be identical.

API Method - B2B

For B2B use, call the Duplicate Amount Check (A7) API before issuance to prevent duplicate issuance.

Buyer

Merchant Server

Hecto Financial

Kbank

11. Payment request (enter phone number)

1. Payment request (enter phone number)

22. Phone ownership verification request (S1)

2. Phone ownership verification request (S1)

33. SMS verification code sent

3. SMS verification code sent

44. Enter verification code

4. Enter verification code

55. Phone ownership verification confirm (S2)

5. Phone ownership verification confirm (S2)

66. Duplicate amount check (A7)

6. Duplicate amount check (A7)

77. Virtual account issuance request (A4)

7. Virtual account issuance request (A4)

88. Kbank virtual account issuance

8. Kbank virtual account issuance

99. Issuance result

9. Issuance result

1010. Issuance webhook sent (notiUrl)

10. Issuance webhook sent (notiUrl)

1111. Customer deposit

11. Customer deposit

1212. Deposit confirmed

12. Deposit confirmed

1313. Deposit webhook sent (notiUrl)

13. Deposit webhook sent (notiUrl)

B2B API Call Order

Step	API	bizType	Description
1	Phone Ownership Verification Request	S1	Send SMS verification code to customer's phone
2	Phone Ownership Verification Confirm	S2	Verify the code entered by the customer
3	Duplicate Amount Check	A7	Check for existing issuance at the same amount (required for B2B)
4	Virtual Account Issuance	A4	Issue 010-format virtual account number

Duplicate Amount Check Required for B2B

For B2B service, requesting A4 (issuance) without A7 (duplicate amount check) will result in a VA03 error if a virtual account with the same amount has already been issued.

Differences Between B2C and B2B

Category	B2C	B2B
Deposit Expiry	Up to 27 days	Up to 3 years
Bank Statement Name	Fixed as "010가상계좌"	Format: "010_CustomerName"
Virtual Account Number	Phone number	Phone number + 3 digits
Transaction Amount	Actual payment amount	1 KRW or more (unrelated to actual deposit amount)
Duplicate Amount Check (A7)	Not required	Required

Post-Deposit Processing

After a virtual account is successfully issued and the customer deposits to that account, Hecto Financial sends a deposit webhook (notiUrl) to your server.

Issuance Cancel (A2): Cancels the issued virtual account before customer deposit.
Refund (C0): Processes a refund after customer deposit. (Requires separate refund service registration)

Key Features and Characteristics

Feature	Description
Phone-Based	The customer's 010-format phone number is used as the virtual account number
Phone Ownership Verification Required	Account is issued after identity verification via phone ownership verification
Kbank Integration	Virtual account service through Kbank (089)
Deposit Expiry Setting	B2C: up to 27 days, B2B: up to 3 years

Suitable for These Services

Identity-Verified Payments: Services requiring identity confirmation via phone ownership verification
Easy Deposits: Accounts in the easy-to-remember 010 number format
B2B Transactions: Business-to-business transactions requiring long deposit deadlines (up to 3 years)

Important Notes

Caution When Testing in Production

Costs incurred when testing in the production environment are borne by the merchant. All testing must be completed in the sandbox environment before using the production environment.

Conditions for Skipping Phone Ownership Verification

Sending both cphoneNo (phone number) and mchtCustId (merchant customer ID) together allows skipping phone ownership verification.

Deposit Expiry Date Setting

If no deposit expiry date (expireDt) is provided, it is automatically set to +10 days from the transaction date.
B2C: Maximum 27 days from the current date
B2B: Maximum 3 years from the current date

Bank Statement Name

B2C: Fixed as "010가상계좌"
B2B: Format "010_CustomerName"

Integration Information

Checkout (UI) URI

Environment	URL
Sandbox	`https://tbnpg.settlebank.co.kr`
Production	`https://npg.settlebank.co.kr`

API URI

Environment	URL
Sandbox	`https://tbgw.settlebank.co.kr`
Production	`https://gw.settlebank.co.kr`

Security Information

Encryption Method (AES-256)

Parameters containing personal information must be encrypted before transmission.

Category	Details
Algorithm	AES-256/ECB/PKCS5Padding
Encoding	Base64 Encoding
Target Fields	Transaction amount, customer name, phone number, email, etc.

Tamper Prevention (SHA-256)

A hash value is generated to prevent tampering with request data.

Category	Details
Algorithm	SHA-256
Encoding	Hex Encoding

Test Key Information

Sandbox-Only Information

The keys and merchant IDs above are for use in the sandbox environment only. In the production environment, use the keys and merchant IDs separately issued by Hecto Financial.

Full API List

Category	API	Description	bizType
Checkout Integration	Issuance (Standalone Checkout)	Virtual account issuance via UI checkout	-
Checkout Integration	Issuance (Integrated Checkout)	Virtual account issuance via integrated checkout	-
API Integration	Phone Ownership Verification	SMS verification code send request	S1
API Integration	Phone Ownership Verification Confirm	SMS verification code verification	S2
API Integration	Duplicate Amount Check	Duplicate issuance check at same amount (required for B2B)	A7
API Integration	Issuance	Virtual account number issuance	A4
API Integration	Issuance Cancel	Cancel issued virtual account (before deposit)	A2
API Integration	Refund	Process refund for completed deposit	C0
Webhook	Deposit Webhook	Webhook delivered upon customer deposit	B1
Test	Deposit Test	Deposit simulation in sandbox environment	F1

010 Virtual Account

Supported Payment Methods