Server and installation requirements

The following table lists the implementation and performance requirements that your integration must meet to ensure efficient operation and proper error handling.


Requirement	Use Case	Endpoint(s)/Model(s)	Required/Conditional/Suggested
Reasonable errors on server-side analysis	Users must ensure that the implementation does not include messages (errors, warnings, etc.) except those that would result from normal (but invalid) user input (for example, invalid PCode data). In addition, these messages must be logged/displayed appropriately in the application.	N/A	Required
Reasonable ratio of transaction calls to committed documents	Users must ensure that the integration minimizes traffic. AFC will expect to see up to approximately 10 calculations per finalized document (including for abandoned carts). Failing to do so will drive up usage and billing. Note that you can also provide a simple "estimated tax" option, just ensure that the estimate doesn’t call to AFC.	N/A	Required
Demonstrate and document installation of software	If there’s something to install on the source application, then you must demonstrate and document that process.	N/A	Required