Search...
APIJSLog inGet started in sandbox
Airwallex logo
Home
Platform APIs
Connected Accounts
Accounts
Payments
Billing
Transactional FX
Payouts
Issuing
Back to home
OverviewChoose your payments solutionGet started with payments
Supported currencies
Online payments
Online payments overviewPayment Method Onboarding RequirementGet started with online paymentsHosted Payment Page
Drop-in Element
Embedded Elements
Card Element
Split Card Element
Korean Local Cards - Split Card Element
Legacy Embedded Elements
Mobile SDK
Plugins
Native API
Automatic Currency ConversionMulti-Currency Pricing API
Invoice integrations
Tax filing

Korean Local Cards - Split Card Element

Note

Korean Local Cards is currently available in beta launch stage. Please reach out to your Airwallex account manager or [email protected] if you'd like to join the beta client list.

The Korean Locard Cards - Split Card Element allows you to embed individual input fields (Korean Card Number JS, Korean Card Expiry Date JS, Korean Card Password First-2 Digits JS and Korean Card Identifier JS) on your checkout page to securely collect card details and submit these details to Airwallex to process a payment with Korean local branded cards. In comparison to Split Card Element , it is customized to cater the special data fields that are only required by the Korean local card companies during checkout.

Checkout flow

At the current stage, we only offer one-off / single payment experience for Korean Local Cards, please see the details in Guest user checkout.

Supported features

Note

Note: Korean Local Cards does not support 3D secure authentication. For consumer cards, Korea’s local card companies rely on the cardholder's date of birth and card PIN first-2 digits to determine whether the shopper is the cardholder itself.

You can use the following features in your Korean Locard Cards - Split Card Element integration.

Style and appearance customization

Style

Provide base styling for the iframe using CSS properties. You can also customize the width and height of a pop-up overlay.

JavaScript

Localization

You can configure the Element to display localized text for payment fields based on the locale specified in init(). If no locale is specified, the browser's locale will be used, if it is supported by Airwallex.js. For a list of supported locales, see locales JS.

If the browser's locale is not supported, the Element will default to en.

Device fingerprinting

Device fingerprinting uniquely tracks and identifies devices used for transacting on your shopping site, increasing your protection from fraud. Airwallex.js automatically handles device fingerprinting, so no additional integration is needed.

Payments for platforms

You can accept payments from Korean local cards as a platform via the Korean Local Cards - Split Card Element. Example platforms include marketplaces, SaaS platforms, on-demand service providers. For more information on payments for platforms with Airwallex as an acquirer, see Airwallex payment gateway. To use Connected Account information to process the payment, e.g., statement descriptor displayed on the shopper's credit card or bank statement, provide connected_account_id in Create a Payment Intent API.

Fraud protection

You can provide specific data fields in Create a PaymentIntent API and Confirm a Payment Intent API endpoints to significantly improve Airwallex's fraud protection performance, ultimately boosting conversion rates and minimizing fraud risk. For more information, see Enhance fraud protection with comprehensive payment data.

FAQ

What card schemes can I accept using Korean Local Cards - Split Card Element?

You can accept credit and debit cards issued by Korea’s 9 major local card companies in the market:

  • BC
  • Hana
  • Hyundai
  • KB
  • Lotte
  • NH
  • Samsung
  • Shinhan
  • Woori

How do I display the cardholder name field for a Korean Local Cards - Split Card Element?

You can render a Cardholder Name input field on your checkout page alongside the Korean Local Cards - Split Card Elements. The cardholder name is not mandatory to confirm and complete a payment.

Was this page helpful?