End user working with Insynch to implement a web integration. They are for some unreason struggling with validating zip codes as entered on the web.
As a workaround they've implemented a method where an unknown zip code is populated as 99999.
This appears to work ok but they are integrated with payments and at some point in this process it looks like payments has taken in the zip code (the temporary 99999) and when they try to change it :
The error trap works and when a zip code does not exist in Sage 100 it populates the zip field with 99999.
Easy to edit zip code in Bill to, Ship to, and the AVS. Authorizes CC fine, but we get an error in Sage 100 that prevents us from printing the order.
Unable to write document. Payment and Deposit records have different credit card information.