Third-Party Integration Setup Guide

This guide explains the standard process for connecting your app to supported third-party integrations (such as POS systems and other service providers). While each provider may have slight differences, most integrations follow the same initial setup steps.

Overview

To enable an integration, your third-party provider must authorize and release API credentials that allow our system to securely connect to your account. These credentials are issued directly by the provider and must be requested by you as the account holder.

Once the credentials are released, our team will handle the technical configuration and complete the integration on your behalf.

Step 1: Contact Your Provider’s Support Team

Reach out to your third-party provider’s support representative or account manager and request API access for your account.

When contacting them, please:

• Request the API credentials required for third-party integrations
• Specify that the integration will be used to connect your account to your mobile app
• Ask that access be authorized and released for production use
• CC our team on the email so we can assist once access is granted

This step must be completed by you, as the account holder, since providers will not release API credentials directly to third parties.

Step 2: Provider Authorization & API Release

Once your provider approves the request, they will either:

• Send the API credentials via email, or
• Confirm that access has been granted and shared securely

No technical action is required from you beyond approving and sharing this access.

Step 3: Integration Setup by Our Team

After API access has been authorized and shared, our team will:

• Securely store the credentials
• Configure the integration on our end
• Test the connection to ensure data is syncing correctly

We will reach out if any additional information is needed.

Important Notes

• Integration timelines depend on how quickly the provider releases API access
• Some providers may have additional approval or compliance requirements
• POSaBIT is excluded from this guide: It’s integration process is more involved and requires separate, provider-specific steps

If you have questions at any point, please contact our support team and we’ll be happy to help.