What is the difference between AIS, AISP and RAISP terminology?

Firms and advisers often use the terms differently in conversation, but in practice they are usually referring to the same core issue, namely whether the business is carrying on regulated account information services and requires the appropriate permissions or registration route.

Can MEMA help if the product uses third party providers?

Yes. Many AIS models rely on external providers for data connectivity, identity checks, or related functions. The key issue is that outsourcing or integration does not remove the applicant's regulatory accountability. The application needs to show how that accountability is retained and overseen.

Do you only help with drafting the business plan?

No. We support the wider application architecture, including perimeter analysis, control design, governance, operational readiness, customer support, complaints, and the narrative that ties the model together.

Can you help if we are not yet certain whether AIS is the correct route?

Yes. That is often the most important point to address first. We can help assess the model and determine whether AIS permissions are the right route or whether a different analysis is required.

Payment Services Permissions

AIS Permissions Support

AIS applications are often delayed because the submission does not explain the operating model with enough precision. MEMA helps firms seeking AIS permissions, AISP authorisation, or RAISP registration build applications that reflect the real product rather than a generic fintech narrative.

Start AIS Application Call: 0330 133 0811

Why AIS Is a Specialist Exercise

The challenge is not describing the technology. It is explaining the regulated activity in a way that is technically accurate, commercially intelligible, and aligned with the Payment Services Regulations.

Common Application Weaknesses

✗Blurs product features with regulated services
✗Underplays third party integration significance
✗Fails to demonstrate compliance accountability
✗Generic fintech narrative without regulatory precision

Strong Application Characteristics

Clearly explains why the service is in scope
Maps the customer journey with precision
Demonstrates governance and oversight structure
Shows the firm is ready, willing and organised

How MEMA Helps

From perimeter analysis to a credible, complete application

Perimeter Analysis

What the product actually does
How payment account information is accessed
Form of aggregation or processing
Whether the service is properly characterised as AIS

Business Plan Architecture

Permissions route and submission logic
Business plan drafting
Governance narratives
Risk and control frameworks

Third Party Oversight

Outsourcing arrangements
Role of each external provider
Retention of accountability
Controls around relationships

Customer & Conduct

Customer support arrangements
Complaint handling design
Consumer Duty positioning
Vulnerability considerations

Operational Evidence

Operational readiness evidence
Data safeguards and security
Customer journey documentation
Compliance monitoring framework

Product Translation

Translate innovation into regulatory language
Preserve commercial logic of the business
Explain layered integrations clearly
Make the regulatory story coherent

Why Firms Choose MEMA

Permissions work is not a form filling exercise. It is a test of whether the business can articulate its model and demonstrate an operating framework.

Effective where products use layered integrations

Explain the role of each third party clearly

Demonstrate retention of regulatory accountability

Built around real FCA expectations

Practical governance around customer outcomes

Technically precise and commercially aware

Case Study

RAISP Registration for a Fintech Data Aggregation Platform

MEMA supported a fintech business seeking registration as a Registered Account Information Service Provider. The service aggregated payment account data, processed that data for reporting and financial management purposes, and relied on third party providers for data connectivity and identity verification.

The application required careful articulation of the perimeter, the customer journey, the role of external providers, the control framework, and the broader proposition around data use, support, and compliance. That kind of project shows why firms benefit from permissions advice that is both technically precise and commercially aware.

Perimeter Analysis

Third Party Oversight

Control Framework

Governance Narrative

AIS, AISP and RAISP: The Landscape

Firms use these terms differently depending on stage, product maturity, and familiarity with the regime. The underlying need is usually the same.

AIS Permissions

Is the business in scope of Account Information Services regulation?

AISP Authorisation

Full authorisation route for Account Information Service Providers

RAISP Registration

Registration route for firms meeting Registered AISP criteria

Frequently Asked Questions

Select a question to view the answer.

Related Services

Firms seeking AIS permissions may also benefit from

FCA Authorisation Variation of Permissions Payment Services Sector Consumer Duty Compliance Outsourcing

Resolve the Permissions Question Early

If your product depends on account aggregation or payment account information, the permissions question should be resolved properly and early.

Phone: 0330 133 0811

Email: contact@memaconsultants.com