Skip to main content
Reuse your own Plaid connection to link a customer’s bank account to Natural, so their wallet can be funded from their bank.
This guide is only relevant if you have a Plaid account for your platform.

Get a processor token

If you already use Plaid, reuse the customer’s existing connection instead of Natural asking them to link their bank again.
1

Run Plaid Link for the customer's bank

Run your existing Plaid Link flow for the customer’s institution. On success, Plaid gives you a public_token.
2

Create a processor token scoped to Natural

Exchange the public_token for your own Plaid access_token, then call Plaid /processor/token/create for the selected account_id with processor: "natural". Plaid returns a processor_token scoped to that one account. You keep the Plaid item and access token; Natural only receives the processor token.
3

Send the processor token to Natural

Pass the processor_token to POST /external-accounts/processor-token with the customer’s partyId.
The full Plaid walkthrough lives in Link a bank account. Nothing about obtaining the token changes when the account belongs to a customer: the only difference is that partyId is the customer’s party. Call POST /external-accounts/processor-token with the customer’s partyId and processorToken.

Keep track of the account

Store the eac_* id from the link response for your own records and account picker. GET /external-accounts lists the accounts linked to your own party, so it will not show a customer’s accounts; the link response is where you capture theirs. With the account linked, the customer’s wallet can be funded from their bank, and your agent can move money on their behalf.