Overview: User Types

Mbanq APIs offer a dynamic user functionality that caters to diverse operational needs through two distinct types of users: System Users and Self-Service Users. This framework is designed to provide tailored access and control, data scoping, and ensuring that both administrative and client-specific tasks are handled efficiently and securely. In this context, data scope means what data a particular user has access to. This can be as wide as across an entire platform or as narrow as only data connected to a single client. In this overview, we'll explore the unique roles and permissions of System Users and Self-Service Users within the Mbanq system, highlighting how their differences facilitate a seamless integration process.

System Users:

System users possess comprehensive data scope across the entire organization. They have the ability to create or update client information, manage accounts, issue cards, and perform various other tasks. However, the specific features accessible to a system user depends on their assigned permissions. For instance, one system user may have permissions to create new clients, while another system user may only have read-only access to existing client information.

Use Case

A Platform facilitates all client user interactions including login, authentication, data access and transacting. In this model, the Platform stands completely in the middle between the client user and the Mbanq cloud back office.

Self-Service Users:

Self-service users are associated with specific clients and have limited data scope, confined to the clients they are connected with. Within their designated client accounts, self-service users can view card information, initiate transfers, generate statements and perform other tasks relevant to their associated clients. Like admin users, the permissions granted to self-service users determine the extent of their access. For example, a self-service user with appropriate permissions may be able to view a client's transaction history, while another self-service user may only be able to access the account balance.

Use Case

A Platform may prefer to have the client user bypass the Platform's authentication and data scope access controls and instead have this governed by Mbanq. In this use case, the client user would authenticate with Mbanq and Mbanq would control data access and transaction permissions.

Note:

Supporting self-service users allows sponsor banks and platforms to continue supporting client users authentication and transactions in the event that the platform systems fail for some reason.

Understanding the distinction between system users and self-service users is crucial for effectively implementing Mbanq's APIs. By leveraging the appropriate user type, you can tailor the integration to meet your specific needs and minimize potential exposure in the event of a data breach at your end.

📘

Important API Endpoints for User Types:

• Enable Self-service Access

Now that we have established the user types, let's delve into the details of Mbanq's APIs and explore how they can be seamlessly integrated into your systems.