Littlepay has global partners, so the possibility of them rejecting or defeaturing benefits simply because it is ’non-UK’ is perverse. I have used their service on a few occasions however the system (as you describe it) means that each payment card has its own ‘account’ (as it were) on their platform. My initial GDPR concern related to the claim that only a card number is required, when you actually require expiry and CVV code Unlike Oyster which will provide full journey history irrespective of financial payment type (excluding cash) as Virtual card wallets generate their own numbers and if you used your card, Watch, or phone the codes would be different and journey history impacted as to be less than useless.
By registering on a transport company’s website and linking to the cards used provides a similar experience to Oyster, as this wasn’t done you are then at the mercy of how Littlepay has been set up on the transport company used - this is hardly ideal snd open to confusion as to what info you can get. (Perhaps slightly less so if the Littlepay provides the web front end to passengers) however multiple accounts based on each and every payment card used is nonsensical.
As a regular passenger with Citylink my payments are only recorded if I remember to log in with username and password, should I forget, then the payment is certainly taken and ticket code emailed but does not show in my travel history. I recall Worldpay was the processor but Citylink’s processes are hardly unique for travel tickets, and a Euro denominated card was accepted without a problem, and showed on my travel history with everything else.
