Configure the KCP gateway integration with the Payment Form SDK
Learn how to configure the NHN KCP gateway integration in the Payment Form SDK to accept credit card payments, KakaoPay, and PAYCO.
- A KCP gateway instance must be configured in your Zuora tenant before you initialize the Payment Form SDK.
- Your integration must implement the
createPaymentSessioncallback. This callback is required for the gateway-hosted card form and the PAYCO button component. The Payment Form SDK returns a configuration error if this callback is absent when either component is initialized. - Your integration must implement the
onCompletecallback to receive the payment result.
The KCP gateway integration supports three payment method types in the Payment Form SDK: credit card, KakaoPay, and PAYCO. Each type uses KCP's hosted payment window to collect payment details. For credit card payments, the Payment Form renders a single button instead of card input fields. When a customer clicks the button, KCP's hosted payment window opens and collects the card details directly. KakaoPay and PAYCO each render as branded button components that follow the same hosted-component pattern.
Card data is collected and encrypted entirely within KCP's hosted window. The Payment Form SDK does not receive or transmit raw card numbers.
When configuration is complete, the Payment Form SDK renders the appropriate component for each KCP payment method type. The credit card form displays a single button that opens KCP's hosted payment window. The KakaoPay and PAYCO components display their respective branded buttons. On successful payment, the onComplete callback receives the payment method ID and payment ID.
If the KCP SDK does not load within 10 seconds, the SDK logs a warning and reports the failure through onComplete. Verify that the KCP SDK URLs are reachable from your environment and that no network or CSP policy blocks the script load.