# Lending and Financial Management 
source: https://developer.mastercard.com/open-finance-data/documentation/use-cases/lending-and-financial-management/index.md

As an AISP, we provide secure, consent-based access to raw bank transaction data---giving you the flexibility to build, analyse, and innovate on your own terms.

Whether you are building a lending engine, a personal finance tool, or a risk model, our platform delivers the unfiltered financial data you need to make smarter, faster, and more personalized decisions.

Companies can leverage account information to offer more accurate and personalized credit scoring to customers (PSUs) who consent to share their financial data.

* Improved Risk Assessment: Make more informed lending decisions based on real-time financial data.
* Faster Onboarding: Streamline credit checks and reduce manual document collection.
* Customer Trust: Offer transparent, consent-based data usage that empowers users.
This Figma diagram demonstrates a typical user flow.
For the best viewing experience, click the **full screen** option.

### How it works {#how-it-works}

Your lending business can securely access a customer's account information---with their consent---to gain a comprehensive view of their financial behaviour. Using the data you can build insights into income, spending patterns, and transaction history, enabling you to assess creditworthiness with greater accuracy and confidence.

We access detailed real-time transaction feeds directly from users' bank accounts, with their explicit consent.

* Transaction dates, descriptions, and amounts
* Merchant and category data (where available)
* Account balances and identifiers
* Multi-bank and multi-account coverage

#### What does the lending and financial management flow look like for an End User? {#what-does-the-lending-and-financial-management-flow-look-like-for-an-end-user}

This Figma diagram shows the user flow from the merchant, through Mastercard Open Finance, and the bank to the successful data sharing.

#### Data flow {#data-flow}

Diagram lending

\* Payment Service User  

\* Account Servicing Payment Service Provider

1. The end user interacts with the customer's website or app, and wishes to apply for credit.
2. The customer decides to use Open Finance data as part of its credit scoring and decisioning for the end user.
3. The customer calls the `Create consent` and `Create managed flow` endpoints to request a URL to start a consent flow which will guide the end user through the steps to authorize their consent.
4. Mastercard returns the Flow URL.
5. The customer redirects the end user to the Flow URL.
6. The end user is guided through steps at Mastercard and at their bank app or website to give consent, authenticate themselves using Strong Customer Authentication (SCA), and authorize data access.
7. The bank redirects the end user back to Mastercard, where they complete the final steps of the flow to authorize sharing their data with the customer.
8. Mastercard requests the end user's account information from the bank (limited to the data scopes specified for the customer's use case).
9. The bank returns the requested information.
10. Mastercard redirects the end user back to the customer's website or app.
11. The customer calls the `Get accounts` endpoint, indicating the data elements that they require by specifying the parameter `include=additionalInformation,identifiers,holders` in the request.
12. Mastercard returns the requested information to the customer.
13. Mastercard requests the end user's transaction history from the bank.
14. The bank returns the requested information.
15. Mastercard sends a webhook to the customer to notify them that the end user's data is ready to retrieve.
16. The customer calls the `Get transactions` endpoint to request the end user's transaction history, optionally indicating the period of time that they require by specifying date parameters in the request.
17. Mastercard returns the requested transaction history to the customer.
18. The customer uses the information they have received from the end user's bank as part of their credit scoring and decisioning.
19. The customer informs the end user of the credit decision outcome.

### Endpoints used {#endpoints-used}

The customer calls the `Create consent` and `Create managed flow` endpoints to request a URL to start a consent flow which will guide the end user through the steps to authorize their consent.

API Reference: `POST /consents`


API Reference: `POST /consents/{consent_id}/managed-flows`

The customer calls the `Get accounts` endpoint, indicating the data elements that they require by specifying the parameter `include=additionalInformation,identifiers,holders` in the request.

API Reference: `GET /accounts`

The customer calls the `Get transactions` endpoint to request the end user's transaction history, optionally indicating the period of time that they require by specifying date parameters in the request.

API Reference: `GET /accounts/{account_id}/transactions`