Bring your own Plaid

Clients use their own Plaid account for now.

This setup keeps BellPathOS client-facing and low-cost while you grow. Clients create their own Plaid developer app, deploy their own Worker, and enter only the Worker URL into BellPathOS. Plaid secrets stay out of the public browser build.

Client-owned PlaidNo BellPath hosting requiredWorker secrets only

Security rule

Do not put Plaid secrets in public JavaScript.

A Plaid client ID can be referenced in setup records, but the Plaid secret and access tokens must be stored in a private backend such as a client-owned Cloudflare Worker. BellPathOS stores only endpoint configuration and non-secret connection metadata in the browser.

Important: the secret field below is used only to generate setup commands in this page. It is not saved by default. The client should paste it into Cloudflare Worker secrets, then clear the form.

1 - Client Plaid account

Plaid app credentials

Plaid environment Plaid client ID Plaid secret Products Country codes Webhook URL

2 - Client-owned Worker

Private connector endpoint

The Worker owns Plaid token exchange. BellPathOS calls this Worker instead of Plaid directly.

Worker base URL Create link token endpoint Exchange public token endpoint Accounts endpoint Transactions endpoint Investments endpoint

3 - Worker secret commands

Copy these into the client's Cloudflare Worker project

These commands are generated locally in the browser. BellPathOS does not save the Plaid secret.

Open setup guide

Fill in Plaid client ID, secret, environment, and Worker base URL, then generate commands.

4 - Status

Local BellPathOS connector record

Saved record includes worker URL, environment, products, country codes, and endpoint URLs. It does not include Plaid secret or Plaid access tokens.

Ready.

Return to Client Setup Launch Check