A wallet authorization ties the confirmation to the payer and to the specific transaction. The consent screen shows amount and payee, and the signature covers both, which is what PSD2 dynamic linking asks for. The result resists phishing and carries an identity binding the issuer can rely on.
Strong customer authentication still leans on SMS codes and push confirmations. SMS is phishable and SIM-swappable. A push that says "approve payment" often does not show what is being approved. And none of it is tied to a verified identity, so it proves possession of a phone rather than that the right person authorised the right payment.
Step 01
The payer sees amount and payee in their wallet, not a generic approve prompt.
Step 02
The signature covers amount and payee, so an intercepted approval cannot be replayed against a different payment.
Step 03
Your flow receives an authorization tied to a verified identity, with the record attached.
Rules in play
PSD2 strong customer authentication and dynamic linking, eIDAS 2.0
Live demo
We built PulsePay, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.
Open the PulsePay demoBuilt on Authbound Payments. One API key covers every flow you add later.
