Integration Models

Atlas Integration Models: Platforms vs. Fintechs

The Atlas Suite provides API-first, embedded finance solutions. It is comprised of two distinct products, each structured with a specific operational, compliance, and relationship model to suit different types of partners.

This guide explains the two models:

• Atlas for Platforms: An embedded model where Verto manages all compliance.
• Atlas for Fintechs: A reliance model where Verto relies on the partner's existing compliance framework. An external compliance audit is mandatory

Due to downstream banking partner relationships, not all currencies can be supported in Atlas for Fintechs, that can be offered for Atlas for Platforms.

1. Atlas for Platforms (Embedded Model)

This proposition enables digital platforms to embed financial services directly into their existing offerings by leveraging Verto's licensing and infrastructure.

Who is it for? Digital platforms like B2B Marketplaces, E-commerce, Payroll, and Expense Management companies, as well as software companies and pre-regulated fintechs.

⚖️ Compliance & Operational Model

Under this model, Verto assumes full compliance responsibility.

• Verto handles all compliance, including conducting KYC/KYB on the end-customers.
• The partner has no regulatory overhead and does not need their own licensing or regulatory expertise, this is all managed by Verto.
• The end-customers become Verto customers by accepting Verto's terms and conditions.
• The financial experience is fully embedded, so the end-user does not need to interact directly with Verto.

🤝 Relationship Model: 'Referred Client' Type

This model typically uses the 'Referred Client' relationship structure.

• The end-client (the platform's user) has a direct contractual relationship with Verto and must be fully onboarded by Verto.
• The partner (the "Parent Account") owns the commercial relationship and has permission to operate the Verto account on the end-client's behalf.

2. Atlas for Fintechs (Reliance Model)

This proposition is designed for regulated financial institutions to embed Verto's core banking, FX, and payment infrastructure directly into their own offerings.

Who is it for? Highly regulated Financial Institutions (FIs), Fintechs, digital banks, Money Service Businesses (MSBs), Payment Service Providers (PSPs), Brokers, and Money Transfer Operators (MTOs).

⚖️ Compliance & Operational Model

This model is based on reliance. Verto conducts a Downstream Assessment (or Nested Assessment) to review the partner FI's own compliance framework.

The outcome of this assessment determines the reliance model:

• High Reliance: For partners with mature compliance functions. Verto trusts the partner's checks, enabling faster processing.
• Low Reliance: For partners with less mature compliance functions. Verto provides greater oversight.
• No Reliance: Partners without a compliance function are not eligible for this model and should be directed to Atlas for Platforms.

🤝 Relationship Model: 'Sub-Client' Type

This model typically uses the 'Sub-Client' relationship structure.

• The end-client only has a relationship with the partner (the "Parent Account").
• The Partner owns both the commercial and the financial services relationship. The end-client has no direct legal relationship with Verto.

At-a-Glance Comparison