Payments
Target merchants by currency, market and cross-border complexity
For Payment providers, FX platforms and merchant acquirers
The problem
Merchant acquisition is a volume game with a targeting problem. The merchants worth winning are the ones with cross-border complexity: multiple currencies, international shipping, a mismatch between where they are and what they charge in.
How the data solves it
Filter on currency and country together. A shop based in one country but charging in another currency, shipping internationally, is carrying FX and settlement friction right now. There is no single mismatch flag: you build it by selecting a country and then excluding that country's own currency, which is two filters rather than one and gives you the same list.
The filter set this maps to
Every field below exists in the shop schema. This is the query, not an illustration.
- Country
- Germany, France, Netherlands
- Currency
- not EUR
- Ships International
- yes
- Is multilingual
- yes
- Products
- > 100
Build it
Four steps to this list
Every column named here exists in the schema, and the request below runs as written.
- 1Set currency_cc_match to no — the currency charged does not match the country of operation.
- 2Add ships_intl = yes to confirm genuine cross-border trade.
- 3Add is_multilingual = yes as a proxy for real international selling, not an accident of configuration.
- 4Export currency and country to size the FX exposure before you call.
The same query through the API
POST this to /api/v1/search for a count, or /api/v1/rows for the shops themselves.
{
"filters": [
{
"kind": "dropdown",
"col": "currency_cc_match",
"values": [
"no"
]
},
{
"kind": "dropdown",
"col": "ships_intl",
"values": [
"yes"
]
},
{
"kind": "dropdown",
"col": "is_multilingual",
"values": [
"yes"
]
}
]
}Playbook
What to do once you have the list
A list is not a campaign. These are the three things that decide whether it converts.
The mismatch IS the pitch
A shop operating in one country and charging in another is paying FX spread and carrying settlement delay right now. You do not have to create the pain.
Size before you call
currency and country together tell you the corridor. A EUR-charging US shop is a different conversation from a GBP-charging Australian one.
Multilingual is the qualifier
Cross-border shops that translated their storefront have committed to the market. They are the ones who will care about local payment methods.
Outcome
What you end up with
Merchants with demonstrable cross-border exposure
Currency and market data to size the opportunity before contact
Multilingual storefronts as a proxy for genuine international sales
Questions
Payments: frequently asked
How do I find shops charging in a currency other than their own country's?
Select the countries you care about, then exclude the currency those countries normally use. Country and currency are separate fields and both are filterable, so a German shop pricing in USD comes back from a two-filter query. There is no single mismatch flag to tick, and a shop charging in a foreign currency while shipping internationally is usually carrying real FX and settlement cost.
Can I find merchants selling into a specific market?
Yes, by combining country, currency, language and international shipping reach to describe the market a merchant actually sells into rather than where they are registered.
Which fields actually indicate cross-border complexity?
Currency, country, international shipping, destination country count and multilingual status. A shop in one country, charging in another currency, shipping to twenty more, running two languages, is carrying FX conversion, settlement delay and tax complexity right now. Each of those is a separate filter you combine.
Can I see which payment provider a shop uses?
Not reliably, and it would be wrong to imply otherwise. Checkout providers are usually loaded inside the checkout flow rather than the storefront, so they are not consistently detectable from a public page. What you can see is the other technology and tracking pixels on the storefront, which sometimes indicates the wider stack.
How do I find merchants selling into a market before they have localised for it?
Filter for shops shipping to a country while not carrying its language. International shipping with a high destination count, combined with a single primary language, is a merchant selling into markets they have not localised for. That is a conversation about local payment methods rather than about rates.
Start finding better e-commerce leads today
Free trial with the full dataset and every filter, and the allowance resets daily rather than expiring.