Reliability and location improvements
Fixed
- More reliable usage reporting during sustained high-volume periods for organizations billed for usage beyond their plan.
- A location’s
websiteno longer contains a Google search, map or redirect link instead of the business’s own site. It isnullwhen the business’s website is unknown, including for previously enriched transactions and location lookups.
Reliability improvements
Fixed
- Fewer temporary
503responses when a transaction is saved during a brief service delay. If such a delay still prevents the save,Retry-Afteron the503response is now 5 seconds instead of 1, so a retry is more likely to succeed. - More consistent response times when processing new transactions.
- Fewer temporary
503responses when saving a transaction during a longer interruption of an internal service. Data you have deleted is still never stored again. - More consistent merchant details for some merchants affected by recent service disruptions. Similar gaps are now repaired automatically.
Better merchant results and data deletion
Fixed
- Restored merchant results for some transactions, including app store purchases and descriptions that shorten or reword a longer business name.
- A transaction’s first response now lists the same intermediaries as later reads of it.
- Large data deletions now continue in the background after the first request. Until a deletion has finished, the request returns
503, so retry the same request to continue it and confirm it’s done. - Fixed a case where a data deletion could report completion too early.
Reliability improvements
Fixed
- Fewer temporary 503 responses during brief service interruptions.
- When all of your concurrent request slots are busy,
Retry-Afteron429responses is now longer, so retries are less likely to run out during short bursts of requests. - Reduced a source of added latency on some enrichment requests.
- Background usage reporting no longer slows down as an account’s usage history grows.
- Data deletion now reports completion only after a final check. Large deletions may return
503once more; retry the same request.
Merchant recognition and reliability improvements
Fixed
- Improved merchant recognition when transaction descriptions contain a website, initials, or additional branch and company details.
- Fewer partial enrichment results during temporary service interruptions.
- Restored merchant results for transaction descriptions that include the merchant’s name with payment prefixes, reference numbers, or a shortened final word.
Accuracy and reliability improvements
Fixed
- Improved reliability and consistency of merchant details.
- Reduced incorrect store locations when an address contains only a postal code and city or conflicts with the street in the transaction.
- Improved location matching for shortened street names when the transaction includes a matching house number and city.
- Improved store-location matching when map details are incomplete.
- Improved merchant matching and category accuracy for previously enriched transactions.
- Improved enrichment reliability during temporary service interruptions.
Paid upgrades and privacy improvements
Fixed
- Strengthened organization isolation for personal details in cached and previously saved transaction results.
- Improved privacy protection for personal details in error diagnostics.
- Improved billing reliability when restoring an organization’s credit state.
- Paid upgrades activate without waiting for previous usage billing, preserve existing credits, and retain the original date for the final old-plan usage invoice.
- Improved paid upgrade reliability across credit renewals, cancellations, and successive plan changes.
- Fixed missing upgrade credits when a previous subscription ends during checkout, and improved completion of pending usage billing after an upgrade.
- Paid upgrades also complete when payment arrives after the previous plan has ended and the account has returned to free.
Changed
- Service maintenance.
Merchant, location, and privacy fixes
Fixed
- Reduced incorrect merchant and store-location matches, including in previously saved results.
- Improved handling of ambiguous addresses and conflicting countries.
- Fixed transaction saving when a merchant has no category.
- Improved transaction-data isolation and deletion, including during concurrent requests.
Changed
- Requests for erased data or inactive organizations return
410without consuming credits.
Merchant, category, and location accuracy
Fixed
- Reduced incorrect merchant matches and third-party branding in results.
- Improved store-location matching and omitted locations without enough supporting detail.
- Recovered missing categories and corrected overstated confidence scores.
- Improved transaction saving during slow connections and cancellation.
Credit and billing accuracy
Fixed
- Corrected monthly allowance timing and preserved separately granted credits during resets and plan changes.
- Prevented interrupted usage reporting from causing duplicate charges or incorrect balances.
- Improved billing accuracy for delayed usage and subscription changes.
Saved transaction accuracy
Fixed
- Fixed transaction saving when reusing previously corrected merchant, location, or payment-service details.
- Preserved corrections that remove an incorrect location.
- Improved merchant matching during concurrent requests and logo retrieval during temporary interruptions.
Category consistency
Fixed
- Corrected categories affected by an earlier transaction’s direction.
- Kept merchant categories consistent with the published category hierarchy.
Changed
- Clarified which transaction ID to use when reporting an enrichment issue.
Security
- Updated supporting dependencies with security fixes.
Platform transaction categories
Added
- Added categories for recognized delivery, grocery, and marketplace platforms, plus the
platform_category_matchconfidence reason.
Fixed
- Improved platform-category accuracy and prevented duplicate signals from overstating confidence.
- Reduced incorrect rate-limit rejections for legitimate API requests.
Merchant categories and accuracy
Added
GET /v1/merchants/{id}now returns primary, secondary, and tertiary categories.
Fixed
- Improved matching and confidence scores for abbreviated merchant names.
- Reduced incorrect locations inferred from numeric store references and recovered missing merchant logos.
Transaction management
Added
- Added
GET /v1/transactions/countwith optionalafterDatefiltering. - Added
DELETE /v1/transactions/batchfor deletion by date range or up to 1,000 transaction IDs. - Added per-organization transaction retention of 1–90 days (
transaction_retention_days).
Changed
- Improved recognition of legal business names in transfer-style descriptions.
Subscription field removal
Breaking
- Removed
data.transaction.subscriptionand its related API and SDK types.
Migration Notes
- Remove subscription-field parsing and validation from your integration. Use
data.transaction.categoryanddata.transaction.confidencefor classification. Dashboard billing subscriptions are unaffected.
Coordinate-based location context
Added
- Added GPS context through
options.location.coordinates, including nearby place-name resolution when no city is supplied.
Changed
- Improved location accuracy for descriptions with little location text. If supplied,
cityNametakes precedence over coordinates.
Fixed
- Prevented country-only location matches and respected
options.filters.noLocation.
Consistent merchant identities
Breaking
- Merchant
entities[].data.idnow identifies the brand rather than an individual store.
Migration Notes
- If you store or join merchant IDs, use the new brand-level ID and update historical mappings by re-enriching transactions. Display-only integrations need no changes.
Added
- Transactions for the same brand now share a merchant ID and brand profile.
Changed
- Improved consistency of merchant names and descriptions across store locations.
Channel field removal and merchant accuracy
Breaking
- Removed
data.transaction.channeland its related API and SDK types. Update integrations that read or validate this field.
Added
- Added the
venue_or_attractionconfidence reason.
Changed
- Improved recognition of abbreviated merchants, venues, attractions, and transport operators.
Fixed
- Reduced third-party websites returned as merchant domains and recovered merchants from URLs in descriptions.
Location cross-checking
Added
- Added location correction and recovery on
POST /v1/transactions/enrich, with confidence reasonsmerchant_location_crosscheck_corrected,merchant_location_crosscheck_recovered,merchant_location_mismatch, andgeo_mismatch.
Changed
- Improved parsing of URL-heavy descriptions and multilingual country names.
Fixed
- Reduced wrong-branch matches and overstated confidence in ambiguous categories.
Enrichment options
Added
- Added optional
optionstoPOST /v1/transactions/enrich. - Skip entity extraction with
options.filters.noMerchant,noIntermediary, ornoLocation. - Supply known merchant details with
options.merchant(id,name, ordomain), location context withoptions.location, or up to five payment services withoptions.intermediaries. - Unknown supplied IDs and combinations of a filter with prefilled data for the same entity return
422.
Fixed
- Improved handling of country suffixes such as
NETFLIX NLand reference-heavy descriptions.
Changed
- Reduced response times when known merchant details are supplied and other entities are skipped.