SwitchFlow routes across gateway accounts you own. Connecting a gateway hands SwitchFlow an API credential for that account; funds continue to settle directly into your gateway account as they always have.

​
Connect a gateway

In the dashboard, go to Connections → Add connection and provide:
FieldNotes
GatewaySTRIPE or ADYEN
API keyThe secret API key from your gateway dashboard (e.g. Stripe sk_live_…)
Merchant account IDRequired by some gateways (e.g. Adyen merchant account)

​
Verify the connection

A new connection starts as CONNECTED (credential stored). Click Verify to have SwitchFlow make a live test call against the gateway. Only VERIFIED connections can be used in routing rules. If verification fails, the status becomes VERIFICATION_FAILED with the gateway’s response — fix the credential and verify again.

​
How your credentials are handled

  • The raw key is accepted once, transmitted over TLS, and stored in an encrypted secret store. It is never echoed back in any API response and request-body logging is disabled on this path.
  • The database keeps only a reference and a masked fingerprint (e.g. sk_live_…4242) so you can recognize which key is connected.
  • At capture time the credential is fetched from the secret store and passed to the payment processor over an authenticated channel — it never appears in logs.

​
Disconnecting

Deleting a connection that is referenced by an active routing rule is blocked by default — remove it from your rules first (or use the explicit force option, which disables the affected rules). Stored credentials are destroyed on disconnect.