Isn't transaction verification tied to block generation, and isn't block generation limited to about 1 every 10 minutes?
From how I understand it, verification involves:
1. Confirming the privately-signed transaction against the public key of the source wallet (transactions not forged).
2. Confirming against the historical transaction chain that the coins actually belong to the source wallet (coins not forged).
3. Passing the verified transaction along to other peers.
Prior to being included in a block, it's entirely possible for the payer to issue the same money to multiple recipients. Once it's in, it's assured that only one is included, and others are therefore invalid. So it's in recipients' best interests to wait for a few blocks before totally accepting something as "paid".
Another approach is to have "trusted sources" which are Bitcoin banks/ewallets. If your customer is using a Bitcoin bank like eWallet to send a payment, you can pretty much assume that the transaction is valid based on the source, without verification.
Either way, this is merely a short term problem. As more Bitcoin infrastructure springs up (more banks, more verification hubs, more incentive on transaction fees rather than mining, when mining gets too expensive) then these problems will be organically mitigated. If the Bitcoin infrastructure were to remain the way it is now forever, it won't scale for many other reasons (like requiring peers' wallets to store significant transaction history that could grow at the rate of gigabytes per hour with "real world" volume).