KICC via Switch KICC (Korea Information & Communication Company) is a payment service provider in Korea that allows you to collect card payments for a variety of currencies. This guide is intended to help you implement KICC via Switch based on your preferred integration workflow.

Services and compatibility


Supported payment types	Card
Supported transaction types	Sale (saved card token) ( API ) Refund (partial and multiple) ( API )
Supported processing currencies	BYN, KRW, KZT, MXN, PHP, RUB, TRY, TWD
3D Secure 1.x supported	No
3D Secure 2.x supported	No
External 3D Secure supported	No
Installments supported	Yes

Gateway-specific information

KICC supports sale transactions as well as partial, multiple, or full refunds.

For Kount with KICC, only Success, Decline, and Error statuses are available. Review is not supported. For additional information about Kount, see Kount verification.

The installment feature for recurring billing is supported. Use a period of 2-12. The amount must be at least 50000 and the transaction currency must be KRW. For additional information, see Recurring billing overview.

The following are not supported with KICC via Switch:

Auth-only and Capture
3D Secure
Void

Configuration

Apart from working with Integrations Support to add KICC via Switch as a connection, you do not need to do any other configuration steps.

Required fields

In addition to the default required field of data.amount, KICC requires the following fields to process a transaction with the Run card transaction or Run card transaction with iframe endpoint.

For many of the fields, when included in the Create one-time-use token, Save card token, or Save card token with iframe endpoint. the field is stored in the card token and automatically gets sent with the Run card transaction request without needing to explicitly specify it. For more information about this possibility, see the What data is saved with tokens? topic.

Required Field	Required?	Description
`card.securityCode`	Yes	The numeric code printed on the card for enhanced security. When included in the Save card token or Save card token with iframe request, Nexio caches the value for up to 24 hours. Therefore, if you save the card token and then submit a transaction with that card token more than 24 hours later, you need to recapture the security code.
`data.amount`	Yes	The transaction amount. For KRW, the value must be a whole number. For installments, this value must be a minimum of 50000 KRW.
`data.currency`	Yes	The three-character ISO currency code for the transaction. For KICC, supported currencies are BYN, KRW, KZT, MXN, PHP, RUB, TRY, and TWD. For installments (recurring payments), only KRW is allowed. If you do not include this parameter, the system uses the default of `USD`. Therefore, if your merchant account does not support USD, you will get an error response.
`card.businessNumber`	Conditional	The phone number associated with the business card. It is a string containing 10 digits. This parameter is required when `card.classification` is `business`.
`card.classification`	Conditional	The card classification. The value must be either `personal` or `business`. This field may be required, depending on the configuration of the merchant account with KICC.
`card.password`	Conditional	The password associated with the business card. It is a string containing two digits. This parameter is required when `card.classification` is `business`.
`data.customer.billToAddressOne`	Conditional	The street address for the customer. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.billToCity`	Conditional	The city for the address record. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.billToCountry`	Conditional	The two-character (Alpha-2) ISO country code. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.billToPhone`	Conditional	The billing phone number. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.billToPostal`	Conditional	The postal code on file. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.billToState`	Conditional	The state or province on file with the payment provider. (If in the US, this must be the two-character state abbreviation). This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.birthDate`	Conditional	The customer's date of birth. Use any of the following formats for the date: Four-digit year, two-digit month and day, separated with hyphens: YYYY-MM-DD. For example, `2001-08-26`. ISO-8601 date expressed in UTC. For example, `2001-08-26T13:35:00Z`. UNIX date (as an integer representing seconds). For example, `998854500`. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.email`	Conditional	The customer's email address. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.firstName`	Conditional	The customer's first name, as it appears on the card. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.lastName`	Conditional	The customer's last name, as it appears on the card. This field may be required, depending on the configuration of the merchant account with KICC.
`data.customer.orderNumber`	Conditional	The order number. This field may be required, depending on the configuration of the merchant account with KICC.

Testing data

Use the following test card information to test your KICC configuration. If you specify a card classification of business, you must also include any 10-digit string for the business number and any 2-digit string for the password.

For testing installments, use only the Visa test card.

Brand	Card number	Expiration date	Security code	Cardholder name	Transaction result
Mastercard	5454545454545454	Any	Any	Any	Success
Visa	4119041212341238	Any	Any	Any	Success

Status workflows

The status of a successful transaction with KICC varies, depending on the options you choose.


Sale	Successful capture transactions will have the following statuses: pending* or authorized settled
Refund	Successful refund transactions will have the following statuses: pending* or authorized settled

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the appropriate transactionStatus table).

If you have any additional questions or feedback, contact us.