New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document what the best practices are for URIs and fields to store in databases #63

Closed

mahmoudimus opened this issue Apr 5, 2013 · 1 comment

Contributor

mahmoudimus commented Apr 5, 2013

Migrated from balanced/balanced-api#209

from @mjallday:

It's probably best to just associate the account_uri with a local user ID. everything else can be derived from that account_uri. However, if you want to display transactions in real time then it will be slow so you may want to keep debit_uris locally as well.

and @bradfordb commented (balanced/balanced-api#209 (comment))

mahmoudimus mentioned this issue

Best practices for what uri's should be stored balanced/balanced-api#209

Closed

Contributor Author

mahmoudimus commented Apr 5, 2013

Right off the bat:

the account uri => map that to a user on your system
for any transaction coming INTO your system (via debiting bank account / charging a card etc) => store the debit uri with that txn in your system
for any transaction LEAVING your system (via ach credit / depositing to a bank account ) => store the credit uri with that txn in your system

remear closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment