Instant Bank Account Verification - China Individual

introduction our instant bank account verification flow is designed to provide secure and efficient account verification services across various countries, including the united kingdom, india, united states, indonesia, vietnam, nigeria, nepal, pakistan, china, korea, and bangladesh etc this process allows businesses and financial institutions to verify bank account details instantly, streamlining the onboarding process and enhancing the overall user experience use cases cross border transactions facilitate cross border transactions by quickly and accurately verifying bank account details, enabling secure and efficient international money transfers enhanced onboarding process streamline the customer onboarding journey by automating the bank account verification process, reducing manual efforts, and minimizing the risk of errors risk mitigation minimize the risk of fraudulent activities by validating bank account details through a robust and reliable verification process, providing an additional layer of security currency confirmation obtain information on the currency associated with the provided bank account, allowing businesses to ensure compatibility and accuracy in financial transactions bank account validation flow api description sample curl pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/cn' \\ \ header 'authorization < auth token >' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abcd company", "accountnumber" "32187216345", "clearingsystemid" "abocc342", "isbusiness" "true", "creditoridentifier" "91111111abhy734" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/cn' \\ \ header 'authorization < auth token >' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abcd company", "accountnumber" "32187216345", "clearingsystemid" "abocc342", "isbusiness" "true", "creditoridentifier" "91111111abhy734" }' request data parameters(for individuals) true false 149,209,129false 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 true unhandled content type true unhandled content type true unhandled content type true unhandled content type true 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 note very big names can cause errors try removing last few words in case of better results we are working to upgrade this in coming months reachout to us if you face any difficulties clearing system id only accepts first 8 digits of swift code we are in the process of implementing logic to accept the 11 digits in the coming months sample response success (200) bank account verified { "result" { "description" "bank account verified", "matchscore" "0 99", "matchscoredescription" "strong match", "namematched" "北京苹果和橙子公司", "currency" "" } } success (200) account number not found { "result" { "description" "account number not found", "matchscore" "", "matchscoredescription" "", "namematched" "", "currency" "" } } success (200) unable to validate account number { "result" { "description" "unable to validate account number", "matchscore" "", "matchscoredescription" "", "namematched" "", "currency" "" } } success (200) clearing system id invalid { "result" { "description" "clearing system id invalid", "matchscore" "", "matchscoredescription" "", "namematched" "", "currency" "" } } bad request (400) { "error" { "name" "error", "message" "bad request", "status" 400, "reason" "fullname required", "type" "bad request", "statuscode" "400" } } upstream down (409) { "error" { "name" "error", "message" "upstream error", "reason" "error", "type" "conflict", "statuscode" "409" } } success response body parameters true false 259false 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 false unhandled content type false unhandled content type false unhandled content type error codes 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 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!