> For the complete documentation index, see [llms.txt](https://verify-doc.tiller-verify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verify-doc.tiller-verify.com/country-coverage-match-rates.md). # Country Coverage Match Rates In our address verification process, we use multiple service providers to check client address information across various countries. Each provider has a unique success rate based on the quality and availability of data sources within a specific country. Due to these differences, match rates can vary between countries and providers.
We categorise the anticipated match rate into the following bands: **+60% Anticipated match rate** {% hint style="info" %} **+60% (High Match Rate):** Countries where address verification sources are highly reliable and have comprehensive coverage. {% endhint %} **>40% Anticipated match rate** {% hint style="info" %} **40% - 60% (Moderate Match Rate):** Countries with fairly good coverage but may have some limitations. {% endhint %} **<40% Anticipated match rate** {% hint style="info" %} **<40% (Low Match Rate):** Countries with limited data sources or lower verification accuracy. {% endhint %} **\*** *Subject to conditions* Please see below for the match rates per continent.
Africa | Country | Country code | Expected address match rate | | ----------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Ghana**\*** | GHA | | | Kenya**\*** | KEN | | | Nigeria**\*** | NGA | | | South Africa**\*** | ZAF | |
Asia & Pacific | Country | Country code | Expected address match rate | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Armenia**\*** | ARM | | | Australia | AUS | | | China | CHN | | | Hong Kong | HKG | | | India**\*** | IND | | | Indonesia**\*** | IDN | | | Japan**\*** | JPN | | | Malaysia**\*** | MYS | | | New Zealand | NZL | | | Philippines**\*** | PHL | | | Saudi Arabia**\*** | SAU | | | Singapore | SGP | | | Thailand**\*** | THA | | | Vietnam**\*** | VNM | |
Europe
Country Country codeExpected address match rate
Austria*AUT
Belgium*BEL
Czech Republic*CZE
Denmark*DNK
Finland*FIN
FranceFRA
GermanyDEU
Gibraltar*GIB
Greece*GRC
GuernseyGGY
Hungary*HUN
Ireland*IRL
Isle of ManIMN
ItalyITA
JerseyJEY
Luxembourg*LUX
Malta*MLT
Netherlands*NLD
NorwayNOR
Poland*POL
Portugal*PRT
Romania*ROU
Slovakia*SVK
Spain*ESP
SwedenSWE
SwitzerlandCHE
Turkey*TUR
United KingdomGBR
North & South/Latin America | Country | Country code | Expected address match rate | | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Argentina**\*** | ARG | | | Brazil**\*** | BRA | | | Canada | CAN | | | Chile**\*** | CHL | | | Colombia**\*** | COL | | | Mexico**\*** | MEX | | | United States | USA | |
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://verify-doc.tiller-verify.com/country-coverage-match-rates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.