Features changed in version 1.1.8


The followings are the changes in javascript sdk 1.1.8 version used for Iamport payment integration. The use of CDN is recommended.

Applied KakaoPay mobile redirection

Unlike other PG services, KakaoPay executed the callbackFunc specified as the second argument when mobile payment was completed through IMP.request_pay(param, callbackFunc). Because of this, KakaoPay payment was able to apply the same code in PC and mobile environments.

However, there were occasional cases where KakaoPay apps were not properly called from Android’s built-in browser and certain versions of Android Chrome. (Iamport uses an iframe to execute callbackFunc at the time of payment completion, but it required extra handling for KakaoPay SDK working unexpectedly in the iframe)

Currently, KakaoPay SDK has stopped supporting iframe based payment, so Iamport will also switch to the redirect method instead of the iframe in accordance with the KakaoPay policy.

Starting from 1.1.8, page redirection is triggered when paying with KakaoPay mobile. When payment is completed, like other PG companies, m_redirect_url parameter is redirected to the specified URL. (m_redirect_url parameter is required for mobile payment)

(On-demand) Add Naver Pay pop-up interface and change the default value

When a payment is requested, the (on-demand)NAVER Pay starts in a pop-up window (new tab) only when popup : true option is explicitly specified.

  • version >= 1.1.8
    • PC environment: The default is a redirect from current page, and it proceeds with the payment in the popup window (new tab) only when popup : true is set.
    • Mobile environment: The default is a redirect from current page, and it proceeds with the payment in the popup window (new tab) only when popup : true is set.
  • version < 1.1.8
    • PC environment: proceeds in a pop-up window (new tab) (regardless of the popup parameter)
    • Mobile environment: proceeds with the current page redirection method (regardless of the popup parameter)


To avoid issues such as popup blocking by browsers, Naver Pay recommends using page redirection. Therefore, the page redirection is the default method for both PC and mobile environments, and the popup window is used only when the merchant needs it.

Redirection support for Eximbay

Previously, payment was always made through a popup window when paying with Eximbay, but since version 1.1.8, if the merchant requests it, it supports the payment with the redirect method by explicitly specifying popup : false option.
  • version >= 1.1.8
    • PC/Mobile: The default is to use a popup window, and it uses the redirect method for the payment only when popup : false is set.
  • version < 1.1.8
    • PC/Mobile: proceeds with a popup window method regardless of the popup parameter


Since it is common not to allow a new window when making a payment with WebView in mobile apps, we support redirection for the smooth payment in WebView environment.

For Eximbay, unlike other PG companies, the pop-up window method was the default, so the redirection method was added in consideration of existing users.

Support multiple PGs to use more than one identity authentication setting

Previously, only Dana-Mobile authentication was provided as the authentication method. With the addition of the Inicis-Credit card authentication, it also supports multiple PGs for mobile authentication so that both can be used. In addition, pg : danal.{Danal CPID} multiple PG calling methods are supported even If you want to use the Danal-Mobile authentication on each site, while obtaining more than two CPIDs.
    pg: "danal", // danal or danal.{Danal CPID}, other parameters are omitted below
  }, function(rsp) {
    if ( rsp.success ) {
      // authentication succeeded and pass imp_uid, merchant_uid (rsp.imp_uid, rsp.merchant_uid)
    } else {
      // authentication failed and abort

Bug fix: White screen appears when the browser Back button is pressed while payment is being processed by redirection in iPhone Safari

A white screen appears in Safari if it returns to the previous page with Back button. It was identified and fixed as a bug due to the behavior in Safari restoring and outputting the DOM before redirection. (Applies to all PG services with redirection method)