Imagine a scenario where two people hold a joint account. Each person signs up for an individual account on a web application which in turn creates two individual consumer accounts with Yodlee. Both people proceed to add their joint account via FaskLink, each with their respective bank/credit card credentials.
So now we have a single joint account linked to two Yodlee consumer accounts. Will this cause all items/transactions in that joint account to be duplicated across the two individual Yodlee accounts?
Yes, as it has been aggregated with two different set of credentials. It will be treated as two separate accounts and you'll see the duplicates.
Related
I am just trying out the open-API specs provided by tmforum https://www.tmforum.org/open-apis/ and cannot seem to figure out the difference and actual purpose of the financial account resource mentioned in account management API specs. Can someone please elaborate?
The financial account aggregates the amounts of one or more billing accounts owned by a given party. For example, as a customer, I may have multiple billing accounts (e.g. for broadband services for multiple properties) - the financial account is the aggregation of these billing accounts.
I am working on a web application which is based on Google App Engine (GAE). The requirement of the application is that one user can be associated with multiple company accounts.
My application has two main types of accounts. One is that main Admin/Company account. Other is the employee account (i.e. the persons who work under a company). Now, what I want to do is that to allow an employee to work under more than one companies, but he does not have to make a separate account for each company. His single account can be associated with multiple companies.
I have explored different platforms which are already supporting this feature. The major ones which I found are Slack and Asana. And my problem can be perfectly mapped to what Slack is doing right now i.e. I create a single account on Slack and I can join multiple workspaces on Slack using this single account.
I want to achieve the same in my application too. I am curious that how Slack is supporting this feature right now? Does it send some ID with every request to the server which indicates that the activity which just has been done is associated with the workspace under this ID? Or there is some unique sort of token associated with every workspace (on Slack API level)?
I do have such a model in my app. A unique auth_token is associated with every company account. So, I am thinking that when an employee wants to do an activity for a specific company he will send this unique token with the request to the server so that server knows for which company the activity was performed.
Does anybody know what is the best way of achieving this?
There are two different concepts at work here:
Relation between account and company / workspace
The data structure for the Slack account is designed such that it can be linked to multiple Slack workspaces, e.g. in SQL you would have a many-2-many relation between the accounts and the workspaces table.
Staying logged in
The way Slack and others Single-Sign-On provides like Google SSO keep you logged in is by settings a browser cookie. That cookie would usually be some kind of crypto hash and the SSO provider will use it to identify to which account the current user belongs to or to request a login via OAuth if the cookie is missing / invalid.
This can also be achieved partly with server sessions (which also uses cookies). Using server sessions is easier to implement than implementing your own (secure) cookie solution, however the user will only stay logged in as long as the browser stays open. But that should be sufficient for most solutions.
Note that tokens for the Slack API work very differently. e.g. they have to be generated per workspace, user and app.
In our application, there are occasionally cases where a bank account is disconnected using removeItem and subsequently reconnected using addItemForContentService1 from the Yodlee SOAP aggregation API. There is anecdotal evidence to suggest that, until relatively recently (1-2 months ago?), the transaction IDs for bank transactions that had already been retrieved from a prior connection would be identical when the same bank account was reconnected. However, now it appears that, when a bank account is disconnected and then reconnected in this way, all of the bank transactions are now assigned new transaction IDs, thus breaking any client logic that attempts to match transactions from previous connections to the same bank account. This can be a serious problem since, for example, it can produce many duplicate transactions for accounts that have already had bank reconciliations performed.
My questions are whether there now exists a reliable mechanism to identify the same bank transactions when disconnecting and reconnecting to the same bank account using removeItem and addItemForContentService1 and, if so, what is it?
When you call removeItem the account is deleted and also all the data related to that account is deleted. Now when you call addItemForContentService1 a new itemId is created for that account and data is freshly added to the data base considering the account as new. Since there is no mapping to the old data , so you will not get the same transaction IDs for those transactions.
Hence removeItem should only be called if you wish to delete the account and it's data from Yodlee platform.
Is there a way to get transactions for all container accounts that belong to a specific site aggregated using Yodle APIs?
For example, the American Express Cards (siteId: 12) have bank, credits, loans and etc enabled containers.
So, can we get the transactions for all enabled container accounts for a single site?
If you mean to ask this- "Is there a way to get transactions for all the accounts(all containers) belongs to a particular site?" Then.
Yodlee provides two ways to get the transactions.
Getting transactions for a specific account i.e., you need to provide itemAccountId for each account to get the transactions for the specific account using executeUserSearchRequest API.
Getting transactions for all the accounts i.e., you need not to provide itemAccountId for any of the particular account while provide rest of the input parameters to get transactions using executeUserSearchRequest but this will return you transactions for all the accounts. Using your example, it will give you transactions for all the container present under SiteID-12 as well as other sites added by the consumer. Though you can use the second approach to get the transactions for all accounts and then filter it out for all containers belongs to a specific site. You can use the sumInfoId(ContentServiceID) present in the response for each transaction.
I'm having a data issue I'm not sure how to handle.
Scenario: A company has a shared credit card. Which means, it is one account, but two people have access to the account, each person with his own credit card with his name on it. Let's call these people Charles and David, and assume they have a Chase account.
When I add this Chase login to Yodlee, it pulls the account THREE times, as:
"Chase - Credit Card - CREDIT CARD"
"Chase - Credit Card - DAVID"
"Chase - Credit Card - CHARLES"
It does this even though they are the same account. (I guess when you login to Chase it shows up multiple times).
All three are coming in with different ID numbers. So there is no way for me to know they are all the same account. My code thinks they are three different accounts, because they have different names and ID numbers.
As a result the account gets stored in my app three times, and the transactions three times.
What do you recommend?
Here are some suggestions:
First thing is to look for a particular site i.e., if Yodlee supports the Business Card site for that particular institution or not. As sometimes some of these Bank websites have a different login URL which can be either accessed by a different credentials or might be by the same and that will show you only 1 actual credit card account instead of 3.
In case the Business site is either not available or not supported by Yodlee(though you can request Yodlee to support the site and it could be prioritized based on the business use case), else you could call deactivateItemAccount API. This will deactivate a particular itemAccount and you can call this for those duplicate accounts.