- From: Petr Dvořák via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Mar 2025 07:02:51 +0000
- To: public-webauthn@w3.org
@ve7jtb One more comment to: > I would like to understand why Secure Transaction Confirmation is not good enough for them before starting on something else. SPC is great for e-commerce purchases online but these are barely all transactions that are out there. Banks must apply SCA to all payment types, including: - Domestic account to account payments - Foreign payments - Bulk payments - Collections - Standing orders (establishment) - Payments to contact - ... any other payment type Besides that, banks must apply SCA for new SCA element binding, meaning that "adding a new authenticator with the following parameters" is a mandatory transaction to cover. Banks also typically use SCA for other use-cases, such as: - Change of card limits - Enabling e-commerce payments on the card - Setting up or modifying an insurance - Change of other credentials - Adding another person to account - Changing registered contact info (address, email, phone number) ... our typical customer has around 200 operation types with different attributes. So, we would need a slight extension for SPC... -- GitHub Notification of comment by petrdvorak Please view or discuss this issue at https://github.com/w3c/webauthn/pull/2020#issuecomment-2760394354 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 March 2025 07:02:52 UTC