Member Information Inquiry API

Retrieves prepaid service enrollment status and member details.

API Information

POST/v1/customer/info

Content-Typeapplication/json

테스트https://tb-mps-api.hectofinancial.co.kr/v1/customer/info

운영https://mps-api.hectofinancial.co.kr/v1/customer/info

Use Cases

NOTE

Required Before Member Registration

You must call this API to verify enrollment status before displaying the member registration or My Information screen.

Use Case	Description
Enrollment check	Verify that the user is not yet enrolled before calling the registration screen
Member number lookup	Retrieve the custNo required for subsequent API calls
Member status check	Check member status: active, locked, withdrawn, etc.

Request Parameters

타입 표기법

N숫자A영문H한글AN영문+숫자AHN영문+한글+숫자

예: AN(10) = 영문+숫자, 최대 10byte

└custNoAN(20)Alphanumeric, up to 20 bytes*Prepaid member number.

Prepaid member number.

*Unique prepaid member number assigned by Hecto Financial. Either custNo or custId is required.

└custIdAN(20)Alphanumeric, up to 20 bytesAES-256AES-256/ECB/PKCS5Padding + Base64Prepaid member ID.

Prepaid member ID.

*AES-256/ECB/PKCS5Padding encryption required. Either custNo or custId is required. Members who have cancelled the service can only be looked up by custNo.

└ciAN(20)Alphanumeric, up to 20 bytes*AES-256AES-256/ECB/PKCS5Padding + Base64Member CI value.

Member CI value.

*Member's unique CI value. AES-256/ECB/PKCS5Padding encryption required.

└midAN(20)Alphanumeric, up to 20 bytes*Merchant ID.

Merchant ID.

*Unique merchant ID assigned by Hecto Financial.

Response Parameters

타입 표기법

N숫자A영문H한글AN영문+숫자AHN영문+한글+숫자

예: AN(10) = 영문+숫자, 최대 10byte

└rsltCdAN(4)Alphanumeric, up to 4 bytes*Result code.0000

Result code.

0000: Success Other: Failure

└rsltMsgAN*Result message.Success

Result message.

rsltObj (Response Object)

└custNoAN(20)Alphanumeric, up to 20 bytes*Prepaid member number.2400001605

Prepaid member number.

└custIdAN(20)Alphanumeric, up to 20 bytes*Prepaid member ID.

Prepaid member ID.

*The member ID passed by the merchant when the member registered.

└midAN(20)Alphanumeric, up to 20 bytes*Merchant ID.M2471645

Merchant ID.

└custDivCdAN(1)Alphanumeric, up to 1 bytes*Customer division code.

Customer division code.

0: Anonymous 1: Named

└custStatCdAN(1)Alphanumeric, up to 1 bytes*Customer status code.

Customer status code.

N: Active D: Service cancelled W: Pending H: Dormant L: Locked K: KYC pending R: Registration rejected

└regDtAN(8)Alphanumeric, up to 8 bytes*Member registration date.20240701

Member registration date.

*yyyyMMdd format.

└regTmAN(6)Alphanumeric, up to 6 bytes*Member registration time.143025

Member registration time.

*HHmmss format.

└csrcRegNoDivCdAN(1)Alphanumeric, up to 1 bytesCash receipt registration number type.

Cash receipt registration number type.

1: Card 3: Business number 4: Mobile number

└csrcRegNoAN(50)Alphanumeric, up to 50 bytesAES-256AES-256/ECB/PKCS5PaddingCash receipt registration number.01011110000

Cash receipt registration number.

*실제 응답값은 AES-256 암호화된 값입니다. 복호화 후 사용하세요.

└kycKindCdAN(1)Alphanumeric, up to 1 bytesKYC type code.

KYC type code.

1: CDD 2: EDD

*For named members only. Null for anonymous members.

└kycExprDtAN(8)Alphanumeric, up to 8 bytesKYC expiry date.20250701

KYC expiry date.

*KYC expiry date for named members. yyyyMMdd format.

└hldLmtAmtAN(7)Alphanumeric, up to 7 bytes*Maximum holding amount.2000000

Maximum holding amount.

*Maximum prepaid balance the member can hold, based on member type.

Request Example

{
  "custNo": "2400001605",
  "ci": "AES-encrypted CI value",
  "mid": "M2471645"
}

Response Examples

Active Member

{
  "rsltCd": "0000",
  "rsltMsg": "Success",
  "rsltObj": {
    "custNo": "2400001605",
    "custId": "user123",
    "mid": "M2471645",
    "custDivCd": "1",
    "custStatCd": "N",
    "regDt": "20240701",
    "regTm": "143025",
    "csrcRegNoDivCd": "4",
    "csrcRegNo": "AES-encrypted number",
    "kycKindCd": "1",
    "kycExprDt": "20250701",
    "hldLmtAmt": "2000000"
  }
}

Locked Member

{
  "rsltCd": "0000",
  "rsltMsg": "Success",
  "rsltObj": {
    "custNo": "2400001605",
    "custId": "user123",
    "mid": "M2471645",
    "custDivCd": "1",
    "custStatCd": "L",
    "regDt": "20240701",
    "regTm": "143025",
    "hldLmtAmt": "2000000"
  }
}

Non-Enrolled User

{
  "rsltCd": "1001",
  "rsltMsg": "Member information does not exist."
}

Member Status Handling

Status	Code	Handling
Active	N	Normal service access
Locked	L	PIN must be reset from the My Information page
Service cancelled	D	New registration required
Pending	W	Registration in progress
Dormant	H	Dormancy must be lifted
KYC pending	K	KYC procedure must be completed
Registration rejected	R	New registration not available

Important Notes

Always verify that the user is not yet enrolled before displaying the registration screen.
If an enrolled member enters the registration screen, error code 103 is returned.
If a non-enrolled user enters the My Information screen, an error occurs.
When both custNo and custId are provided, custId is validated against the custNo.
Members who have cancelled the service can only be looked up by custNo.

Need technical support?

Code Samples

HectoFinancial GitHub