Plaid is a fintech company that facilitates communication between financial services apps and users' banks and credit card providers for the purpose of exchanging data seamlessly and securely
Story:
As user of BudgetSimple I should be able to seamlessly acquire my bank and credit card transaction data to enrich my BudgetSimple profile.
Implementation (extremely vague plan)
Implement Plaid Link and Transactions.
Update Django Models and instantiate new models: Accounts.
Plaid Link
Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access their accounts via the Plaid API.
Build functionality around transaction/get and transaction/sync. Use /get the first time a user links their account, and use /sync each subsequent time to update new transaction--the update cadence is TBD, but in the sandbox let's say daily, or use your best judgment.
Save account data, like name, subtype, type, etc in a new Accounts model. Save transaction data in the transaction model and or removing from the model as needed. We are keeping the upload document option for now so don't delete stuff related to that. You may need to add "Category" as a new field in the transaction model.
Plaid
Plaid is a fintech company that facilitates communication between financial services apps and users' banks and credit card providers for the purpose of exchanging data seamlessly and securely
Story:
As user of BudgetSimple I should be able to seamlessly acquire my bank and credit card transaction data to enrich my BudgetSimple profile.
Implementation (extremely vague plan)
Plaid Link Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access their accounts via the Plaid API.
https://plaid.com/docs/link/
Transaction endpoint Retrieve and refresh up to 24 months of historical transaction data, including geolocation, merchant, and category information.
https://plaid.com/docs/api/products/transactions/
Build functionality around
transaction/get
andtransaction/sync
. Use /get the first time a user links their account, and use /sync each subsequent time to update new transaction--the update cadence is TBD, but in the sandbox let's say daily, or use your best judgment.Save account data, like name, subtype, type, etc in a new Accounts model. Save transaction data in the transaction model and or removing from the model as needed. We are keeping the upload document option for now so don't delete stuff related to that. You may need to add "Category" as a new field in the transaction model.
Example response body from
transaction/get
: