Skip to main content
The Connectivity Service provides a connector framework that allows you to integrate with any payment provider. It pre-packages the integration logic for some of the most popular payment providers, as per the table below, with the goal of providing connectivity to as many local and specific payment providers as possible. You can also create your own custom connectors by implementing the Connector Framework and taking inspiration from the existing connectors in the Github repository.

​
Logic behind the connectors

When installing a connector on Formance Console or by using the API, you will be able to configure a polling period that will default to 2 minutes if not specified. This polling period will be used to periodically poll the payment service provider in order to fetch all the data we need: Payments, Accounts, Transfer/Payouts statuses when you create your transfer initiation etc.

​
Monitoring connector schedules

To check when a connector last pulled data, you can use the Connector Schedule APIs.

​
Finding the schedule ID

Each connector has schedules that are automatically generated when the connector is installed. The schedule ID follows this format: 
{stackID}-{connectorID}-{capability}
For example: stack123-abc-FETCH_ACCOUNTS To find the schedule IDs for your connectors, use the List All Connector Schedules endpoint.

​
Checking last pull time

Once you have the schedule ID, call the List Connector Schedule Instances endpoint with the schedule ID to see the history of data pulls, including the most recent one. This is useful for:
  • Debugging synchronization issues
  • Monitoring connector health
  • Verifying data freshness

​
Supported processors

ConnectorAccounts Data LayerExternal Accounts Data LayerAccounts Balances Data LayerTransactions Data LayerBank Account CreationTransfer InitiationPayout Initiation
adyen✅❌❌❌❌❌❌
atlar✅✅❌✅❌❌❌
bankingcircle✅❌✅✅✅✅✅
column✅✅✅✅✅✅✅
currencycloud✅✅✅✅❌✅✅
generic✅✅✅✅❌❌❌
increase✅✅✅✅✅✅✅
mangopay✅✅✅✅✅✅✅
modulr✅✅✅✅❌✅✅
moneycorp✅✅✅✅❌✅✅
qonto✅✅✅✅❌❌❌
stripe✅✅✅✅❌✅✅
wise✅✅✅✅❌✅✅

​
Capabilities definitions

​
Accounts Data Layer

Provide the ability to fetch internal accounts from the payment provider. Internal accounts are accounts where you have operational control, such as digital e-wallets or payment service provider accounts.

​
External Accounts Data Layer

Provide the ability to fetch external accounts, which represent accounts used as destinations for transfers, such as the user’s bank accounts.

​
Accounts Balances Data Layer

Provide the ability to fetch the internal accounts balances. It is important to note that none of the payment providers supports the fetching of the balances history for accounts.

​
Transactions Data Layer

Provide the ability to fetch the transactions happening on the payment provider and relate them to the accounts previously fetched.

​
Bank Account Creation

Provide the ability to create a bank account on the payment provider side. This is useful when you want to create a bank account for a user and then initiate a payout to that bank account.

​
Transfer Initiation

Provide the ability to initiate a transfer from one internal account to another internal account.

​
Payout Initiation

Provide the ability to initiate a payout to an external account from an internal account.