Skip to main content

FAQ

Development Environment​

Q. Does KICC provide test payment methods (cards or accounts) for development?

A. We do not provide dedicated test cards or accounts. You must use a real card or account number. In the development (test) environment, actual payments are not processed; instead, they are provided in a "Simulated Approval" format.

Important Precautions
  • For Affiliate Simple Payments (Kakao Pay, PAYCO, SSG Pay, Toss Pay Money, Naver Pay Money, Mobile Carrier Billing), actual charges may occur during testing. You must cancel the transaction after testing. (Uncancelled test transactions are collectively voided at 23:00 on the same day.)
Q. How can I test virtual account deposits in the test environment?

A. You can simulate deposits via the Virtual Account Deposit Simulation page. To receive deposit notifications (webhooks), please refer to the Webhook Guide. You must register your Callback URL in the Merchant Admin Console > Notification Settings menu.

Q. How can I obtain the Merchant ID (MID) and Secret Key for the production environment?

A. Required IDs and keys vary depending on the service:

  • Online Payment Service: Issued after document submission during the Service Onboarding Process.
  • Simple Payment Service: Please request the Service ID and Secret Key from your designated sales representative.
  • VAN Payment Service: You can use your existing Merchant ID without needing a separate issuance.

Online Payment​

Q. Where can I check transaction details processed in the test environment?

A. You can check them in the Test Merchant Admin Console. Please contact your sales representative to obtain the login ID and password for the test console.

Q. How do I get a Test Merchant ID (MID)?

A. Go to Test MID Application Page You will receive a Secret Key along with your Test MID upon application.

Q. What is the process for testing credit card payments in the production environment?

A. Once your test integration is complete, you must request a review from the card issuers. Issuers will verify if the payment window functions correctly on your actual shopping mall site or app.

It typically takes 5 to 10 business days after KICC submits the review request to the issuers. You can track the progress at EasyPay Website > Service Application/Inquiry.

Q. Can I show only specific cards or simple payment providers in the payment window?

A. Yes, you can configure this in the Merchant Service Settings or by passing specific parameters during the Payment Registration API call. For service settings, contact your KICC sales representative. For parameter-based configuration, follow these steps:

  1. Specify Payment Method Type (payMethodTypeCode) Set this to Credit Card (11) in the registration request.
  2. Specify Display Area (payMethodInfo > cardMethodInfo > displayArea) Set this to CARD (Credit Card) or SPAY (Simple Payment).
  3. Specify Specific Provider
    • Card List (cardInfoList): List specific card codes to display only those issuers.
    • Simple Payment List (usedSpayCode): List specific affiliate service codes to display only those providers.
Q. How can I offer interest-free installments only for specific cards?

A. You can apply this via the API parameters during Payment Registration:

  1. Enable Interest-free (payMethodInfo > cardMethodInfo > setFreeInstallment) Set this value to Y.
  2. Define Card List (payMethodInfo > cardMethodInfo > cardInfoList) Specify the card code (cardCd) and the allowed interest-free months (freeInstallmentMonthList) for each card.
Q. Why do I see error WN14 "This transaction was previously failed"?

A. Cause: This occurs when you attempt to invoke a payment window URL that has already failed during a previous authentication attempt. Solution: You must request a new payment window URL via the Transaction Registration API.

Simple Payment​

Q. How do I get a Service ID for the test environment?

A. Contact the merchant support department to request a Test Service ID. Include the issued Service ID in the Authorization header of your API requests. Go to HTTP Header Authentication Guide

For production Service IDs, use the same contact channel.

Q. Are there test cards or bank accounts for the simple payment test environment?

A. Only Samsung Card is supported for registration in the test environment. Set the first 6 digits to 9410-09 and fill the remaining fields with random values. For bank accounts, all account numbers are accepted.

Q. Account verification fails in the test environment.

A. Verification codes are not sent via SMS in the test environment. Simply enter 1234 as the verification code to proceed.

VAN Payment​

Q. How can I test EasyTalkPay in the test environment?

A. You can test by obtaining a VAN Terminal ID (TID) from your sales representative. Only Samsung Card is supported in the test environment.

Q. Is EasyTalkPay available in a PC environment?

A. Card issuer App-Card payments are only available on mobile devices. If a customer needs to pay via PC, please provide a payment URL via SMS/KakaoTalk or display a QR code so they can open it on their mobile phone.

Q. Error 'Merchant registration required' occurs during EasyTalkPay approval.

A. This occurs when EasyTalkPay is not registered for the terminal you are using. Please request EasyTalkPay terminal registration for that specific TID through your sales representative.

Global Payment​

Q. I received "NO_AUTH" as a response message from WeChat Pay.

A. This error may occur if the merchant is not registered with WeChat Pay. Please verify your registration status with your KICC sales representative.

Troubleshooting​

Q. How do I resolve error R108 "Duplicate request"?

A. Cause: This is caused by reusing a shopTransactionId that has already been used. Solution: Ensure that the shopTransactionId is unique for each approval and cancellation request within the same day (00:00 - 24:00).

Q. Why do I get error R114 "Message authentication failed"?

A. Cause: This occurs when the msgAuthValue is incorrectly generated during a cancellation (refund) request. Solution: Ensure the plain text is constructed according to the signature rules and encrypted with your issued Secret Key. Refer to the specific API guide or the Message Authentication Glossary.

Q. How do I resolve error R200 "Unregistered merchant"?

A. Cause: This occurs when the mallId (Merchant ID) used in the request is not registered in the target environment (Production or Test). Solution: Use the Production MID for the production environment and the Test MID for the test environment.