South Korea iOS entry card: keep each wallet route in its own test row

South Korea’s Apple payment list supports a concrete wallet test matrix. It does not support a claim that one wallet is preferred by mobile-game payers. The first production task is to distinguish available routes, account eligibility and the path that a tester actually completed.

What the official record establishes

Apple’s service-availability record includes the App Store in its South Korea section. Its payment-method record lists kakaopay, Naver Pay, PAYCO and Toss Pay. These examples are not an exhaustive list: the live source’s eligibility notes still apply, and the page says methods can change. Storefront availability does not establish that your particular game is approved, distributed or purchasable there.

The first test to run

Use separate rows for the selected wallet paths and any carrier-billed observation. Keep result labels consistent: method unavailable, purchase cancelled, purchase successful and entitlement missing are different outcomes. Only the final two concern a completed charge, and they need different follow-up evidence.

Localise the observed journey

Review Korean reward descriptions, product names and error recovery in the release candidate. Ask the reviewer to follow the same purchase script used in other territories, then record local wording problems separately. Comparable scripts improve investigation; they do not make the underlying player populations interchangeable.

Keep the decision tied to evidence

Use the editable launch checklist and CSV evidence matrix to keep documented availability separate from actual tests. Both include explicit untested states. The country card supplies no CPI, ROAS, payer-share estimate or legal clearance. Local expert review, game-specific distribution checks and real account observations remain outstanding.

Before a paid test, define the campaign identifiers, install cohort, offer event and purchase outcome you intend to reconcile. Inspect a permitted test transaction end to end, then preserve the raw event references. A successful walkthrough establishes implementation evidence for that case; it cannot establish campaign incrementality or expected acquisition economics.

Related reading: South Korea: PC-heritage IP and mobile UA and Text-free playable design for global campaigns.

No observed campaign or purchase results are claimed.