I'm attempting to get transactions on an account previously added (more than a few days ago).
The account was added to a test account on our sandbox but the account is real.
I use executeUserSearchRequest to initiate the search, with the parameters shown in the image below (screenshot from PhpStorm, while debugging).
The result can also be seen on the screenshot.
Please note that I've also attempted fetching transactions for another account on a different financial institution (that was added to the customer account on Yodlee again several weeks ago). It also returns no results.
When both accounts were added, they were added using addItemForContentService1 with a parameter to refresh right after adding (startRefreshItemOnAddition=true).
What can be the reason for this 'no transactions' reply? (although we know that there were transactions on those accounts).
Thanks
As per the screenshot it seems like you are filtering the transactions based on the containerType= 'stocks', this will return transactions for all the investment accounts for that user.
Also, you are passing the itemAccountId.identifier which is for a specific account.
It would be great if you check followings:
The actual account aggregated is an investment account?
The itemAccountId is correct for that account?
Else, you can just remove the itemAccountId.identifier param as it is non-mandatory field and try. You should get some transactions in response.
Related
I've used my live PayPal account to login to developer.paypal.com where I created 2 new accounts buyer# (personal) and seller# (business). I've implemented a PayPal plugin for a shop (CubeCart + PayPal Standard Payment Gateway plugin https://www.cubecart.com/extensions/payment-gateways/paypal-standard). When I complete an order (sandbox testing) I sign using buyer# email and password and complete the order. I can then click to view account and it shows "payment to", "unclaimed" and the amount I've paid. When I logout of this account and login as my buyer#, I see no transactions. If I log back into developer.paypal.com and go to transactions under "Sandbox" section and select any of the email addresses I see the same statement for all of them "You don't have any transactions".
If I login to sandbox.paypal.com using james-facilitator# account (business) there are no transactions here either.
If I login to sanbox.paypal.com using james-buyer# account (personal) there is only the one initial transaction here for the initial 9,999 funds
I've obviously missed something but I can't think what, I'm not sure how a sandbox account knows who it's seller should be but I've checked both sandbox seller accounts. I find it strange that the buyer account I used has registered the transaction but it seems like it's orphaned as there isn't any other record of it any where else including the developer.paypal.com sandbox transaction. I've tried this several times to see if I could get it working and I've also allowed for 24 hours just in case there was a delay somewhere.
I just want to be able to test transactions before going live.
Any help/advice?
Much appreciated :)
Cheers
James
Solved - silly really now I know but it was simply the email address I used to test the API. I used my main live account and I should have used the fake email address in my API call. Since my live controls the test accounts I assumed that this should have been used.
I using the executeUserSearchRequest to get transactions for bank,credit etc.
But I'm not able to get Bill Pay transactions.
Should I not be using this method to retrieve the lines, or perhaps I'm doing the search wrong. I know the account I'm using does contain lines as I've verified using another application that uses the yodlee api;s.
I using these settings
ContainerType: All
SplitType : ALL_TRANSACTION
transactionSearchRequest.searchFilter.itemAccountId.identifier = 9999999
where 99999 is the itemaccountid
all other values are defaults from the API testing tool
https://developer.yodlee.com/Aggregation_API/Aggregation_Services_Guide/Aggregation_REST_API_Reference/executeUserSearchRequest
You should be able to retrieve transactions for billpay using the same API i.e., executeUserSearchRequest. Please remove itemAccountId.identifier and try to get transactions, it will return transactions for all accounts.
You can then verify is transactions for your billpay account is present or not.
If you want transactions for specific account then you can first call getItemSummariesForSite API to get the account level details for the added account and from there you can use the itemAccountId and pass it on to executeUserSearchRequest API.
If you still face any problem, please share your memSiteAccId over our chat support and we will be able to help you.
How do people deal with the situation of bounced checks when getting Yodlee transactions through the Aggregation API?
Our app only retrieves posted transactions and it has led to an issue.
Most banks seem to balance the bounced check situation by providing posted transactions for both the initial check disbursement (negative amount) and for the bounced check (positive amount). Bank of America, however only posts the positive amount transaction - (the one the increases the balance of the consumer's bank account) - the original transaction never gets past the pending stage. and since the original transaction (the check) is never posted it results in an incorrect increase in balance on the consumer side.
Any thoughts?
If you are customer of Yodlee, then you can reach out to Yodlee's support team and raise your issue with details like BankName, SiteId,memSiteAccId and cobrandId. Yodlee's data team will look into it and would be able to help you out.
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.
Customers have started to find that the transaction description field provided by Yodlee is changing, without the original / older transaction being removed and a new one being created in it's place.
Our expectation up to now is that if any changes take place, the old transaction is deleted and a new one is created, with a new internal transaction_id used by Yodlee. This is the system that is used for moving pending transactions to posted.
Is it now standard practice that merchant descriptions change frequently within the same transaction ID, or is this being done in error? Should we open a service request for the problem to be resolved?
Yodlee scrapes transactions from the Bank websites in each refresh for a specific duration- 30days, so if there are few transactions which got scraped and filed into Yodlee DB in previous refresh and now Bank has updated the description of those transaction while keeping rest of the information same. And say those are coming in current refresh also, then Yodlee will apply its logic and will update the description without changing anything else. But the chances when Bank Website does this is very rare.
If you are facing this kind of issue repeatedly/frequently then we suggest you to open a service request, with all the relevant information.
Note: The above scenario is in the case of Posted Transactions only.