# Consumer Lending source: https://developer.mastercard.com/open-finance-europe/documentation/licensed/use-cases/consumer-lending/index.md This service is available using connectivity from Mastercard's Open Finance [Insights Service](https://developer.mastercard.com/open-finance-europe/documentation/licensed/insights/index.md). Accurately asssessing an End-User's income is crucial for appropriate Consumer Lending when determining affordability. Traditionally, this process relies on paper wage slips, bank statements, or static credit reference data, making it slow for both end users and lenders. Our Open Finance data solutions give you access to the real-time insights needed to make informed, fair lending decisions -- allowing you to accept more loan applications, while mitigating the risks associated with underwriting and servicing those loans and may enhance Data For Credit Scoring. We offer [Verification of Income](https://developer.mastercard.com/open-finance-europe/documentation/licensed/insights/voi/index.md) solution analyses positive inbound transaction amounts, distinguishes between one-off and recurring income streams to provide clarity on the nature of income. It then employs a series of calculations---including total income, total salary, regularity, longevity, and stability of income---to generate confidence ratings, categorized as high, medium, or low. Clients can seamlessly access these income-related insights through the Insights API, available in JSON and PDF formats. Importantly, clients are at their own discretion of this information, whether for approving or declining credit applicants.​ This solution is tailored for Third-Party Providers (TPPs) who operate under their own AIS license only. Ensuring compliance with PSD2 Open Finance consent requirements on behalf of the end user. ### How it works {#how-it-works} Merchants can use Open Finance for consumer verification when providing lending services, as follows: 1. A consumer lending journey is requested through our APIs when the consumer applies for a loan. 2. Mastercard handles the communication with the consumer's bank, including user authentication using Strong Customer Authentication (SCA). 3. The consumer data is retrieved and the consumer's lending request is approved or rejected. **The following screenshots show sample screens that can be rendered using this service:** ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_1.png) The consumer agrees to the lending terms. ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_2.png) The consumer selects their bank. ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_3.png) The consumer authenticates themselves using the bank's existing authentication method. ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_4.png) Available accounts are displayed, and the consumer selects the account to share their data with the lender. ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_6.png) The merchant app shows an additional confirmation about the access and use of data for the consumer to agree. ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_7.png) The merchant app fetches and process the account data. ![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/ConsumerLending/licensed/ConsumerLending_8.png) The merchant app shows a confirmation of loan approval. ### Data flow {#data-flow} Diagram voi-enterprise-how-it-works **Detailed steps are explained below:** 1. End User initiates a service with the client. For example, a consumer wishes to apply for a Credit Card. 2. The Client collects the consent from the end user with data parameters defined according to which product they would like to consume. 3. End user gives consent to the client to connect to their bank. Consent is managed by the client. 4. Client submits the Insights job through the Insights endpoint and specifies which service they would like ( eg: Verification of Income). 5. Mastercard validates client credentials. 6. Mastercard returns the Connect URL 7. Mastercard presented the Connect URL to the end user on the clients site. 8. The connectURL is presented to the end user who can use it to authorise access to their account. 9. The URL will either direct the End User to the Bank Selection screen or ASPSP depending on whether the Client has passed a Provider ID to Insights. 10. End User Redirected to the client. 11. Mastercard requests transactions information from the bank 12. Mastercard receives account and transactions information from the bank. 13. Mastercard performs categorisation and leverages algorithmic models to provide Income insights. 14. Client polls the Status end point to enquire about the status of the job 15. Status of the job returned 16. Insights available to the client. 17. Client requests the insights results. 18. The Client can use the results to make a decision that relates to the end user. ### Next steps {#next-steps} * Learn more about our [Verification of Income](https://developer.mastercard.com/open-finance-europe/documentation/licensed/insights/voi/index.md) product and how you can use it. * Refer to the [Quick Start](https://developer.mastercard.com/open-finance-europe/documentation/licensed/insights/quickstart/index.md) for the API integration steps. * Refer to the [API References](https://developer.mastercard.com/open-finance-europe/documentation/licensed/insights/api-references/index.md) to learn more about the API.