_Docs/
Get StartedModulesPlatformDeployCookbookChangelogReference
_Stack
_Modules
  • Ledger
  • Numscript
  • Connectivity
    • Capabilities
    • Operations
    • Accounts
    • Payments
    • Transfer Initiation
    • Account Pools
    • Payment Service Users
    • Connectors
      • Generic ConnectorEE
        • Getting Started
        • How it Works
      • PSP Connectors
        • Adyen
        • Atlar
        • Bankingcircle
        • Column
        • Currencycloud
        • Increase
        • Mangopay
        • Modulr
        • Moneycorp
        • Qonto
        • Stripe
        • Wise
        • Banking BridgeEE
        • RoutableEE
      • Exchange Connectors
        • Coinbase PrimeEE
          • Payments
          • Conversions
          • Orders
        • FireblocksEE
        • BitstampEE
      • Open BankingEE
        • Getting Started with Open Banking
        • Plaid
        • Tink
        • Powens
      • Build a connector
  • WalletsEE
  • FlowsEE
  • ReconciliationEE
  1. Modules
  2. Connectivity
  3. Connectors
  4. Generic Connector
Generic Connector
Connectivity

Generic Connector

The Generic connector is a thin shim over an HTTP service you run yourself. Use it when no Formance-shipped connector exists for the upstream you need to integrate, or when you want the integration to live in your own infrastructure for compliance, vendor-neutrality, or operational reasons.

Formance's side stays generic: the platform calls a small set of HTTP endpoints on your service to fetch accounts, balances, and payments, and forwards transfer / payout initiation requests when configured. Your service is responsible for the upstream-specific glue — auth, rate limiting, format conversion.

Available pages#

Getting Started

Install the Generic connector pointed at your HTTP service.

How it Works

The wire protocol Formance expects from your service — endpoints, payloads, error semantics.

When to reach for it#

The Generic connector is the right tool when:

  • You're integrating with a provider Formance doesn't ship a connector for, and waiting for one isn't an option.
  • You already operate a service that talks to the upstream, and want Connectivity to consume it through a stable contract instead of duplicating the integration.
  • You need the integration in your own VPC for regulatory reasons, with Formance reading from it across a controlled network boundary.

For first-party Formance-shipped integrations, see PSP Connectors, Exchange Connectors, and Open Banking. To contribute a new first-party connector upstream, see Build a connector.

ConnectorsGetting Started
On This Page
  • Available pages
  • When to reach for it