What is the decoupled authentication model?

In the decoupled model the payment is authorised and authenticated on a separate device to the one on which the payment was requested. The decoupled modelled is reliant on the <a href="/glossarycollection/payment-service-user" style="color:#48277C;" target="_blank" title="Payment Service User">PSU</a> providing an identifier to the <a href="/glossarycollection/third-party-provider" style="color:#48277C;" target="_blank" title="Third-Party Provider">TPP</a> that can then be used by the <a href="/glossarycollection/account-servicing-payment-service-provider" style="color:#48277C;" target="_blank" title="Account Servicing Payment Services Provider">ASPSP</a> to look up the correct account to generate the authorisation / authentication request for. If the User is able to authenticate via Mobile App then this will usually be the mobile app.

The decoupled model lends itself well to IOT Use Cases where the PSU can, for instance, confirm a shopping order made by their smart-fridge on their mobile banking app.