The Connectivity Service provides a connector framework that integrates with payment providers and exposes a stable set of capabilities per connector — fetching accounts, balances, payments, initiating transfers, and so on. This page is the per-connector capability inventory.
You can also create your own custom connectors by implementing the Connector Framework and taking inspiration from the existing connectors in the GitHub repository.
For operational guidance — polling cadence, monitoring schedules, health checks, and recovery — see Operations.
How to read this page#
The matrix below is generated at build time from docs/other/connector-capabilities.json in formancehq/payments, one snapshot per Payments release. Flip the Payments picker in the sidebar to see what a stack pinned to that release exposes — new connectors appear, capabilities added later light up.
The Edition column shows which connectors ship in the open-source Community edition (CE) versus the Enterprise edition (EE). EE connectors require an EE license to install.
PSP connectors#
| Connector | Edition | Accounts | External Accounts | Balances | Payments | Other Fetches | Bank Account Creation | Transfer Initiation | Payout Initiation | Webhooks |
|---|---|---|---|---|---|---|---|---|---|---|
adyen | CE | ✓ | — | — | — | — | — | — | — | ✓ |
atlar | CE | ✓ | ✓ | — | ✓ | ✓ | — | — | — | — |
bankingcircle | CE | ✓ | — | ✓ | ✓ | — | ✓ | ✓ | ✓ | — |
column | CE | ✓ | ✓ | ✓ | ✓ | — | ✓ | ✓ | ✓ | ✓ |
currencycloud | CE | ✓ | ✓ | ✓ | ✓ | — | — | ✓ | ✓ | — |
generic | CE | ✓ | ✓ | ✓ | ✓ | — | — | ✓ | ✓ | — |
increase | CE | ✓ | ✓ | ✓ | ✓ | — | ✓ | ✓ | ✓ | ✓ |
mangopay | CE | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
modulr | CE | ✓ | ✓ | ✓ | ✓ | — | — | ✓ | ✓ | — |
moneycorp | CE | ✓ | ✓ | ✓ | ✓ | — | — | ✓ | ✓ | — |
qonto | CE | ✓ | ✓ | ✓ | ✓ | — | — | — | — | — |
stripe | CE | ✓ | ✓ | ✓ | ✓ | — | — | ✓ | ✓ | ✓ |
wise | CE | ✓ | ✓ | ✓ | ✓ | ✓ | — | ✓ | ✓ | ✓ |
PSP connectors model traditional payment service providers — single-asset balance movements on a single account leg. See PSP Connectors for the catalogue.
Exchange connectors#
| Connector | Edition | Accounts | Balances | Payments |
|---|---|---|---|---|
coinbaseprime | EE | ✓ | ✓ | ✓ |
fireblocks | EE | ✓ | ✓ | ✓ |
Exchange connectors surface trading-venue activity. Two primitives that don't exist on traditional PSPs are surfaced as their own columns from Payments 3.3.0: Orders (instructions placed against an order book) and Conversions (atomic two-asset swaps that bypass the order book).
See Exchange Connectors.
Open Banking connectors#
| Connector | Edition | Accounts | External Accounts | Balances | Payments | Webhooks |
|---|---|---|---|---|---|---|
plaid | CE | ✓ | ✓ | ✓ | ✓ | ✓ |
powens | CE | ✓ | ✓ | ✓ | ✓ | ✓ |
tink | CE | ✓ | ✓ | ✓ | ✓ | ✓ |
Open Banking connectors are read-only data aggregators backed by Payment Service Users. See Open Banking.
Capability definitions#
Accounts#
Fetch the 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. Maps to CAPABILITY_FETCH_ACCOUNTS upstream.
External Accounts#
Fetch external accounts, which represent accounts used as destinations for transfers, such as the user's bank accounts. Maps to CAPABILITY_FETCH_EXTERNAL_ACCOUNTS.
Balances#
Fetch the internal-account balances. None of the upstream providers expose historical balance series, so balances are always point-in-time. Maps to CAPABILITY_FETCH_BALANCES.
Payments#
Fetch payments happening on the provider and relate them to the accounts previously fetched. Maps to CAPABILITY_FETCH_PAYMENTS.
Other Fetches#
Pull provider-specific objects that don't fit any of the standard streams (mandates, beneficiaries, …). Surfaced under metadata on the relevant resource. Maps to CAPABILITY_FETCH_OTHERS.
Orders#
Fetch trading orders placed on the provider — instructions to exchange one asset for another at a price. Each order carries a direction (BUY or SELL), a source and destination asset, a type (MARKET, LIMIT, STOP_LIMIT, TWAP, VWAP, PEG, BLOCK, RFQ), a status that follows the fill lifecycle (PENDING, OPEN, PARTIALLY_FILLED, FILLED, CANCELLED, EXPIRED, FAILED), ordered and filled quantities, time-in-force, fees, source and destination account references, and an append-only adjustment list capturing every observed state change. Maps to CAPABILITY_FETCH_ORDERS (Payments 3.3.0+).
Conversions#
Fetch atomic two-asset swaps — moving a balance from one asset to another at the provider, with distinct source and destination amounts. Each conversion carries source and destination assets and amounts at each side's precision, fees, a status (PENDING, COMPLETED, FAILED), and source and destination account references. Conversions are commonly used for stablecoin redemption (1:1 swaps such as USDC ↔ USD) and for FX-style asset swaps. Maps to CAPABILITY_FETCH_CONVERSIONS (Payments 3.3.0+).
Bank Account Creation#
Create a bank account on the payment provider side. Useful when you want to create a bank account for a user and then initiate a payout to that bank account. Maps to CAPABILITY_CREATE_BANK_ACCOUNT.
Transfer Initiation#
Initiate a transfer from one internal account to another internal account. Maps to CAPABILITY_CREATE_TRANSFER.
Payout Initiation#
Initiate a payout to an external account from an internal account. Maps to CAPABILITY_CREATE_PAYOUT.
Webhooks#
Subscribe to provider webhooks and translate them into Connectivity events. The matrix collapses the upstream CAPABILITY_CREATE_WEBHOOKS and CAPABILITY_TRANSLATE_WEBHOOKS pair into a single column — they always ship together.