1. We adopted chip cards quite late, so a lot of legacy hardware still exists - including payment terminals built into restaurant point of sale machines with a magnetic strip reader, instead of a separate card terminal.
2. Wireless card terminals are not common in the US, outside of things like Square or Toast readers. Readers are usually hardwired to the POS and aren't able to be "undocked" and carried around.
3. Outside of contactless, signatures are still usually required, and people are still used to having the receipt printer at the host stand alongside the terminal, instead of built into the card reader.
This is all slowly changing, and I honestly chock a lot of it up to stuff like smartphone payments (remember, we got Apple Pay before having contactless embedded in the majority of cards!) and smartphone-based POS systems like Square.
If you're a weather app, being able to tell your users "it will start raining in 35 minutes but pass in 55 minutes" is a huge value add over "80% chance of rain in the next hour". I found it to be quite accurate down to the 5-10 minute increment when I used to live in an area with frequent summer thunderstorms.
Some of today's most interesting and exciting "technical" challenges have their roots in many disciplines. Cybersecurity can be tackled from a full range of perspectives, from the highly technical (e.g. cryptography) to traditionally non-technical disciplines like law, public policy, and design. The kind of deep thought our world needs on things like AI and ML needs people who are just as informed about the social sciences, psychology, philosophy, and economics as they are about computer science. Our ongoing debates about issues like content moderation or digital privacy need folks who understand how to think about people, including those who are at risk and vulnerable, and then translate that knowledge into the language of engineers.
And even though we've made progress on this front, our governments, courts, and legislatures are still running on a deficit of knowledge about tech, which is a whole different ballgame. (I'd encourage reading Bruce Schneier's site on public interest technology if you're interested: https://public-interest-tech.com/)
All this is to say: if your daughter wants to go the hardcore tech route and loves solving CS or software engineering challenges, more power to her! But I also hope that she doesn't feel limited or boxed in by the traditional definitions of the discipline.
* www[0-9].example.tld -> [0-9].example.tld, e.g. www1.nyc.gov -> 1.nyc.gov
* example[ac|co|gov|edu].tld -> example.[ac|co|gov|edu].tld e.g. exampleac.uk -> example.ac.uk
My guess, as someone else further down the comments mentioned, is that some URL handling library is doing more than expected to its input. I filed an internal bug report referencing some of the public reports from a dev build of Android 12, so hopefully this will get triaged soon if someone hasn't already done a similar reproduction.
(I work at Google, but on nothing remotely related to Android.)
My only downside with Schwab is the UI on their site. It seems very much geared to the boring investor, moreso than the checking account customer. Maybe some people prefer that, though.
I suppose you could just issue EMV-compatible cards where you grant the holder free travel, though I'd expect this would be more complicated than the status-quo (both in terms of needing to register IDs in lists that aren't particularly long currently, and in terms of needing a much larger standard implemented).
I also tried Rosetta stone. It's a good companion to an other learning tool but not very good on its own.
I'm a fan of pimsleur language learning. It's old school but it works, if you do it consistently and follow what they ask you to do.