US TIN Verification

overview a taxpayer identification number (tin) is a unique identification number used by the internal revenue service (irs) in the administration of tax laws while there are various types of tins, all businesses will have some form of tin, which will act as a unique identifier of a business entity the list of tin types are the following social security number (ssn) employer identification number (ein) individual taxpayer identification number (itin) taxpayer identification number for pending u s adoptions (atin) preparer taxpayer identification number (ptin) all valid business entities will have an ein issued by the irs the federal government requires a legal entity to have an ein to pay employees and to file business tax returns to be considered a partnership, llc, corporation, s corporation, non profit, etc , a business must obtain an ein when incorporating eins do not expire once an ein has been issued to an entity, it will not be reissued as such, each ein is unique to a business and persists over time how does signzy help in verifying tin? verifying the tin of a business is a crucial part of business verification signzy will ascertain if a tin is valid or not and that it matches the name passed to the api against irs database use cases tax filing and reporting tins are required on all tax documents they are used to track an individual's or business's tax obligations and ensure proper tax compliance opening a bank account banks and financial institutions often require a tin to open a bank account, particularly for business accounts employment employers use an individual’s ssn to report earnings to the irs and state taxing authorities credit applications tins are used when applying for credit credit bureaus use it to identify an individual’s credit records accurately government benefits ssns are required to apply for government services and benefits, such as unemployment benefits or social security benefits api details request body pre production curl location 'https //api preproduction signzy us/api/v3/us kyb/tin verify' \\ \ header 'accept application/json' \\ \ header 'content type application/json' \\ \ header 'authorization < auth token >' \\ \ data '{ "name" "yahoo inc", "tin" "770434749" }' production curl location 'https //api signzy us/api/v3/us kyb/tin verify' \\ \ header 'accept application/json' \\ \ header 'content type application/json' \\ \ header 'authorization < auth token >' \\ \ data '{ "name" "yahoo inc", "tin" "770434749" }' request body parameters field type description required name string the name of the business to verify special characters are not allowed into the business name field yes tin string the taxpayer identification number yes response body successful response { "result" { "responsecode" "3", "responsemessage" "tin was missing or tin not 9 digit numeric ", "responsedesc" "valid return code " } } response body parameters field type description responsecode string contains code explaining what kind of match is received from irs responsemessage string contains message explaining the response code 0 tin and name combination matches our records 1 tin was missing or tin not 9 digit numeric 2 tin entered is not currently issued as per irs records 3 tin and name combination does not match irs records 4 invalid tin matching request 5 duplicate tin matching request 6 tin and name combination matches irs ssn records 7 tin and name combination matches irs ein records 8 tin and name combination matches both irs ssn and ein records 10 tin and name combination not found in our records 90 99 connection/query/miscellaneous error responsedesc string contains basic description of whether valid response or not e rror code response & mapping 400(bad request) { "error" { "name" "error", "message" "name is required", "status" 400, "reason" "validation error", "type" "bad request", "statuscode" "400" } } 401(unauthorized) { "message" "invalid authentication credentials" } 403(forbidden { "error" { "name" "error", "message" "forbidden", "reason" "error", "type" "bad request", "statuscode" "403" } } 409(upstream down error) { "error" { "name" "error", "message" "upstream down", "status" 409, "reason" "error", "type" "conflict", "statuscode" "409" } } 500(internal server error) { "error" { "name" "error", "message" "internal server error", "status" 500, "reason" "error", "type" "bad request", "statuscode" "500" } } field type description name string text displayed on the screen explaining error type reason string reason for the error status number http status code message string error message indicating an upstream error type string error type statuscode string status code representing the error scenario getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at we strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively we value your feedback and are committed to making your experience smooth and enjoyable our team is dedicated to assisting you with any needs you may have thank you for choosing our services we look forward to helping you!