That's what I said. What he said is beyond a certain amount, Apple Pay user will be required for signature regardless of store, location or CC used. It's obligated. No may, but must.
He never specified how many this threshold is exactly, however.
That's because what I and others have said here, is that it's dependent on the purchase and merchant:
Nobody said you had to sign every time. As I noted, and as any credit card or NFC payment user knows, many merchants nowadays only require signatures above a certain threshold.
We still have to sign if the transaction goes above whatever purchase limit the merchant or card scheme has set.
The Apple Pay FAQ even notes it:
In other words, it's just like any other card purchase. Remember, these electronic wallets are emulating a contactless card. They're not some magical new payment method.
What you said was:
I know this. That's why I thought it's futile. In that strict sense, the signature you signed to confirm the credit card purchase isn't a part of "transaction" either. So it's right as I said: Conceptually Touch ID functions as a signature (to authorise or verify a purchase).
Touch ID does not function as a signature, conceptually or otherwise. When the terminal says a signature is required, it's required.
Touch ID only functions as a shortcut for the passcode. Either one can be used.
In the case of using the Apple Watch with say, an iPhone 5C, Touch ID isn't even an option. Its absence, just like its presence on newer devices, will not be noticed by the merchant terminals.
That's the reason for his argument, I guess. He argued under the assumption that basically Apple Pay is no different than Google Wallet, so Touch ID, which only Apple has, must not be a part of the Apple Pay transaction.
From the merchant standpoint, there is no difference. If the merchant has set a limit on purchases above which a signature or PIN is required, it will be required no matter how you unlocked the payment app... whether by passcode, voice, fingerprint or nothing at all.
You're confusing a method of enabling a device payment app, with what is required on the merchant/bank side to complete a transaction. In this case they're simply not related.