Before buying a Korea concert ticket, compare the attendee’s passport name with the ticket account, fanclub membership and booking name. Use the spelling shown in the passport’s Latin-alphabet name fields unless the ticket seller gives a different event-specific instruction. If anything differs, contact the designated seller before purchase or before the correction deadline; do not assume venue staff can fix it at the door.
Make one name record before you register
| Record | What to compare | Risk if different |
|---|---|---|
| Passport | Latin-alphabet family and given names, date of birth | Identity check may fail |
| Ticket account | Member name and verified identity | Booking or collection may be restricted |
| Fanclub membership | Membership holder and linked account | Presale verification may not link |
| Booking | Purchaser or attendee shown in My Ticket | Will call or entry may be denied under the event rule |
YES24 Global’s FAQ says will-call collection generally requires a physical valid passport and booking confirmation, warns that a different account name can cause trouble, and tells readers to follow the individual show page first. The CUTIE STREET Live in Korea 2026 notice went further for that event: the YES24 account had to be in the attendee’s own name, and its fanclub-presale instructions connected passport identity, membership and ticket purchase. Do not apply that notice’s entire document list to another concert.
Check before you click purchase
- Read the exact event’s identity and collection section.
- Open the passport and compare every account involved. Check spacing, hyphens, omitted middle names and reversed family/given-name order.
- Confirm that eKYC, if required, shows a completed status in the same ticket account.
- Verify fanclub membership only through the ticket route named by the organizer.
- After booking, open the order and confirm which name the seller will use for collection or entry.
If your name is shortened or out of order
Take screenshots of the account profile, verified status and booking, but do not post passport images publicly. Contact the ticket seller through its official account inquiry and quote the order number and event. Ask whether the displayed difference is acceptable and whether an account or booking correction is permitted. If fanclub verification is also involved, ask which service has to be corrected first. Do not delete and recreate accounts, transfer a membership or cancel a scarce ticket until official support explains the effect.
Bring the evidence named for your event
A passport is a common requirement for foreign attendees, but the exact acceptable ID, whether a copy is allowed, and whether membership proof or a payment card is required can differ. Build your collection pack from the event notice, not from a fan checklist. For the final day-of sequence, use the will-call guide.
What a matching name does not guarantee
Name alignment does not prove that a ticket is authentic, transferable or sufficient for entry. Staff may also check age, fanclub status, the original booking record or another document named in the event notice. Only the organizer and designated ticket seller can decide whether a specific variation is acceptable.
Do a separate check for every person in a group order
Group bookings create a second problem: the purchaser field and the individual attendee fields may not work the same way. Read whether the event names only the purchaser, requires every attendee’s ID, or restricts collection to the account holder. Do not copy one passport spelling into all attendee fields or assume companions can enter when the purchaser is absent.
Create a private note for each traveler with the passport spelling, ticket-account email, membership holder, performance date and seat. Store only what the group needs and never circulate passport scans in a group chat. If one person cannot attend, ask the organizer whether the companion tickets remain valid before travel. A family relationship or shared surname does not automatically override a purchaser-only rule.
The U-KNOW PROJECT 26 notice is another event-specific example connecting the fanclub member, ticket purchaser and actual attendee. It reinforces the need to inspect your own event’s matching rule before a group purchase.
Last checked: August 24, 2026. Recheck the event’s ID wording before purchase and again 48 hours before collection.
Build one immutable identity row before registration
| System | Value to capture | Authority | Correction decision |
|---|---|---|---|
| Passport | Latin family name, given names, date of birth and expiry | Physical valid passport | Renew or use only the document the event accepts |
| Ticket account | Displayed member name and verified fields | Seller account/profile | Use the seller’s published support route before purchase |
| Membership | Holder name, membership number and linked account | Official fanclub/community record | Correct before the event’s verification deadline |
| Booking/attendee | Name shown on order or My Ticket | Completed seller order | Do not assume venue staff can rewrite it |
Do not invent a universal spacing or middle-name rule
The safe comparison is between the physical passport’s Latin fields and every exact account used by the named event. Spacing, hyphens, order and omitted names matter only as the seller or event defines them. Do not silently normalize a mismatch because another concert accepted it.
What current YES24 guidance establishes
YES24 Global’s FAQ generally calls for a physical valid passport plus booking confirmation at will call, warns that a different account and passport name can cause collection trouble, and gives the individual show page priority. Its verified fields—such as name and date of birth—may not be editable after identity verification, which makes pre-submission review consequential.
Use event notices as narrow contracts
The CUTIE STREET event notice and the U-KNOW event notice connect particular account, membership, purchaser or attendee fields for their own sales. Extract the named people, deadlines, documents and route from the exact notice. Never carry a document list or no-correction rule into a different event without its own wording.
Stop conditions before payment
- The event requires the attendee’s name, but the order screen identifies only another person.
- The ticket account is already verified to a different passport or immutable identity.
- Membership verification completed on a different language route or seller account than the sale route.
- The seller has not answered a material mismatch before the published correction or sale deadline.
Editorial boundary: this owner covers the exact identity string and its connection across passport, ticket account, membership and booking. It does not promise entry, define every venue’s ID list or troubleshoot biometric capture. Official seller and event guidance was rechecked on August 24, 2026.