Question: Is AC blocking my TK FFP?
#1
Original Poster
Join Date: Sep 2007
Location: YYZ
Programs: TK*G, Marriott Gold, Hilton Diamond, IHG Plat
Posts: 678
Is AC blocking my TK FFP? (mystery solved)
Since about 3-4 months ago, I noticed that I am not longer able to add my TK FFP to AC reservations by AC phone/social media agents. Each time, I was told by AC agents that they received error msg "name mismatch". This is regardless AC 014, UA 016 or tickets issued by other airlines. The workaround for AP tickets (adding to OAL FF info section) no longer works either - same error msg.
At the airport, although the AC agents can add TK #, it won't show up on the BP - neither the # nor *G status and I get Zone 5 each time. The funny thing is that when I check in with AC for an AC/UA interline ticket, AC legs will show Zone 5 and no FFP, and UA leg will show TK# and status on AC-issued BP.
Is it possible that AC is blocking my TK FFP? Anyone else used TK FFP on AC flights recently?
This is extremely frustrating because my name already gets mistakenly flagged for DHP and I have to check in at the AC counter each time whenever an AC segment is involved (UA/NZ cannot even check me in on AC leg).
At the airport, although the AC agents can add TK #, it won't show up on the BP - neither the # nor *G status and I get Zone 5 each time. The funny thing is that when I check in with AC for an AC/UA interline ticket, AC legs will show Zone 5 and no FFP, and UA leg will show TK# and status on AC-issued BP.
Is it possible that AC is blocking my TK FFP? Anyone else used TK FFP on AC flights recently?
This is extremely frustrating because my name already gets mistakenly flagged for DHP and I have to check in at the AC counter each time whenever an AC segment is involved (UA/NZ cannot even check me in on AC leg).
Last edited by ericw; Feb 13, 2019 at 9:23 pm
#3
Original Poster
Join Date: Sep 2007
Location: YYZ
Programs: TK*G, Marriott Gold, Hilton Diamond, IHG Plat
Posts: 678
but I don’t even have a middle name. My name is correct with TK. It has always worked previously.
Also, forgot to mention - once ac agent at airport adds my TK ffp to the PNR, I do get miles correctly. Just no indication of TK # nor status on AC BP.
Also, forgot to mention - once ac agent at airport adds my TK ffp to the PNR, I do get miles correctly. Just no indication of TK # nor status on AC BP.
#5
A FlyerTalk Posting Legend
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,346
I feel like this was discussed already, but sometime in the last year or so, AC added name matching.
Previously, anyone could throw any *G number on the PNR and receive full *G benefits.
Now, it does a name match.
So if it stopped working 3-4 months ago, it's likely because whatever's in TK's system doesn't match your ticket.
UA does not do name matching, which is why you have no issues with them.
Previously, anyone could throw any *G number on the PNR and receive full *G benefits.
Now, it does a name match.
So if it stopped working 3-4 months ago, it's likely because whatever's in TK's system doesn't match your ticket.
UA does not do name matching, which is why you have no issues with them.
#6
Suspended
Join Date: Sep 2014
Programs: AC SE100K-1MM, NH, DL, AA, BA, Global Entry/Nexus, APEC..
Posts: 18,877
I feel like this was discussed already, but sometime in the last year or so, AC added name matching.
Previously, anyone could throw any *G number on the PNR and receive full *G benefits.
Now, it does a name match.
So if it stopped working 3-4 months ago, it's likely because whatever's in TK's system doesn't match your ticket.
UA does not do name matching, which is why you have no issues with them.
Previously, anyone could throw any *G number on the PNR and receive full *G benefits.
Now, it does a name match.
So if it stopped working 3-4 months ago, it's likely because whatever's in TK's system doesn't match your ticket.
UA does not do name matching, which is why you have no issues with them.
OP's post 39 in his thread
AC secrect “travel ban” for middle eastern frequent flyers?
#7
Original Poster
Join Date: Sep 2007
Location: YYZ
Programs: TK*G, Marriott Gold, Hilton Diamond, IHG Plat
Posts: 678
Thanks guys for confirming that TK still works with AC and the name matching thing is new.
I guess I will submit a ticket to AC.
Thanks a lot!
#8
Moderator, Air Canada; FlyerTalk Evangelist
Join Date: Feb 2015
Location: YYC
Programs: AC SE MM, FB Plat, WS Plat, BA Silver, DL GM, Marriott Plat, Hilton Gold, Accor Silver
Posts: 16,775
I feel like this was discussed already, but sometime in the last year or so, AC added name matching.
Previously, anyone could throw any *G number on the PNR and receive full *G benefits.
Now, it does a name match.
So if it stopped working 3-4 months ago, it's likely because whatever's in TK's system doesn't match your ticket.
UA does not do name matching, which is why you have no issues with them.
Previously, anyone could throw any *G number on the PNR and receive full *G benefits.
Now, it does a name match.
So if it stopped working 3-4 months ago, it's likely because whatever's in TK's system doesn't match your ticket.
UA does not do name matching, which is why you have no issues with them.
#9
Original Poster
Join Date: Sep 2007
Location: YYZ
Programs: TK*G, Marriott Gold, Hilton Diamond, IHG Plat
Posts: 678
OK, after many back and forth with AC and TK and troubleshooting with a bunch of FFP #s , it seemed the problem was on the TK side (sorry AC) - albeit a weird one:
I registered my TK# years ago in Title Case "Eric Wxxxxxx". For some weird reason, the letter i is stored as unicode u0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE), instead of u0069 in TK's back end system that is linked to *A. TK.com shows Eric or ERIC fine. Only when I copied & pasted my name from TK's support email to a unicode translator did I notice the discrepancy.
That's why AC was saying "name mismatch"...
The lesson is - always CAPITALIZE your name when registering.
I registered my TK# years ago in Title Case "Eric Wxxxxxx". For some weird reason, the letter i is stored as unicode u0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE), instead of u0069 in TK's back end system that is linked to *A. TK.com shows Eric or ERIC fine. Only when I copied & pasted my name from TK's support email to a unicode translator did I notice the discrepancy.
That's why AC was saying "name mismatch"...
The lesson is - always CAPITALIZE your name when registering.
Last edited by ericw; Feb 13, 2019 at 9:22 pm
#10
Suspended
Join Date: Sep 2014
Programs: AC SE100K-1MM, NH, DL, AA, BA, Global Entry/Nexus, APEC..
Posts: 18,877
OK, after many back and forth with AC and TK and troubleshooting with a bunch of FFP #s , it seemed the problem was on the TK side (sorry AC) - albeit a weird one:
I registered my TK# years ago in Title Case "Eric Wxxxxxx". For some weird reason, the letter i is stored as unicode u0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE), instead of u0069 in TK's back end system that is linked to *A. TK.com shows Eric or ERIC fine. Only when I copied & pasted my name from TK's support email to a unicode translator did I notice the discrepancy.
That's why AC was saying "name mismatch"...
The lesson is - always CAPITALIZE your name when registering.
I registered my TK# years ago in Title Case "Eric Wxxxxxx". For some weird reason, the letter i is stored as unicode u0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE), instead of u0069 in TK's back end system that is linked to *A. TK.com shows Eric or ERIC fine. Only when I copied & pasted my name from TK's support email to a unicode translator did I notice the discrepancy.
That's why AC was saying "name mismatch"...
The lesson is - always CAPITALIZE your name when registering.
#11
Join Date: Jun 2012
Programs: TK*G
Posts: 267
OK, after many back and forth with AC and TK and troubleshooting with a bunch of FFP #s , it seemed the problem was on the TK side (sorry AC) - albeit a weird one:
I registered my TK# years ago in Title Case "Eric Wxxxxxx". For some weird reason, the letter i is stored as unicode u0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE), instead of u0069 in TK's back end system that is linked to *A. TK.com shows Eric or ERIC fine. Only when I copied & pasted my name from TK's support email to a unicode translator did I notice the discrepancy.
That's why AC was saying "name mismatch"...
The lesson is - always CAPITALIZE your name when registering.
I registered my TK# years ago in Title Case "Eric Wxxxxxx". For some weird reason, the letter i is stored as unicode u0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE), instead of u0069 in TK's back end system that is linked to *A. TK.com shows Eric or ERIC fine. Only when I copied & pasted my name from TK's support email to a unicode translator did I notice the discrepancy.
That's why AC was saying "name mismatch"...
The lesson is - always CAPITALIZE your name when registering.
EDIT: Did some more reading, and it seems like dotted versus dotless "i" is probably due to the way the Turkish language handles these letters as distinct (https://en.wikipedia.org/wiki/Dotted_and_dotless_I). E.g. İ is the capital version of i, and I is the capital version of ı. Will report back with my experience in a few weeks.
Last edited by State of Trance; Mar 3, 2019 at 9:43 pm
#12
Original Poster
Join Date: Sep 2007
Location: YYZ
Programs: TK*G, Marriott Gold, Hilton Diamond, IHG Plat
Posts: 678
You will be probably fine if your name has always been capitalized in TK FFP.
AC systems have always been hit and miss and inconsistent in showing FFP among AC.com Manage my booking, Seat Selection Tool and AC app.
EDIT: thanks for the wikipedia page - I suspected that and now I am confident that's the root cause.
AC systems have always been hit and miss and inconsistent in showing FFP among AC.com Manage my booking, Seat Selection Tool and AC app.
EDIT: thanks for the wikipedia page - I suspected that and now I am confident that's the root cause.
#13
Join Date: Jun 2012
Programs: TK*G
Posts: 267
You will be probably fine if your name has always been capitalized in TK FFP.
AC systems have always been hit and miss and inconsistent in showing FFP among AC.com Manage my booking, Seat Selection Tool and AC app.
EDIT: thanks for the wikipedia page - I suspected that and now I am confident that's the root cause.
AC systems have always been hit and miss and inconsistent in showing FFP among AC.com Manage my booking, Seat Selection Tool and AC app.
EDIT: thanks for the wikipedia page - I suspected that and now I am confident that's the root cause.
Do you also have "i" present in your surname as well? My TK correspondence always seems to address me as First Middle LAST. I wonder if that also affects how TK reports names to *A.
#14
Original Poster
Join Date: Sep 2007
Location: YYZ
Programs: TK*G, Marriott Gold, Hilton Diamond, IHG Plat
Posts: 678
Even before TK changing my name to capitalized, I only saw regular i and I on TK.com in my profile. I never knew what AC saw would be different.
#15
Join Date: Jun 2012
Programs: TK*G
Posts: 267
Did you have any issues with receiving priority boarding and baggage or lounge access from AC by presenting your physical *G card even if the BP didn't reflect it?