Know Your Customer
...
Asia Pacific
Indonesia Tax Id check
overview and purpose overview the indonesia npwp check api is a specialized digital tool designed for businesses and individuals operating within indonesia this api provides essential support by verifying and fetching detailed information associated with an npwp number from official indonesian records, enhancing trust, accuracy, and compliance across various sectors key features and functionalities information retrieval takes an npwp number as input and retrieves comprehensive details such as the name and address of the individual or organization associated with that npwp enhanced data accuracy ensures that businesses have access to accurate and reliable data, essential for processes like account creation, financial transactions, and access to services business trust for sectors such as banking, finance, and telecommunications, where detailed customer information is critical, this api builds a foundation of trust by ensuring that all retrieved information is accurate and reliable compliance support helps businesses meet stringent regulatory requirements by providing reliable information retrieval services that comply with indonesian laws and guidelines this is particularly crucial in industries like finance and healthcare, where precise information is mandatory the indonesia npwp check api is vital for securing and streamlining customer onboarding and transactions, reinforcing compliance and trust for businesses in indonesia api details api overview the check api enables the retrieval of detailed information based on an npwp number, including the name and address of the individual or organization each input is cross referenced against authorized sources to ensure the accuracy and reliability of the retrieved data authorization access to this api is granted via an authorization token, ensuring secure and authenticated access for authorized users sample curl preproduction curl location 'https //api preproduction signzy app/api/v3/global kyc fetch/id/npwp' \\ \ header 'authorization \<auth token>' \\ \ header 'content type application/json' \\ \ data '{ "npwp" "081853269215000" }' production curl location 'https //api signzy app/api/v3/global kyc fetch/id/npwp' \\ \ header 'authorization \<auth token>' \\ \ header 'content type application/json' \\ \ data '{ "npwp" "081853269215000" }' api input request body { "npwp" "081853269215000" } request body parameters true false 0,0,307false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type response sample response success 200 { "result" { "npwp" "081853269215000", "name" "r b rt b rr t m n l p l p ssy", "address" "pt t c nd n s ,l t 108 110 b p , m k k n ng" "statuswp" "aktif", "statusspt" "invalid" } } response body parameters true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type error code and response mapping 400 (bad request) { "error" { "name" "error", "message" "bad input and description ", "status" 400, "reason" "validation error", "type" "bad request", "statuscode" 400 } } 401(unauthorized) { "error" { "name" "error", "message" "invalid authentication credentials", "status" 401, "reason" "authentication error", "type" "bad request", "statuscode" 401 } } 403 (forbidden) { "error" { "name" "error", "message" "forbidden", "reason" "error", "type" "bad request", "statuscode" "403" } } 500 (internal server error) { "error" { "name" "error", "message" "internal server error", "status" 500, "reason" "error", "type" "bad request", "statuscode" 500 } } 409(upstream down { "error" { "name" "error", "message" "upstream down", "status" 409, "reason" "error", "type" "bad request", "statuscode" 409 } } true falsefalse left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type 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 help\@signzy com 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!