Account Aggregator Hackathon Tech FAQ
03 Jul 2020
This FAQ is for the teams participating in our Account Aggregator hackathon.
AA Sandboxes For AA Hackathon
Please register on the signup page of each of these AA sandboxes. Each AA will contact you. For support please contact each of the Account Aggregators directly. If you have trouble contacting any of them, let us know.
|Account Aggregator||Sandbox URL||Support Contact Info|
|All sandboxes are available 24x7! What are you waiting for? Hack on!|
Onemoney: There is no usage limit. API keys will be provided through our developer portal.
Finvu: There is no usage limit on the sandbox and key would be provided
Perfios: There is no usage limit
There is no preference on the programming languages as the ecosystem is API driven, it’s your choice, however, reach out to specific AA sandbox providers for any restrictions.
Onemoney: There are no restrictions from Onemoney as to what your programming languages can be. Examples on our portals are in node.js.
Finvu: There are no restrictions from Finvu on the programming language. Some of our sample code has been illustrated in Java. All APIs are REST based.
Perfios: The APIs are RESTFull APIs. Use any language, we will support you.
Onemoney: We provide details of SDKs once you log in into the developer portal.
|Category Code||Category Name||Description||Purpose|
|1||Personal Finance||Wealth management service||101|
|1||Personal Finance||Customer spending patterns, budget or other reportings||102|
|2||Financial Reporting||Aggregated statement||103|
|3||Account Query and Monitoring||Explicit consent for monitoring of the accounts||104|
|3||Account Query and Monitoring||Explicit one-time consent for the accounts||105|
See http://sahamati.org.in/account-aggregator-key-resources or the schemas are available at the ReBIT site https://api.rebit.org.in
All 23 schemas will not be available for the hackathon teams. The following will be available,
– Deposit schema
– Recurring Deposit
– Term Deposit
– Mutual Fund
We encourage you to get your app to work with multiple AAs.
A few AAs are also providing access to an FIU module so teams can focus on building their specific FIU use case and minimise time spent on data connectivity. These include Finvu, OneMoney, Perfios and Yodlee.
The Deposit schema has the details of the bank statements. The schemas are on http://sahamati.org.in/account-aggregator-key-resources/
This would be available through direct interaction with the AA sandbox providers.
Refer to the AA sandbox providers who are also providing ability to add data.
All AAs have the same set of API and no difference is anticipated as they need to meet the standards published by ReBIT.
Currently, the ecosystem does not support consent for joint account holders
No. Loan information, liabilities are not covered in the AA ecosystem. Refer to this FAQ on the supported schemas.
No, you can only share information using your VUA via that AA.
No, consent porting is not supported in the ecosystem.
Data will be fetched based on the accounts linked to the Consent. If multiple accounts are attached to the consent, data from all of them will be pulled. It is not possible to selectively enable data pull for a subset of accounts linked to a consent.
Currently, the consent request does not allow the FIU to request for consent for a particular bank or account type. Consent can be raised for a particular FIType, not for a particular account type.
OTPs will be sent to the phone numbers used to register with the respective AAs. Some AAs allow for generic OTPs in their sandbox environment. Reach out to the AAs and refer to the individual AA sandboxes for further information.
Refer to this link for the error codes and associated tabs have details on the codes. e.g. If building an FIU you can refer to the AA error codes tab for the response codes.