Configs - Svb

Aggressive failover configs can cause race conditions – sending the same payroll ACH twice if both SVB and Mercury appear “active” simultaneously. Use distributed locks (e.g., Redis Redlock) in your config driver.

Unlike standard APIs secured only by HTTPS, banking APIs often require mTLS. This means the client (your server) must present a valid certificate to the bank's server to establish a connection.

Implementation:

A modern SVB config file (or secret store) now looks like this:

# banking-config.yaml
banks:
  primary:
    name: "SVB (new entity under First Citizens)"
    routing: "121140399"
    api:
      url: "https://api.firstcitizens.com/svb/v2"
      oauth_client: "prod_svb_01"
    limits:
      daily_ach: 5000000
      daily_wire: 10000000
    status: "active"
secondary:
name: "Mercury"
routing: "121141822"
api:
url: "https://api.mercury.com/v1"
limits:
daily_ach: 2000000
status: "warm_standby"
tertiary:
name: "JPMorgan"
routing: "021000021"
api:
url: "https://api.jpmorgan.com/treasury/v1"
limits:
daily_wire: 25000000
status: "cold_failover"