Below is an overview of the Mifundo Consumer API (MCA) service, including descriptions of the communication flow and how credit-related data is retrieved using session-based requests.
The Mifundo Consumer API provides structured access to consumer financial, legal, and personal information collected from various sources such as credit bureaus, courts, registries, and banks. Consumers initiate sessions that define input parameters, after which the API delivers categorized responses with high granularity.
- Session-based data retrieval: Start a session to define the subject and scope of information needed.
- Modular data access: Retrieve specific datasets like account statements, tradelines, immovables, legal entities, identity verifications, scores, registry-reported incomes, court and insolvency cases, categorizations, and metrics.
- Secure access: Uses OpenID Connect for authentication.
- Multiple data formats: JSON and TSV outputs supported.
- Error handling: Granular error reporting including problem and validation details.
| Open API 3 | JSON / YAML |
| Endpoint Test | https://apitest.mifundo.com/mca/ |
| Endpoint Live | https://api.mifundo.com/mca/ |
| Current API version | v1 |
| Authentication | oAuth, Bearer Token (JWT) |
| Support and incidents | support@mifundo.com |
| Term | Explanation |
|---|---|
| MCA | MCA stands for Mifundo Consumer API — a standardized interface developed by Mifundo that enables the secure exchange of consumer credit data between financial institutions, credit bureaus, and other authorized Data Providers across European countries. The MCA facilitates the collection, transformation, and delivery of consumer credit-related DataPoints in a harmonized format, enabling banks and lenders to access cross-border credit profiles through a unified API, regardless of local data structures or sources. |
| Data Subject | A Data Subject is the natural person (i.e., individual human being) to whom personal data relates. In the context of the Mifundo Consumer API (MCA), the Data Subject is the consumer whose credit-related data is being accessed, processed, or shared through the API, based on their explicit consent. |
| Session | A Session in MCA represents a temporary and traceable interaction instance initiated by Client on behalf of a Data Subject to retrieve their credit-related information from one or more Data Providers. It serves as a container for the full data access process — from consent collection to data retrieval and final delivery. |
sessionID | The sessionID is a unique identifier assigned to each Session. It is used to:
|
| Client | A Client refers to any authorized organization or system that integrates with the Mifundo Consumer API (MCA) to initiate and manage data retrieval processes on behalf of a Data Subject. Typically, a Client is a bank, lender, fintech, or service provider that consumes credit-related DataPoints via MCA to assess creditworthiness, support lending decisions, or fulfill compliance obligations. |
| DataPoint | A DataPoint represents a single, standardized unit of consumer credit-related information within the Mifundo Consumer API. Each DataPoint has a defined structure, meaning, and data type, and may originate from various external providers such as credit bureaus, banks, or open banking services. DataPoints are used to model individual pieces of credit data — such as total outstanding debt, number of active loans, or presence of late payments — and serve as the foundation for building a unified, cross-border credit profile. |
| Data Provider | A Data Provider is any external organization or system integrated with the Mifundo Consumer API (MCA) that supplies consumer credit-related information in response to a valid Session and consent from a Data Subject. Data Providers are the sources of raw or structured credit data, such as credit bureaus, banks, open banking aggregators, or alternative data services. Each Provider supports a specific set of DataPoints and typically operates within a defined country or regulatory domain. |
| Consent | A data subject’s explicit permission allowing a data provider (e.g., a credit bureau, bank, or utility provider) to share their personal or financial information with a third party (e.g., a bank or lender) for a specific purpose, such as credit assessment or identity verification. |
The communication between the client (e.g., a consumer application) and the Mifundo Consumer API follows a series of steps to create and manage credit profiles. Below is a step-by-step description of how the communication should flow and how the credit profile is filled.
Before interacting with the API, the client must authenticate to obtain an access token.
- Authentication Method: Bearer Token (JWT)
- Process:
- Client sends credentials to the authentication endpoint.
- Receives an access token upon successful authentication.
- Includes the access token in the
Authorizationheader for subsequent API requests.
Use POST /v1/sessions to initiate a session by providing search input such as personal details or identifiers.
A successful creation of a Session returns a sessionID used for all subsequent data requests.
Each endpoint delivers data tailored to the specific Data Subject identified in the Session. The data is structured using predefined schemas and returned with detailed source attribution. Use the SessionID to request any of the following:
| Name | Description |
|---|---|
| Account Statements | Bank transaction summaries and downloadable TSV files. |
| Categorizations | Categorized financial data. |
| Court and Insolvencies | Legal data including insolvency and court history. |
| Identity Verifications | Verified identity details, list of images and associated images. |
| Immovables | Property data associated with Data Subject. |
| Legal Entities | Company affiliations to the Data Subject. |
| Metrics | Derived metrics related to financial behavior. |
| Positive Tradelines: | Positive credit info about Data Subject, like active loans, credit cards, etc. |
| Negative Tradelines: | Negative credit info about Data Subject. |
| Person Details | Verified personal identity data. |
| Scores | Credit scores known about Data Subject. |
| Registry Incomes: | Declared or registered incomes. |
Use PATCH /v1/sessions/{sessionId} to append parameters, namely countries or Data Packages to an existing Session.
Use GET /v1/sessions/{sessionId} to view session summary or GET /v1/sessions to list sessions.
Responses include structured error types: status or detail with HTTP status codes 400–500.
Each Session may involve multiple Data Sources (e.g. national credit bureaus, population registers, financial data aggregators, etc.). For each source, a separate status is returned to indicate the progress or outcome of the data retrieval process.
This means that a single Session can include multiple statuses - one per each Data Provider involved. These statuses help you monitor the lifecycle of data collection and understand which providers have responded, are pending, or encountered issues.
For a detailed explanation of statuses, see the corresponding query descriptions.
To obtain test data, please contact our support team at support@mifundo.com.
The Mifundo Consumer API delivers reliable, detailed insights into consumers' financial profiles. By leveraging its modular endpoints and secure Session-based model, integrators can efficiently access and act upon complex data structures.
Highlights:
- Session-driven architecture: Enables focused and secure data queries.
- Granular endpoint coverage: Target specific areas of consumer data.
- Strong error reporting: Interpret failures easily with standardized messages.
- Privacy-centric: Compliant with data protection principles.
This makes MCA a robust backbone for financial institutions, fintechs, and data processors working with cross-border consumer credit insights.