We went through a painful process of trying to get the IRS to integrate into the Cipheredtrust API, without success of course. In the end we had to settle for a browser extension which requires us to hold tax information (only in computer memory for a given session). We hope that eventually we'll be able to convince the IRS to do the integration for the good of every taxpayer who needs it.
Recently the FAFSA tool (called the IRS Data Retrieval tool) which students rely on to pull data directly from the IRS into their application was shutdown due to security concerns.
The case we made to the IRS for supporting this integration specifically made reference to the integration of the IRS data-source into the Department of Education application as an example of how making it easy and secure for people to leverage their tax information can deliver great value.
The benefit of the data retrieval tool is two fold, first it is convenient for students since it automates the completion of parts of what is a complicated application. Secondly, the tool eliminates the need for financial aid offices to engage in the manual process of verifying information since it comes directly from the authoritative source (ie the horse's mouth). This is precisely what our API/Protocol facilitates at scale while robustly addressing security and privacy concerns.
Using a federated API like ours, the IRS would eliminate the need to have an adhoc authentication solution for the FAFSA (or any other specific client), rather all clients get a single interface from which to easily get the information while meeting all security, trust and privacy requirements.
With our API the IRS doesn't need to make provision for a separate data retrieval tool, a taxpayer simply accesses the Get Transcript ONLINE service leveraging the security of that service and then selecting the information they wish to share with some third-party (no need for IRS to know who that is) . The IRS could even leverage something like JSON Web Signatures to ensure the recipient can trust the information.
If anyone at the IRS or DOE wishes to work with us, give us a ping!
Recently the FAFSA tool (called the IRS Data Retrieval tool) which students rely on to pull data directly from the IRS into their application was shutdown due to security concerns.
The case we made to the IRS for supporting this integration specifically made reference to the integration of the IRS data-source into the Department of Education application as an example of how making it easy and secure for people to leverage their tax information can deliver great value.
The benefit of the data retrieval tool is two fold, first it is convenient for students since it automates the completion of parts of what is a complicated application. Secondly, the tool eliminates the need for financial aid offices to engage in the manual process of verifying information since it comes directly from the authoritative source (ie the horse's mouth). This is precisely what our API/Protocol facilitates at scale while robustly addressing security and privacy concerns.
Using a federated API like ours, the IRS would eliminate the need to have an adhoc authentication solution for the FAFSA (or any other specific client), rather all clients get a single interface from which to easily get the information while meeting all security, trust and privacy requirements.
With our API the IRS doesn't need to make provision for a separate data retrieval tool, a taxpayer simply accesses the Get Transcript ONLINE service leveraging the security of that service and then selecting the information they wish to share with some third-party (no need for IRS to know who that is) . The IRS could even leverage something like JSON Web Signatures to ensure the recipient can trust the information.
If anyone at the IRS or DOE wishes to work with us, give us a ping!
Your post is really impressive and it has lots of knowledge in learning. Keep share your valuable knowledge with us.
ReplyDeleteIRS tax controversy audits and resolution