Instant Bank Account Verification

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 (for all countries except few exceptions mentioned below) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx" }' note here, the \<country code> in api endpoint will be "uk", "in" etc please check full table below for supported country codes sample curl (china individual) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/cn' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx", "isbusiness" "false" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/cn' \\ \ header 'authorization your api key' \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx", "isbusiness" "false" }' note for china business bank account verifications, please get in touch with your account manager sample curl (us ) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/us' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx", "isbusiness" "true/false" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/us' \\ \ header 'authorization your api key' \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx", "isbusiness" "true/false" }' sample curl (us method 2 & method 3 ) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \ header 'content type application/json' \\ \ data '{ "accountnumber" "1234567xx", "clearingsystemid" "abc123xxx" }' note here, the \<country code> in api endpoint will be "us v1" for method 2 and "us v2" for method 3 please check full table below for supported country codes sample curl (mexico , argentina & peru) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx" }' note here, the \<country code> in api endpoint will be "mx" for mexico , "ar" for argentina and "pe" for peru please check full table below for supported country codes sample curl (uk iban ) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/gb v1' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/gb v1' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx" }' sample curl (brazil , belgium & italy) pre production curl location 'https //api preproduction signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx",, "creditoridentifier" "abc" }' production curl location 'https //api signzy us/api/v3/global bank verification/validate bank account/\<country code>' \\ \ header 'authorization your api key' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "abc", "accountnumber" "1234567xx",, "creditoridentifier" "abc" }' note here, the \<country code> in api endpoint will be "br" for brazil , "ar" for argentina and "pe" for peru please check full table below for supported country codes request data key value authorization access token (returned as id field of login request) content type application/json request data parameters parameter description validation checks type required fullname full name of bank account holder any non empty string string varies from country to country please see curls above accountnumber account number of bank account alphanumeric string varies from country to country please see curls above clearingsystemid clearing system codes of financial institutions associated with the bank account alphanumeric string varies from country to country please see curls above creditoridentifier uniform credit code (18 char alphanumeric code) as registration id alphanumeric string varies from country to country please see curls above isbusiness flag for business checks yes/no boolean true/false boolean varies from country to country please see curls above coverage & country code url input country county code(at the end of url) united states name ownership check us united state method 2 us v1 united state method 3 us v2 united kingdom uk united kingdom iban method gb v1 india in china cn vietnam vn indonesia id bangladesh bd pakistan pk south korea kr nepal np nigeria ng argentina ar mexico mx uganda ug uruguay uy belgium be italy it brazil br malaysia my peru pe sample response success (200) bank account verified { "result" { "description" "bank account verified", "matchscore" "1", "matchscoredescription" "strong match", "namematched" "all nepal hikking pvt ltd ", "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" "" } } success (200) account flagged, review required { "result" { "description" "account flagged, review required", "matchscore" "", "matchscoredescription" "", "namematched" "", "currency" "" } } success (200) account number format is invalid { "result" { "description" "account number format is 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 key description type result description validation description string result country country associated with bank account string result matchscore degree of matching float result matchscoredescription description reflecting the strength of the match string result namematched name that achieved the match string result currency currency associated with the validated information string country details country creditor (name) creditor account (account number) creditor agent (clearing system id) creditor identification (creditoridentifier match score match score description data remarks united states (us) name( given name and surname) beneficiary bank account id aba code as clearing system id na discrete values representative of strength of match (1, 0, etc ) strong, weak confirms name ownership united states method 2 (us) na beneficiary bank account id us aba code as clearing system id na na return a logic score on the likelihood of whether an account and routing code pair exists; does not perform any name/ownership validation united states method 3 (us) na beneficiary bank account id us aba code as clearing system id na real time microdeposit, returns certainty of account existence, but no ownership/ name check united kingdom (uk) name beneficiary bank account id sort code as clearing system id na discrete values representative of strength of match (1, 0 5, 0) strong, partial, weak supplies full name string in case of partial match only, currency validates only domestic currency (gbp accounts) united kingdom iban (uk) name account number na na discrete values representative of strength of match (1, 0 5, 0) strong, partial, weak supplies full name string in case of partial match only india name beneficiary bank account id ifsc code as clearing system id na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string, currency validates only domestic currency (inr accounts) indonesia name beneficiary bank account id bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string vietnam name beneficiary bank account id bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string, currency validates only domestic currency (vnd accounts) nigeria name nuban as account id bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string nepal name beneficiary bank account id bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string in case of match score > 0 8 only pakistan name beneficiary bank account id or iban bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string, currency validates only domestic currency (pkr accounts) china (individual) name (in chinese characters) beneficiary bank account id (in 62 pan format) na na discrete values representative of strength of match (1, 0) strong, weak n/a south korea name beneficiary bank account id bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string (in hangul), currency validates only domestic currency (krw accounts) bangladesh name beneficiary bank account id bic code (mtblbddh, dhblbddh) na continuous variable, indicating strength of match (0…1) strong, partial, weak supplies full name string, currency argentina name cbu as account id na na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string, currency validates only domestic currency (arl accounts) mexico name clab as account id na na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string, currency validates only domestic currency (mxn accounts); requires repeat request after 5 minutes in case of failures because of source constraints uganda name beneficiary bank account id bic code na continuous variable, indicating strength of match (0 1) strong, partial, weak supplies full name string, currency brazil name iban na cpf in 000 000 000 00 or cnpj in 00 000 000/0000 00 format continuous variable, indicating strength of match (0…1) strong, partial, weak supplies full name string, currency validates only domestic currency (brl accounts) belgium name iban na vat, company no continuous variable, indicating strength of match (0…1) strong, partial, weak supplies full name string in company id match scenarios validates business accounts only italy name iban na vat continuous variable, indicating strength of match (0…1) strong, partial, weak supplies full name string in company id match scenarios validates business accounts only malaysia name beneficiary bank account id bic code na continuous variable, indicating strength of match (0…1) strong, partial, weak supplies full name string, currency peru name cci as account number na na continuous variable, indicating strength of match (0…1) strong, partial, weak supplies full name string, currency uruguay name beneficiary bank account id bic code na discrete (1, 0 5, 0) strong, partial, weak supplies partially masked name string, currency error codes error code description 200 success the request was processed successfully 400 bad request the request was malformed or invalid 409 conflict the request conflicts with the server state 500 internal server error an unexpected error occurred 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!