Full Integration Flow

SecurePay Prepaid is a service that uses both a UI screen (member registration/management) and an API server (balance spend/top-up/inquiry).

Overall Flow

Customer

Merchant

Hecto Financial

11. Request service

1. Request service

22. Call member registration screen (GET /identity)

2. Call member registration screen (GET /identity)

33. Display member registration screen

3. Display member registration screen

44. Identity verification and information entry

4. Identity verification and information entry

55. Return registration result (returnUrl)

5. Return registration result (returnUrl)

66. Call balance spend/top-up/inquiry API

6. Call balance spend/top-up/inquiry API

77. Return processing result

7. Return processing result

NOTE

One-Time Member Registration

Member registration (steps 2–5) is performed only once. After registration, you can immediately use balance spend, top-up, inquiry, and other features via the API.

Step 1: Member Registration Screen (UI)

The merchant calls the member registration screen provided by Hecto Financial.

Item	URL
Sandbox	`https://tb-mps.hectofinancial.co.kr/identity`
Production	`https://mps.hectofinancial.co.kr/identity`
HTTP Method	`GET`

Required Parameters

Parameter	Description
`mId`	Merchant ID
`mCustId`	Prepaid member ID
`ciEnc`	Customer CI (AES-256/ECB/PKCS5Padding, Base64 encoded)
`returnUrl`	URL to redirect to after registration completes

UI Integration Docs

Member Registration Screen

New prepaid member registration UI integration

My Information Screen

Existing member information management UI integration

Step 2: Balance Spend / Top-up / Inquiry API

After member registration, the merchant server calls the API directly.

Item	Value
Sandbox	`tb-mps-api.hectofinancial.co.kr`
Production	`mps-api.hectofinancial.co.kr`
HTTP Method	`POST`
Content-Type	`application/json;charset=UTF-8`

pktHash Generation Rules

API Common Signature Generation`pktHash`

필드명	파라미터
Prepaid member number	`custNo`
Merchant ID	`mchtId`
Merchant transaction reference number	`mTrdNo`
Transaction amount (plaintext)	`trdAmt`
Hash key	`hashKey`

SHA256(custNo + mchtId + mTrdNo + trdAmt(plaintext) + hashKey)

NOTE

Void API Signature Composition

The Spend Void and Top-up Void APIs use orgTrdNo + orgTrdDt instead of trdAmt: custNo + mchtId + mTrdNo + orgTrdNo + orgTrdDt + hashKey

Key APIs

Feature	URI
Balance inquiry	`/v1/wallet/balance`
Spend	`/v1/wallet/use`
Spend void	`/v1/wallet/use/cancel`
Top-up	`/v1/approval/charge`
Top-up void	`/v1/approval/charge/cancel`
Withdrawal	`/v1/money/withdrawal`
Transaction history inquiry	`/v1/trade/list`