Toqio’s Integration Hub is your centralised cloud platform designed for integrating financial services seamlessly within the Toqio ecosystem. This comprehensive guide provides all necessary resources to ensure a smooth and successful integration with Toqio.

Overview

The Integration Hub acts as a vital intermediary, enabling secure and efficient communication between Toqio and external financial service providers. An integration, therefore, refers to software developed by third-party integrators to facilitate interaction between Toqio and financial providers.

How It Works

Integration software receives and processes requests from Toqio, translating these requests into the specific API calls required by the financial provider.
Responses or notifications from the financial provider are similarly received and processed by the integration, then communicated back to Toqio via webhooks.
Think of the Integration Hub as a translation and orchestration layer between Toqio and the external financial providers.

Check out the Integration guide for the practical steps and technical requirements to connect a provider to Toqio, including authentication, mandatory endpoints, error handling and capabilities.

Critical Requirements for Integration

To successfully connect and utilise the Toqio Integration Hub, integrators must adhere to the following key requirements:

1. Authentication and Encryption

All requests and responses between Toqio and the integration software must be authenticated and encrypted to ensure data security and compliance.
Implement double authentication:
- Toqio's authentication requirements.
- Authentication methods mandated by the financial provider.

2. Financial Provider API Integration

Assess and implement integration with the financial provider's API.
Integration software must translate Toqio's requests into compatible API calls. For example:
- A user requests a new account within the Toqio platform.
- The integration receives this request, translates it into the financial provider’s API format, and sends it to the financial provider.

3. Webhook Communication

The integration software must process incoming requests or updates from the financial provider and communicate these asynchronously to Toqio via webhooks.
The integration does not retrieve data stored directly in Toqio; data needed internally must be stored in the integration’s own database or requested via the provider’s API.
Refer to Toqio Webhooks Documentation for additional details.

4. Data Management

Any data required by internal processes must be securely stored in the integration's database or dynamically fetched from the financial provider via their API.

5. Mandatory and Optional Endpoints

The integration must implement a set of mandatory endpoints to receive and respond to requests from Toqio.
Integrators can selectively implement additional optional endpoints based on specific use cases and requirements outlined in the endpoint catalogue.

Endpoint Catalogue

Below are the core endpoint categories integrators may consider:

Account Management: Open, close, and manage user accounts.
Transaction Processing: Execute and track transactions.
Compliance Checks: Perform compliance verification steps (e.g., KYC).
Notifications: Handle asynchronous updates and push notifications via webhooks.

Note: Integrators must clearly define which endpoints are mandatory for their specific integration and adhere strictly to the interface definitions.

Next Steps

After successfully developing your integration:

Conduct comprehensive testing within our sandbox environment.
Deploy your integration within the live Toqio environment to offer enhanced financial services to your end-users.

Thank you for choosing Toqio's Integration Hub. We look forward to empowering your financial solutions together.