Merchant matching is not enabled by default. To request access, please contact us at .
/merchants/ match
POST
endpoint to submit a real-time merchant match.
Tip: Latitude & longitude are the strongest disambiguators after name + address. Use them when you have them.
Field | Description |
---|---|
id | Spade Counterparty ID |
name | Canonical business name. |
similarity | 0–100 match confidence. |
Field | Description |
---|---|
id | Spade Location ID |
name | Location‑level business name (if distinct from brand). |
address | Cleansed, correctly cased postal address. |
city | Cleaned city corresponding to the Location |
similarity | Confidence that this physical location is the one you provided. |
Similarity vs. Match Score? For merchant matching we use similarity (string & geo distance based). Card enrichment uses matchScore (ML model across many signals). Treat them the same way: higher = better.
counterparty
or location
means we couldn’t find an acceptable match. Typical reasons:
POST /batches/merchants/match
. Learn more in our batch merchant matching guide.
application/json
. Some HTTP tools fallback to multipart/form-data
; override it explicitly.Done? | Recommendation |
---|---|
Send full street address and city/region/postalCode. | |
Provide latitude/longitude when available (mobile checkouts, GPS capture). | |
Store counterparty.id and location.id once → attach to every transaction. | |
Decide on a similarity threshold (e.g., drop matches <70 ). | |
Use batch matching for historical backfills and weekly sync jobs. |