Skip to content
Merulan

Plaid setup

What an operator supplies to connect the Plaid Source, and the verification the provider requires.

Connecting Plaid exchanges a short-lived provider token for a stored grant. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Plaid refuses the connection until every item holds.

  • A Plaid account with production access for the products a Pipeline reads.
  • A bank login the account holder completes in the Plaid dialog.

Credentials

Plaid stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No lasting secret is typed into Merulan. The Plaid dialog returns a short-lived public token, Merulan exchanges it once, and the stored access token has no refresh half.

Scopes

Plaid requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • transactions

Plaid grants reach per product rather than per scope string, and transactions is the product this Source reads.

Verification

Provider app review governs the Plaid connection. Plaid reviews the application before granting production access, so a sandbox connection never carries live account data.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.