I'm wondering what happens with auto refreshes on Yodlee's end once an account fails to authenticate the user's credentials?
Does the daily refresh still take place, or is this process paused until the credentials are updated?
I guess what I want to know is if our user changes their bank credentials, and not the credentials stored in Yodlee, will they eventually be locked out from Yodlee continuing to attempt to login?
Thanks.
Let us say a consumer changed his/her bank credentials at the bank website while Yodlee system credentials are not updated. Yodlee will try to refresh the consumer's account at scheduled time and it will fail with LOGIN_EXCEPTION(error code- 402) which means credentials are not valid.
Once, Yodlee system gets this error code it will refrain from doing any more retries(which may result into Account Locked or some other issues) and will wait for consumer to update the credentials into Yodlee system.
Related
Here is the scenario:
User logins to the bank successfully (via Fastlink)
Right after user logs in, I get user's provider_accounts (via /providerAccounts API)
Then when I call to get the accounts, (via /accounts) I sometimes get empty response (zero accounts found?)
When I try later (seconds or minutes after) I get some accounts information back.
Is this because Yodlee is still trying to gather account information when I'm making /accounts api call?
This is because the accounts are still being added/linked.
Using the requestId and providerAccountId provided by FastLink callback, you need to poll continuously to know the refresh status of the account linking process and once it's done, you can call the get accounts.
Read more about the refresh status in the "Add/Update Account Process Status" section.
Yodlee makes things easier now with webhooks. Read more here:
Using Webhooks with the Yodlee Core API
TL/DR: You need to wait for the add/link completion before retrieving the accounts.
I am using auth0 in my existing regular php web application.
I have free as well as paid users in my site. For free users registration process is simple, I call the create user api which triggers the verification email.
But for paid users I have a multistep form. In first step users enters his information and registered as a free user in application then redirected to payment page. I can not call auth0 reg api after first step as user will get immediately verification email before payment.
If I call it after successful payment then its impossible to track if user bails out(Doesn't fill payment form, but already registered as a free user).
Please suggest what approach I should follow.
Thanks in advance
Make sure that you disabled public signups (this endpoint) and instead are performing the registration of users from your backend through the Management API create user endpoint.
Then you can use the verify_email parameter to indicate that a verification email should not immediately be send after user creation. You could then later use this endpoint to trigger a verification email to be sent after the payment form is completed.
If you have want to achieve best result i think you must follow below step to get rid of this problem:
1. Remove public signups in your application by trying this authenticating signup.
2.Perform the registration of individual user by this way create user's
3.Now you can simply use the verify_email parameter.
This parameter can be easily use post verification email process which prevent the issue of signup/signin before making payment.
Hope you got it & feel free for any help.
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'm using yodlee live API to link the bank transaction details.
Invalid bank account details accepts, when we add new site account in yodlee via live API, For example, the the account details like xxxxx and yyyyy, then the account added successful.
It's normal or any settings to be turned on in yodlee account or API parameters?
How can i validate the account details? while user add new site account?
Thanks in advance.
Though Yodlee accepts the invalid details/credentials, the account would fail. This would be represented by an Error code such as 402, which would mean that the credentials are wrong.
This is normal setting and teh only way you can validate if the details are right is by checking the status of the account. The error code should be "0" if everything is right.
Hope this helps. You can get more details on error codes under different scenarios #Error Code
Hope this helps
-Vijay
In short: Yodlee doesn't know the username/password entered during add account are correct or not; it has to validate the same with Bank website.
To explain you the process:
When you are adding a particular Bank account, you provides the username/password(it may be correct or incorrect) Yodlee doesn't know and can't validate at the time of submission. Yodlee takes the inputs(username/password) and submits the same to the Bank website(which consumer had selected); meanwhile you'll receive a response from API- addSiteAccount1, which will have the code as 801 (Refresh Never Done and Yodlee is going to update your account).
Once Bank website validate the same and found them incorrect Yodlee return 402 error code(invalid credentials), you need to call getSiteRefreshInfo API to check the same in loops each of 3-4sec.
The Amazon FPS documentation says in several places that a customer can cancel their recurring payment token at any time from Amazon's UI, and that Amazon will then notify the application that the token has been cancelled. I'd like to test this.
How does a user do that?
As a test user, I see nothing in my Amazon Payments UI that shows my existing recurring payment tokens so I can cancel them. Googling for an answer gives me lots of results explaining how my application can cancel the token, but none explaining how the user can cancel their own token behind my app's back.
You should see any tokens that your account has authorized in Your Account > Edit My Account Settings > Manage my payment authorizations.
From there you should be able to cancel your reoccurring token.