You can add KCP Direct Card Capture to your existing integration. The following instructions show only what you must add to your integration specifically for KCP Direct Card Capture.
If an instruction on this page corresponds with a step in the main integration guide, it includes a link to corresponding step of the main integration guide.
The additions you must make depend on the server-side flow that your integration uses:
Key implementation notes
Make sure that your implementation adheres to the following:
- Component only: drop-in and sessions are not supported. Use
checkout.create('scheme', ...)withkoreanAuthenticationRequired: true andcountryCode: KR. - All Korean-issued cards: the
kcp.cardTaxnoandkcp.cardPwdfields are required for all Korean-issued cards - domestic cards, and co-branded Visa, Mastercard, JCB, Diners, and UnionPay cards issued in Korea. Do not scope this tokorean_local_cardonly. - One-time payments: always include both
additionalDatafields. - Tokenization: include both fields on the first (shopper-present) transaction only. Omit them on subsequent recurring charges.
- Both fields together:
kcp.cardTaxnoandkcp.cardPwdare validated as a pair - sending one without the other returns a validation error. - No 3DS: this integration does not support 3D Secure. The KCP authentication fields serve as the alternative authentication mechanism mandated by Korean issuers.
- No liability shift: because 3DS is not used, this flow does not provide liability shift on chargebacks.
- Installments UI: the card component does not render an installments selector. Build and collect this in your own UI if you intend to offer installments.