Your registration will be initiated until you have signed your contract and completed the open banking application form. Typically, some open banking institutions should be available within 2 weeks of initiation. Individual financial institutions must approve your application in order to enable open banking with their institution. Each institution follows their own timeline, so you will see some financial institutions available in open banking before others. Most open banking connections will be available within 6-8 weeks. Please note: Some institutions take longer to complete the open banking registration process.
Yes, SVGs are an open banking requirement. If you do not have an SVG of your favicon and logo, we can recommend a freelancer on Fiverr who can redraw pixel-based logos as an SVG, which usually runs under $20 USD.
You have four Config options:aggregation, for aggregation onlyverification, for verification onlyaggregation_and_verification, for mandatory aggregation followed by optional verificationverification_and_aggregation, for mandatory verification followed by optional aggregationAccount details can be accessed with any aggregation flow. However, if you want to access ongoing balance refreshes, user data including name or email, or account and routing numbers, you need to use one of the three verification configurations. If you have specific questions about which config is best for you, please email the specifics about your use case to support@fingoal.com.
The amount of historical data you receive depends on the specific financial institution linked. In most cases, opening banking connections provide more extensive data – often up to a 365-day lookback and in some cases longer. However, some open banking connections (like Capital One and Edward Jones) impose a 90 day historical transaction limit. For screen scraping sites, you may receive between 90 and 720 days of transactions depending on the specific financial institution. Be aware that screen-scraped accounts which have been dormant for several months may require you to use toDate and fromDate parameters on your API request to receive transactions.
You don’t need to set up webhooks, but we recommend it. The DATA_UPDATES event sends an automatic notification whenever user data changes, which minimizes the need to consistently call to determine if data has changed.
To set up your own webhooks, you’ll want to follow the guide provided here along with the Yodlee webhook docs to see the schema.FinGoal can also manually enter the URIs for callbacks into the portal, if you know what alerts you want and where you would like them to go.
When moving from development to production, an "Unauthorized User", could also mean you didn't switch over all of your creds and urls yet. Check to make sure that your credentials are consistent and correct for the environment. The error may also occur because you have not whitelisted your IP address. If you need to whitelist your IP address, please send it in IPv4, not v6, to support@fingoal.com or place it in your Slack channel.
Technical Errors can occur for a number of reasons. If you are testing, this is the first time linking this financial institution following an open banking initiation, or if the institution is a small bank/Credit Union that may not be regularly linked, please try the account linking a second time before reporting an error. If the Technical Error occurs more than once, please provide:A screenshot of the error code (Please open the inspect window in your browser, select the console tab and take a screenshot of the corresponding error codes—expand the dropdown, if necessary) A detailed description at what point during the account linking flow the error occurred (Ex: After selecting the PNC open banking tile, I entered user credentials, selected the MFA type, but never received the MFA code)Send the site ID if you know it and the name of the financial institution you are attempting to linkIf you entered user credentials, please include the Yodlee user ID, GUID, or loginName
No, FinGoal does have access to any user credentials. For open banking, credentials are passed directly to your bank and are not retained by Yodlee. Yodlee does retain user bank credentials for screen scraped accounts.
To ensure accounts are deleted, you can follow the Core API docs and call for specific account IDs to delete accounts on demand. Please note the response can be a bit misleading. If you are unsure if the account was deleted, place a GET/account request to determine if the account still exists. You can also delete the user wholesale, which will purge all associated accounts.