Plaid
live · conformance passing
Models Plaid as Sandbox answers an application — Link sessions and Sandbox public tokens, the Item and its accounts, cached versus live balances, ACH numbers and their verification, Transactions Sync and the legacy read, recurring streams and Enrich presets, Identity and Identity Match, Investments, Liabilities, Statements, Assets reports, Transfer with its ledger, users and OAuth, and institutions — against First Platypus Bank as Sandbox's user_good, with every envelope, token shape and replay rule taken from live Sandbox and checked by a replayed differential corpus. What Sandbox cannot do on demand is the point: a pending charge posts when the environment advances, a Link session finishes, an Item falls into ITEM_LOGIN_REQUIRED and is repaired through update mode, a report is built, a balance endpoint answers BALANCE_LIMIT, and every change arrives as a signed webhook.
- Category
- Banking
- Environment key
- a 30-character token, no prefix
- Verified against
- plaid-python 44.0.0
- Replaces
- Plaid Sandbox, whose Items drift, whose updates arrive on their own schedule and whose rate limits cannot be summoned
What it models
Records your code can read, write and edit for the life of the environment. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- clients
- link_sessions
- public_tokens
- items
- access_tokens
- accounts
- auth_numbers
- transactions
- transaction_events
- webhooks
- webhook_keys
- account_owners
- securities
- holdings
- liabilities
- recurring_streams
- transfer_ledgers
- transfer_authorizations
- transfers
- transfer_events
- transfer_refunds
- transfer_sweeps
- asset_reports
- asset_report_audit_copies
- users
- oauth_tokens
- consent_events
- statements
Verified in CI against
- pythonplaid-python44.0.0