Plaid vs Salt Edge Account Information

Plaid

Public OpenAPI file, llms.txt with about 250 entries and a Markdown twin of every docs page. No prices before a Production application, and Transactions, Liabilities and Investments bill per Item each month until removed.

Salt Edge Account Information

5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.

Plaid

1. Point calls at https://sandbox.plaid.com until you hold a Production secret; request shapes are the same
2. Create a sandbox Item with /sandbox/public_token/create and ins_109508, then /item/public_token/exchange, no Link UI needed
3. Use /transactions/sync with its cursor and back off on 429 RATE_LIMIT_EXCEEDED yourself, since no Retry-After comes back
4. Call /item/remove when the user is done, or subscription products keep billing
5. Send an idempotency_key on /transfer/authorization/create so a retried request can't authorise twice

Salt Edge Account Information

1. Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error
2. Start with fakebank_simple_xf in country XF; it needs no bank sandbox
3. Sign requests from the start even in Test, so the move to Live doesn't change your client
4. Follow next_page from the meta block rather than building from_id URLs yourself
5. Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done