LATAM context
It's the model behind Belvo, Plaid, Prometeo and Open Finance APIs. Safer than asking for a password, but it requires the bank to support it. Many LATAM banks still don't expose OAuth.
Concrete example
A budgeting fintech asks you to connect your bank. It redirects you to your bank's own portal, you enter your credentials there, authorize read access to your transactions, and the fintech receives your data without ever holding your credentials.
How it shows up on your bank statement
It doesn't show up in the document either. It's the mechanism by which an app gets permission to read the account directly from the bank, instead of starting from a file the user downloaded.
How does finO$ handle this?
finO$ does NOT use OAuth aggregation. It processes PDFs directly. Useful when OAuth isn't available (many LATAM banks) or when persistent authorization isn't something the user wants to grant.