Select the Right Integration for You

When integrating with i-payout, choosing the method that best fits your business needs is vital. This page summarizes the available integration methods and provides a comparison table to help you make an informed decision.

Integrations Comparison

i-payouts provides four types of integrations. In the following table, you can see all the specifications for each.

❗️

Batch File Integration

Working with the Batch File Integration requires that you upload the files every time you need to make payouts. It is also the method that is most succeptible to human error.

Hosted Solution

In the Hosted Solution, users interact directly with the i-payout platform. i-payout handles most of the account management and user interface, offering limited customization confined to the platform's functionalities. The integration effort is low, mainly involving API calls to create accounts and process payouts.

This solution is best for small to medium-sized businesses that prefer a ready-to-use solution with minimal development effort. It is ideal when companies want to quickly integrate a payout solution without building extensive front-end interfaces. For example, a business that wants to provide an eWallet service to its users without handling the complexities of account management and compliance would benefit from this integration.

Full API Integration

The Full API integration allows users to interact exclusively through the merchant's interface without visiting the i-payout platform. Merchants are responsible for the front end while using i-payout APIs for backend processes. This approach offers high customization, enabling merchants to seamlessly design their user experience and integrate i-payout functionalities. However, incorporating all functionalities via API requires a high level of integration effort and significant development.

This method is best for large businesses with robust technical teams capable of managing extensive integrations. It is particularly useful when businesses require complete control over the user experience and want to integrate payout functionalities into their existing systems. An example use case would be an enterprise incorporating payout services into its e-commerce platform without redirecting users to an external site.

Embedded Solution

In an Embedded Solution, users interact with i-payout functionalities embedded within the merchant's website. Responsibility is split between merchants handling the front end and using i-payout's pre-built UI components for specific tasks. This integration offers medium customization, allowing merchants to integrate specific functionalities without extensive development, and requires a moderate level of integration effort involving embedding scripts and minimal API integration.

This solution is best for businesses that want some customization but want to avoid handling sensitive information directly. It is ideal when companies want to integrate specific functionalities, such as KYC or bank account additions, using pre-built UI components to ensure security and compliance. For example, a merchant who wants to offer a seamless bank account setup experience on their website without building the UI from scratch would benefit from this integration.

Batch File Integration

The Batch File integration requires that you interact directly with the system every time you wish to make a payout. Batch files are used for account and transaction management, with merchants handling data preparation and file uploads. This option offers low customization, is limited to what can be achieved through file uploads, and requires an effort every time you want to make a payout.

This method is best for businesses with very limited technical resources. It is useful when businesses prefer managing transactions and accounts through batch file uploads rather than real-time API calls.

What's next?

Click the link below to integrate your chosen solution: