Changelog

​

More resilient transaction processing

​

Fixed

• Improved handling of cancelled and stalled transaction lookups.
• Improved diagnostics for temporary credit-check failures.

​

More reliable transaction processing

​

Fixed

• Kept credit checks responsive while background usage is saved.
• Prevented interrupted database transactions from affecting subsequent requests.
• Improved reporting of incomplete results and temporary provider failures.

​

More reliable credit accounting

​

Fixed

• Preserve exact UTC allowance anniversaries and stop stale admissions at allowance boundaries; delayed resets allocate only the current eligible period. Existing-customer adoption requires a separately reviewed period preview.
• Preserved gift and other independently granted credits during monthly resets and subscription plan changes.
• Made credit usage, grant deductions, and balances commit together and recover safely after interrupted flushes.
• Preserved the original allowance for requests completed across a credit reset or plan change.
• Prevented duplicate overage reporting after interrupted billing acknowledgements.
• Kept overage occurrence times and metered billing periods stable across delayed reporting and subscription transitions.
• Made late usage and incomplete invoice reconciliation visible without assuming that accepted usage has been paid.
• Preserved billing evidence for later invoice reconciliation when an organization is deleted.

​

More reliable transaction enrichment

​

Changed

• Improved reporting of unsuccessful requests and recovery.

​

Fixed

• Improved authentication recovery and cleanup after interrupted transaction saving.
• Kept optional merchant matching from delaying transaction results.
• Improved location matching and handling of incomplete results.
• Protected credit reservations during concurrent requests.

​

More reliable recovery and safer diagnostics

​

Fixed

• Preserved ambiguity from incomplete location candidates when query recovery returns fewer results.
• Prevented unexpected database connection errors from interrupting unrelated persistence jobs.
• Preserved the original transaction failure when rollback also fails so persistence retries retain the correct cause.
• Kept credit checks within their existing deadlines through response reading and stopped cancelled requests from continuing into enrichment.
• Stopped cancelled admission requests from waiting behind parallel limit checks or occupying recovery probes.

​

Changed

• Improved privacy and correlation of cache lookup and fallback error reporting while preserving visibility of unsuccessful requests.
• Added privacy-safe export of database resource observations with incident windows, sampling gaps, and access limits.
• Improved diagnostics for temporary admission failures while preserving request limits and credit reservation safeguards.

​

More reliable recovery and accurate reporting

​

Changed

• Improved privacy of database error reports and distinction between recovered operations and unsuccessful requests.

​

Fixed

• Improved transaction saving when an interrupted attempt is still running.
• Stopped cancelled requests from continuing to wait for recipient details to be saved.
• Corrected usage reporting for location recovery requests while preserving customer credit charges and request deadlines.

​

More reliable releases

​

Fixed

• Improved reliability when releasing service updates.

​

Improved location recovery and error reporting

​

Changed

• Improved safe diagnostics for unsuccessful AI attempts and provider recovery while preserving validation and request deadlines.
• Improved recovery of missing location addresses when a single place can be identified.
• Improved error reporting for unsuccessful enrichment requests.
• Reduced duplicate reports of transaction saving failures.

​

Fixed

• Improved logo retrieval when an image source fails or returns an unusable image.
• Prevented temporary error-reporting interruptions from marking recovered logos as failed.

​

More reliable transaction recovery

​

Changed

• Improved diagnostics for slow requests and recovery after temporary connection interruptions.

​

Fixed

• Improved recovery when a temporary connection interruption delays transaction lookups or saving.
• Retried interrupted connections before saving transaction details, while preserving accurate credit charges.

​

More reliable transaction saving and request recovery

​

Changed

• Expanded automated checks for request limits, accurate credit charges, and safe recovery after temporary service interruptions.
• Reduced database work when verifying enrichment details before saving.

​

Fixed

• Fixed failed transaction saving when reusing older reviewed merchant, location, or payment service details.
• Preserved earlier corrections that remove an incorrect location.
• Improved retry guidance when required transaction details are temporarily unavailable.
• Improved merchant matching during simultaneous enrichment requests.
• Improved recovery from temporary logo storage interruptions while protecting reviewed logos.

​

More reliable location and merchant enrichment

​

Fixed

• Reduced malformed AI responses during location matching and merchant verification.
• Improved recovery and diagnostics when AI responses are incomplete.

​

Faster reuse and up-to-date transaction details

​

Fixed

• Reduced waiting time when reusing previously enriched transactions.
• Saved merchant, location, and payment service details more efficiently.
• Kept reviewed corrections and updated merchant details current when reusing earlier results.

​

Faster transaction enrichment

​

Fixed

• Reduced waiting time when reusing previously enriched transactions, merchants, and locations.
• Preserved corrected transaction details when reusing earlier results.

​

More reliable location matching

​

Fixed

• Improved location recovery when search results lack an address or coordinates.
• Prevented incomplete search results from overstating location confidence.
• Fixed invalid location selections attaching coordinates from a different result.

​

Faster transaction retries

​

Fixed

• Reduced waiting time when retrying older enriched transactions while preserving their original results.
• Preserved immediate transaction retrieval and issue reporting after successful enrichment.

​

Faster, reliable transaction saving

​

Fixed

• Fixed failed P2P enrichments when reusing a previously identified payment platform.
• Reduced database waiting time when saving complete enrichment results.
• Preserved immediate transaction retrieval and issue reporting after a successful enrichment.

​

Reliable transaction results

​

Fixed

• Fixed missing or incomplete details when viewing newly enriched transactions.
• Restored creating and viewing enrichment issue reports.
• Improved transaction saving performance.

​

More reliable transaction enrichment

​

Fixed

• Improved recovery from temporary connection failures while preserving daily usage limits.
• Prevented connection retries from consuming daily allowance more than once.
• Reduced authentication delays during temporary service interruptions.
• Improved retry guidance for temporary service interruptions and kept quota errors distinct from service outages.
• Removed internal diagnostic details from public error responses.

​

More reliable store location recovery

​

Fixed

• Fixed premature timeouts that could discard valid store locations during backup maps searches, while preserving time for location validation.

​

Faster recovery from temporary search outages

​

Fixed

• Added alternative web search recovery with bounded waiting times while preserving merchant identity validation.
• Improved store location recovery when the primary places search fails.
• Adapt search capacity across instances when an upstream service reaches its rate limit.

​

More reliable recovery from AI service delays

​

Fixed

• Fixed an issue that could prevent backup AI providers from processing transactions after a service delay.
• Improved failure reporting while preserving partial enrichment results when AI services are unavailable.

​

More reliable merchant and location matching

​

Fixed

• Improved merchant and location matching when external searches respond slowly.
• Added further recovery for merchant lookups during temporary search outages.

​

Faster and more reliable transaction enrichment

​

Fixed

• Reduced lookup delays and improved recovery from temporary connection failures when applying reviewed transaction corrections.
• Fixed premature timeouts that could interrupt transaction enrichment before its allowed time had elapsed.
• Improved lookup speed when matching a provided merchant name, preserving exact matching and duplicate detection.

​

Enrichment reliability improvements

​

Fixed

• General improvements to transaction enrichment accuracy and reliability.

​

More resilient enrichment admission

​

Fixed

• Replenish reserved enrichment allowance before it runs out, reducing request delays and temporary rejections during brief limiter communication failures while preserving the daily ceiling.

​

Database connection recovery

​

Fixed

• Improved recovery from temporary database connection failures during authentication, cached transaction lookup, and entity saving. Authentication remains unavailable when its database checks cannot complete.

​

More reliable transaction reference matching

​

Fixed

• Recognize supported merchant reference formats without repeated title analysis, while preserving meaningful merchant and location text.
• Recognize Amazon Marketplace billing prefixes while preserving the possible seller name.
• Prevent opaque wallet and QR payment references from becoming invented merchants or storefronts, and recover incomplete merchant cache results.

​

More reliable enrichment during service delays

​

Fixed

• Fixed an issue where slow external services could keep transaction enrichment waiting beyond its intended time limit. Requests now recover or return available results more reliably during service delays.

​

More reliable enrichment results

​

Fixed

• Improved consistency of merchant and location details when transactions are enriched again.

​

Search timeout recovery

​

Fixed

• Recover transient web and places search timeouts within the remaining enrichment budget while preserving time for analysis and response processing.

​

Parent redirect reliability

​

Fixed

• Continue parent merchant matching when a cached redirect lookup has no match, and recover malformed redirect cache entries through a database lookup.

​

Parent association reliability

​

Fixed

• Preserve supported merchant identities when parent evidence is stale or conflicting, without repeating database recovery work. Parent creation now validates same-name candidates and waits for the saved merchant identity.

​

Bank lookup performance

​

Fixed

• Reduced database connection overhead for bank searches and profile lookups, with bounded retries for transient failures. Search matching, pagination, and response fields are unchanged.

​

Bank reference data

​

Added

• Search stored bank profiles by name and optional country of origin, or retrieve a bank by ID, at zero credit cost. Profiles support founding information, descriptions, logos, and website details as the catalog is populated.

​

Prefilled entity reliability

​

Fixed

• Reduced connection-related failures when resolving prefilled merchants and intermediaries, with bounded retries inside the existing entity lookup time budget.

​

Rate limiter recovery

​

Fixed

• Improved recovery from transient global rate limiter connection failures and reduced duplicate circuit-breaker alerts while preserving the daily request limit.

​

Transaction cache reliability

​

Fixed

• Restored organization-scoped database cache hits to avoid unnecessary re-enrichment. Cache lookups load transaction and entity data together and exclude deleted transactions.

​

Entity persistence reliability

​

Fixed

• Reduced connection-related failures when saving enriched merchants and locations. Retries retain completed writes, and unfinished entity relationships remain recoverable through durable transaction processing.

​

Reliability and data protection

​

Changed

• Improved the reliability of transaction processing and service updates.
• Strengthened protection of organization-specific transaction and person data.

​

Database performance and maintenance

​

Changed

• Accelerated parent-merchant domain lookups and retention checks and reduced unnecessary database response traffic during enrichment saves.

​

Fixed

• Retention monitoring now retries after a failed check and resumes after cleanup grace periods.

​

Service maintenance

​

Changed

• Removed unused development dependencies and consolidated API development tooling and documentation. API endpoints and response formats are unchanged.

​

Transaction reliability

​

Fixed

• Applied transaction retention policies to delayed recovery data.

​

Transaction reliability

​

Fixed

• Fixed recovery of transactions delayed by extended service interruptions.

​

Transaction reliability

​

Fixed

• Improved reliability when saving enriched transactions during temporary service interruptions.

​

Service maintenance

​

Changed

• Removed the last operational references to the retired logo upgrade service.

​

Service maintenance

​

Changed

• Removed references to the retired external logo upgrade service.

​

Service maintenance

​

Changed

• Maintenance release supporting independent logo portal and local analytics development.

​

Service improvements

​

Changed

• General improvements to service maintenance and reliability.

​

Service improvements

​

Changed

• General improvements to service maintenance and reliability.

​

Dependency security

​

Fixed

• Updated the shared image-processing dependency to include its latest security fixes.

​

Merchant identity integrity

​

Fixed

• Preserved recognized merchant names, websites, logos and identity confidence when a similar parent belongs to a different business.
• Prevented rejected parent associations from returning through cached transactions or merchant reuse.

​

Entity persistence reliability

​

Fixed

• Kept enriched merchant and location details available during brief database connection interruptions.

​

Transaction refresh reliability

​

Fixed

• Improved reliability when refreshing recognized payment processor transactions.

​

Payment processor recognition

​

Fixed

• Made recognized payment processor results consistent when optional profile lookups are slow or unavailable.

​

Payment processor recognition

​

Fixed

• Kept recognized payment processors in enrichment results when optional business-profile details are unavailable.

​

Payment processor recognition

​

Fixed

• Kept production verification aligned with the merchant and payment processor returned for processor-prefixed transactions.

​

Payment processor recognition

​

Added

• Recognized Nyx and SimplePay in transaction descriptions that place the payment processor before the merchant.

​

Fixed

• Kept Tifon and BudapestGO as the merchant while returning the payment processor separately.

​

Enrichment freshness

​

Fixed

• Rechecks reported transactions without reusing earlier transaction, merchant, or descriptor analysis.
• Protects reported-transaction rechecks with additional access controls.

​

Enrichment freshness

​

Fixed

• Rechecks reported transactions when an earlier merchant or category result is incomplete or incorrect.
• Restores corrected categories when an affected transaction is processed again.

​

Release metadata reliability

​

Fixed

• Kept runtime health and API specification version metadata aligned with each deployed release.
• Added release validation to prevent mismatched version metadata from reaching production.

​

Database reliability

​

Fixed

• Improved cache and authentication reliability during brief database connection interruptions.
• Reduced connection setup overhead for enrichment cache lookups.

​

Authentication reliability

​

Fixed

• Kept API authentication available during brief rate-limit coordination interruptions.

​

Wallet and payment processor recognition

​

Added

• Recognized short-form Alipay transaction prefixes (ALP*, ALP-, ALP/, ALP ) used by banks in Southeast Asia, the Middle East, and other regions.
• Extended deterministic title matching to identify Alipay and other wallet-prefixed transactions regardless of country, reducing processing time for these transactions.
• Added support for configuring known short-form wallet abbreviations that receive relaxed matching when they appear at the start of a transaction description.

​

Fixed

• Improved identification of wallet-only QR code payments that contain no merchant name, preventing generic reference numbers from being treated as merchants.
• Corrected display name normalization for Alipay variants (Ali Pay, ALP, ALIPAY) to consistently resolve to the canonical name.
• Prevented wallet abbreviations from being misidentified as merchant names or person-to-person recipients when a wallet intermediary is already detected.

​

Enrichment reliability hotfix

​

Fixed

• Improved delivery of successful enrichment results during brief service congestion.
• Prevented slow coordination checks from consuming the request’s processing window.
• Improved deadline handling for optional entity reuse and fallback categorization.

​

Background processing

​

Changed

• Improved background handling after a successful enrichment.

​

Enrichment freshness

​

Fixed

• Rechecks earlier unresolved merchant and location results when a newer API version retries a low-confidence transaction.
• Continues reusing current and successful entity results to avoid unnecessary processing.

​

Transaction description accuracy

​

Fixed

• Recovered merchant and address details when an address-shaped description previously returned no entities.
• Applied the same safe recovery to earlier cached description analysis results.

​

Transaction description accuracy

​

Fixed

• Improved merchant and location identification for descriptions containing a business name followed by a numbered address.
• Prevented address text from being mistaken for a person-to-person recipient when no transfer or payment-platform signal is present.

​

Enrichment freshness

​

Fixed

• Rechecks older low-confidence transaction results when newer enrichment capabilities may identify the merchant.
• Keeps current and intentionally filtered results cached to avoid unnecessary processing.

​

Merchant identification accuracy

​

Changed

• Improved merchant identification for compact transaction descriptions whose business names are commonly written as separate words.
• Improved local business matching when independent web and location results consistently identify the same company.

​

Fixed

• Preserved valid merchant matches when an official website cannot be established.

​

AI failure diagnostics hotfix

​

Fixed

• Prevented exhausted request deadlines from being reported as missing AI-provider configuration.
• Removed duplicate merchant-enrichment alerts for AI availability failures already reported by the provider layer.
• Preserved actionable error reporting when no AI-provider secret is actually configured.

​

Search reliability

​

Fixed

• Improved enrichment continuity when search services take longer than usual to respond.
• Prevented slow search requests from extending beyond their allotted response window.
• Reduced duplicate recovery traffic during temporary search-service slowdowns.

​

Changed

• Added additional capacity protection for search traffic and improved reliability monitoring.

​

Database and cache reliability hotfix

​

Fixed

• Prevented oversized transaction titles from exceeding Cloudflare KV’s key-size limit.
• Reduced database cache-read round trips and kept optional entity lookups inside their request deadline.
• Gave deferred entity persistence its own background database lifecycle and connection budget.

​

Enrichment deadline reliability

​

Fixed

• Prevented late enrichment retries from exceeding the request’s remaining response budget.
• Improved successful response delivery when entity storage is temporarily slow.
• Reduced the time spent waiting for optional entity-cache lookups during database degradation.

​

Changed

• Improved failure diagnostics for correlating provider activity with affected enrichment requests.

​

Service observability maintenance

​

Changed

• Expanded service monitoring for faster identification of API, enrichment-quality, and upstream-provider regressions.
• Improved provider reliability reporting across successful attempts, timeouts, rate limits, and fallback recovery.

​

Enrichment latency hotfix

​

Fixed

• Prevented optional search recovery from consuming the remaining response budget.
• Improved graceful partial enrichment when search services remain slow.

​

Search recovery hotfix

​

Fixed

• Improved recovery when both active search services time out during the same enrichment request.
• Kept the additional recovery work bounded to protect response latency and service capacity.

​

Search reliability hotfix

​

Fixed

• Improved recovery when preferred search services are simultaneously slow.
• Kept search recovery bounded to protect response latency and service capacity.

​

Changed

• Search requests now use Serper and Autom; Exa is disabled.
• Improved diagnostics to distinguish upstream timeouts from rate limiting and track successful recoveries.

​

Enrichment reliability

​

Fixed

• Improved enrichment continuity when multiple search services respond slowly at the same time.
• Preserved a complete response window for the final search fallback during temporary upstream delays.

​

Changed

• Improved search-fallback diagnostics for faster identification of isolated upstream timeouts.

​

Service reliability

​

Fixed

• Improved continuity when external search services slow down or temporarily limit traffic.
• Improved recovery checks so isolated upstream failures do not interrupt healthy provider traffic.
• Improved processing-provider capacity selection using provider-specific limits.

​

Changed

• Expanded service telemetry for more accurate provider-capacity and reliability reporting.
• Updated supporting dependencies to security-patched releases.

​

Enrichment reliability

​

Fixed

• Prevented routine income enrichment safeguards from being reported as service errors when the final category is valid.

​

Service continuity

​

Fixed

• Improved request recovery during routine service updates and temporary infrastructure moves.

​

Service continuity

​

Fixed

• Improved request continuity during routine service updates.

​

Maintenance reliability

​

Fixed

• Improved cache-cleanup safety checks before account data maintenance begins.
• Avoided unnecessary cache deletion requests when no matching records are present.

​

Categorization consistency

​

Fixed

• Prevented an earlier transaction direction from affecting categories returned for later transactions involving the same merchant.
• Improved automatic recovery when a stored merchant category conflicts with the requested transaction direction.
• Ensured related merchant profiles consistently use the published category hierarchy.
• Clarified which transaction identifier to use when reporting an enrichment issue.
• Updated supporting framework dependencies to security-patched releases.

​

Enrichment reliability hotfix

​

Fixed

• Prevented slow entity lookups from exhausting the enrichment request budget.
• Improved graceful fallback when optional AI analysis or validation retries are temporarily unavailable.

​

Categorization improvements

​

Fixed

• Improved merchant matching for transactions involving delivery platforms and support URLs.
• Ensured returned category hierarchies and names consistently follow the published categorization schema.

​

Reliability improvements

​

Fixed

• Improved API reliability during temporary service interruptions and high-traffic periods.

​

Reliability improvements

​

Fixed

• Improved API reliability and response times during temporary service interruptions and high-traffic periods.

​

API stability improvements

​

Fixed

• Reduced intermittent slow responses when enrichment requires multiple data lookups.
• Improved enrichment response times by more effectively selecting available processing providers.
• Improved enrichment reliability by routing requests away from temporarily degraded providers.

​

Changed

• Improved recovery behavior during temporary database connectivity issues.
• Improved fallback enrichment processing to maintain throughput during high-traffic periods.

​

Enrichment reliability improvements

​

Fixed

• Improved API reliability when external enrichment services are slow or temporarily unavailable.
• Reduced intermittent enrichment timeouts caused by incomplete provider responses.
• Improved recovery from timed-out enrichment work to prevent follow-on request failures.

​

Changed

• Improved graceful recovery during temporary third-party service interruptions.
• Expanded automatic fallback coverage for web searches.

​

Reliability improvements

​

Changed

• Improved internal rate limit monitoring and database connection handling for more reliable API performance during high traffic.

​

Reliability improvements

​

Changed

• Improved internal release validation and provider error monitoring for more reliable API updates.

​

Reliability improvements

​

Changed

• Improved internal monitoring for requests.

​

Reliability improvements

​

Changed

• Improved internal latency to database operations.

​

Reliability improvements

​

Fixed

• Improved enrichment reliability under moderate load by reducing unnecessary AI provider timeouts.
• Improved credit confirmation resilience during deployments, reducing the chance of unconfirmed billing reservations.
• Fixed a connection pool leak that could occur during background parent-merchant resolution.

​

High-traffic reliability and persistence improvements

​

Fixed

• Fixed intermittent enrichment failures and stalled requests that could occur when many organizations sent requests concurrently.
• Improved transaction-history reliability by durably accepting completed enrichments before returning a successful response.
• Improved automatic recovery from temporary database connectivity issues while preventing one request from affecting another request’s processing.

​

Changed

• Failed transaction-history writes now retry automatically with duplicate protection, reducing the risk of missing or repeated activity records during infrastructure disruptions.

​

Reliability maintenance

​

Changed

• Improved internal accuracy of AI with new model configuration.

​

Reliability maintenance

​

Changed

• Improved internal latency to database operations.

​

Reliability maintenance

​

Changed

• Improved internal database read/write performance and reliability.

​

Reliability maintenance

​

Changed

• Improved internal database handling and request recovery for more reliable API processing during temporary service slowdowns.

​

Reliability maintenance

​

Changed

• Improved internal request handling for better reliability during temporary infrastructure slowdowns.

​

Maintenance update

​

Changed

• Improved internal service architecture for faster iteration on enrichment features and reliability improvements.

​

Maintenance update

​

Changed

• Improved internal maintenance tooling for external dependencies.

​

Enrichment reliability improvements

​

Fixed

• Improved enrichment reliability during high traffic and temporary database slowdowns, reducing avoidable timeouts and improving fallback behavior when upstream providers are slow.

​

Enrichment stability and load balancing improvements

​

Fixed

• Fixed intermittent enrichment failures that could occur when multiple requests were processed concurrently within the same service instance, improving reliability under sustained traffic.

​

Changed

• Improved load balancing accuracy for providers that enforce concurrent request limits, reducing unnecessary failovers and improving throughput during high-traffic periods.

​

New AI infrastructure improvements

​

Fixed

• Improved reliability in periods of high traffic for the AI infrastructure.

​

Reliability monitoring improvements

​

Fixed

• Improved internal monitoring for rate limits and enrichment errors, helping the API team spot real reliability issues more quickly while reducing duplicate operational alerts.

​

Maintenance update

​

Changed

• Improved internal maintenance tooling for database-backed checks, helping keep release validation and audits reliable without changing production API behavior.

​

Place detection stability fixes

​

Fixed

• Resolved recurring place detection interruptions during traffic bursts. The place detection service no longer performs heavy warm-up work while serving live requests, removing the timeouts that intermittently disabled place detection for 30-second windows.
• Place detection retries now get a fairer time budget, improving recovery when an initial attempt is slow during scale-out.

​

Enrichment reliability and stability improvements

​

Fixed

• Enrichment requests no longer fail when a cached result is temporarily unavailable; processing continues normally and recovers automatically.
• Improved place detection stability after brief service interruptions, reducing false detection outages.
• Faster switchover to a fallback web search provider when the primary provider is slow, improving enrichment response times.
• Improved resilience to brief database connection interruptions during enrichment lookups.
• Slow cache lookups can no longer delay enrichment responses.

​

Merchant confidence accuracy improvements

​

Added

• Merchant results are now corroborated against the independently found location for the same transaction: when both clearly agree on the same real-world business, merchant confidence reflects that verification instead of staying conservatively low.
• New confidence reason codes (location_corroborated, location_domain_corroborated, location_title_corroborated) explain when and why a merchant was verified by its location result.

​

Changed

• Soft confidence penalties (such as broad or ambiguous merchant names) are lifted when the location result confirms the exact business, improving confidence accuracy for small local merchants.
• Merchant websites surfaced by the location result can now be attached when verified as merchant-owned; booking-platform, directory, and venue-hosted pages are never attached.

​

Enrichment reliability improvements

​

Changed

• Improved enrichment response times when an upstream search provider is slow or degraded.
• Improved provider failover so enrichment can recover more reliably before timing out.
• Added more detailed cache performance monitoring to help keep response times stable.

​

Performance and reliability fixes

​

Fixed

• Improved enrichment response times by restoring the previous stable place detection route.
• Reduced false cache write timeout alerts during periods of higher load.
• Improved reliability for concurrent cached enrichment lookups, reducing unnecessary reprocessing.
• Corrected production environment tagging in error monitoring.
• Reduced duplicate upstream provider rate-limit alerts during provider incidents while still tracking suppressed events.

​

Scaling and high-concurrency reliability improvements

​

Changed

• Improved enrichment capacity coordination across all running instances, allowing higher sustained request rates without upstream provider rate-limit errors.
• Upstream provider backoffs are now shared instantly across all instances, reducing failed enrichment attempts during traffic spikes.
• Request load is now spread across healthy AI capacity proactively instead of all at once after saturation.
• Reduced authentication cache contention during request bursts for the same organization.
• Faster and more reliable internal place detection calls during scale-out

​

Enrichment stability and recognition improvements

​

Changed

• Improved enrichment reliability and throughput during higher traffic periods.
• Reduced false internal service disruptions during transient upstream capacity limits.

​

Merchant domain accuracy improvements

​

Changed

• Improved merchant website matching to reduce cases where third-party listing, directory, map, or profile pages are selected as merchant domains.
• Added more consistent entity reasoning codes and explanations in enrichment responses, including cached and previously saved results.

​

Enrichment stability and recognition improvements

​

Changed

• Improved enrichment reliability and throughput during higher traffic periods.
• Improved handling of slower transaction-title analysis to reduce premature timeouts.

​

Fixed

• Improved recognition of Chinese payment references in transaction titles.

​

Enrichment availability improvements

​

Changed

• Improved enrichment availability when individual processing providers are slow or temporarily limited.
• Improved consistency of enrichment responses during short-lived upstream service issues.

​

Load balancing improvements

​

Fixed

• Internal load balancing improvements to reduce the impact of temporary upstream capacity limits.

​

Merchant accuracy and stability improvements

​

Fixed

• Improved merchant brand matching to reduce rare cases where unrelated businesses could be grouped together.
• Improved enrichment stability during temporary upstream capacity limits.

​

Minor stability improvements

​

Fixed

• Improved enrichment reliability during brief database slowdowns or high-load periods.
• Reduced rare delays when using cached enrichment and entity results.

​

Codebase optimization improvements

​

Changed

• Improved internal maintainability of the enrichment pipeline, cache handling, and internal service routes.

​

Database query timeout improvements

​

Changed

• Improved enrichment response times during temporary database slowdowns.
• Improved enrichment reliability under high traffic by reducing the impact of slow queries on unrelated requests.

​

Enrichment persistence reliability improvements

​

Fixed

• Improved reliability of saved enrichment results during temporary database connectivity issues.
• Improved consistency of cached enrichment results and activity history during short-lived traffic spikes.
• Reduced rare cases where merchant resolution or enrichment follow-up processing could be delayed after a transient persistence failure.

​

Reliability and location resilience improvements

​

Changed

• Improved enrichment reliability when location detection or coordinate-based place resolution is temporarily slow or unavailable.
• Improved transaction dissection and AI-assisted enrichment completion rates for more complex or slower-to-resolve transaction titles.
• Improved request handling during traffic bursts and temporary service slowdowns.

​

Fixed

• Reduced rare enrichment misses caused by transient location lookup failures.
• Reduced occasional request delays or throttling inconsistencies during short-lived high-traffic periods.

​

Enrichment response-time improvements

​

Changed

• Improved enrichment response times, especially for new transactions that require merchant matching.
• Improved consistency when the same transaction is enriched multiple times at once.

​

Fixed

• Reduced rare delays for repeated enrichment requests during high-traffic periods.

​

Enrichment response-time and high-traffic reliability improvements

​

Changed

• Improved response times for transaction enrichment, especially for repeated or concurrent requests with the same transaction details.
• Improved enrichment latency for common Chinese payment titles, including Alipay, WeChat Pay, Tenpay, UnionPay, JD Pay, Huabei, and bank-transfer formats.
• Improved enrichment reliability during high-traffic periods by reducing request-path waiting and cache/database contention.

​

Parent-merchant resolution speed and identity-consistency improvements

​

Changed

• Improved enrichment response speed for transactions where a merchant brand is already known, by resolving parent-merchant identity earlier in the pipeline.
• Improved merchant identity consistency in enrichment responses - parent-merchant name, logo, and category are now only applied when the association has been confirmed, reducing cases where an unverified brand identity could appear in results.

​

Platform-derived category signals and pre-auth rate-limiting refinements

​

Added

• Known platform intermediaries such as Uber Eats, DoorDash, Deliveroo, Wolt, Instacart, Getir, Lazada, and Shopee can now contribute deterministic transaction categories such as Food Delivery, Groceries, and Online Marketplaces.
• Added platform_category_match as a category confidence reason for platform-derived category results.

​

Changed

• Improved category accuracy for delivery, grocery, and marketplace platform transactions so known platform categories can outweigh weaker merchant-derived classifications.
• Refined pre-auth rate limiting so missing or malformed API keys are handled separately from valid-format API key cache misses, reducing false positives for legitimate authenticated traffic while still protecting authentication lookups.

​

Fixed

• Prevented duplicate platform category signals from inflating category weighting when the same intermediary is encountered through both cached and newly enriched data.

​

Upstream lookup reliability improvements

​

Changed

• Improved lookup reliability during upstream rate limits and temporary outages.

​

P2P disambiguation and parent-merchant resolution reliability improvements

​

Changed

• Improved person-versus-merchant disambiguation for transfer-style transactions by adding P2P intermediary context (platform, wallet, and transfer-token signals) to merchant analysis.
• Improved P2P routing so person-detected payees keep intermediary platform context, leading to more complete peer-to-peer enrichment results.
• Improved parent-merchant resolution reliability during enrichment with a more resilient retry path.

​

Fixed

• Prevented merchant-stage P2P placeholders from overwriting valid intermediary-derived P2P recipient data.
• Ensured merchant entities[].data.id remains canonical at the parent-merchant level when a parent profile is temporarily unavailable.
• Fixed parent-merchant redirect lookups to apply consistently for merchants missing a stored parent ID.

​

Merchant category response field and enrichment quality improvements

​

Added

• GET /v1/merchants/{id} now includes the merchant’s category field with primary, secondary, and tertiary classification (same CategoryStructure format as enrichment responses).

​

Changed

• Improved merchant name normalization internally in the enrichment pipeline.
• Improved merchant confidence scoring for single-token acronyms and abbreviations by using fuzzy domain-anchor matching against search results and resolved domains.
• Location enrichment now skips purely numeric store-ID hints because of misclassification of enrichment results.

​

Fixed

• Merchant logos are now more likely to show if existing entity internally has no logo.

​

Enrichment responsiveness and merchant normalization performance improvements

​

Changed

• Faster response times for common enrichment traffic, especially when similar transaction patterns repeat.
• Better responsiveness during high-traffic periods through more efficient capacity checks.
• Faster merchant normalization for clear brand matches, with heavier reconciliation work moved to background processing.

​

Fixed

• Reduced response delays when merchant redirect lookups are slow.
• Reduced repeated work for known unresolved redirect mappings with short-lived miss caching.

​

Intermediary alias detection and location cross-checking reliability improvements

​

Changed

• Improved intermediary detection for short processor aliases in transaction titles, increasing recognition accuracy for delimiter-based formats.
• Improved location cross-checking for store/branch-specific transactions to better validate that selected places match the transaction context.

​

Fixed

• Reduced incorrect location matches for store-ID and branch-hint transactions when geographic validation signals are missing or inconsistent.

​

Enrichment throughput and parent-merchant consolidation performance improvements

​

Changed

• Improved enrichment throughput for concurrent requests, reducing end-to-end latency in high-traffic periods.
• Improved parent-merchant consolidation flow so enrichment results are returned faster while keeping merchant identity consistency.

​

Merchant/intermediary recognition and location extraction reliability improvements

​

Changed

• Improved merchant detection for noisy and reference-heavy transaction titles.
• Improved intermediary and merchant brand recognition using broader keyword and domain matching.
• Improved location extraction reliability when using selective entity filters.

​

Fixed

• Prevented location-only extraction paths from reusing merchant values as location fallbacks.
• Reduced repeated warning noise for invalid AI model overrides in long-running environments.

​

Parent merchant matching and confidence improvements

​

Changed

• Improved parent merchant matching accuracy for brands that appear on shared marketplace/portal domains.
• More reliable merchant confidence scoring for ambiguous payment-style titles and legal-name search results.
• Better consensus handling when search evidence consistently points to a single merchant brand.

​

Fixed

• Reduced incorrect parent-merchant merges for unrelated merchants sharing the same host domain.

​

Transaction lifecycle endpoints and classification improvements

​

Added

• GET /v1/transactions/count endpoint to retrieve the total number of stored transactions, with optional afterDate filter.
• DELETE /v1/transactions/batch endpoint for bulk deletion by date range or list of IDs (max 1000). Associated cache and all internal organization related entries are purged automatically.
• Per-organization transaction retention setting (transaction_retention_days, 1–90 days) to control how long enriched results are cached.

​

Changed

• Improved person vs. merchant classification: legal entity suffixes (LTD, LLC, GmbH, B.V., etc.) now strongly favor merchant classification in both title dissection and merchant analysis.
• Improved P2P detection: transfer phrases followed by business names with legal suffixes are no longer misclassified as person-to-person transfers.
• Improved merchant detection signals: company registries, commercial directories, and invoice/reference patterns now contribute to merchant classification confidence.

​

Legal-name accuracy and IBAN anonymization improvements

​

Changed

• Accuracy improvements for legal names in transaction enrichment POST /v1/transactions/enrich pipeline.
• Improved anonymization: IBANs are now always hidden in internal pipeline processing.

​

Recurring-payment metadata removal from transaction responses

​

Breaking

• Removed the legacy recurring-payment object from enrichment transaction responses.
• Removed recurring-payment enum/type surfaces from the public API contract.

​

Migration Notes

• Action required if your integration reads or validates the legacy recurring-payment object.
• Update response parsing, DTOs, and schema validation to use data.transaction.category and data.transaction.confidence only.
• This change does not affect billing plan flows in the dashboard and Stripe.

​

Changed

• Internal enrichment persistence no longer stores legacy recurring-payment classification fields for transactions and merchants.

​

Coordinate-based location context and resolution improvements

​

Added

• Core API now accepts GPS coordinates in options.location.coordinates as location context for enrichment.
• When coordinates are provided without a city name, the API now resolves them to a nearby place name.

​

Changed

• Location enrichment is now more accurate for transactions where the title has little or no clear location text.
• If both coordinates and cityName are provided, cityName remains the source of truth.

​

Fixed

• Prevented country-level matches from being used as location results when resolving coordinates.
• Ensured coordinate-based location hints are not applied when options.filters.noLocation is enabled.

​

More conservative fallback categorization for IBAN-heavy transfer-like titles

​

Changed

• Fallback categorization is now more conservative for transfer-like titles that contain full IBAN-style account references.
• For IBAN-heavy titles, you may see lower confidence and reference_code in confidence reasons, even if transfer wording is present.

​

Fixed

• Improved reliability of request gating under high-load/throttling scenarios.
• Improved consistency of credit reservation handling when requests are denied by system-wide capacity protections.

​

Canonical brand-level merchant IDs

​

Breaking

• Merchant entities[].data.id now returns the canonical brand-level merchant ID (parent merchant UUID), not a store-level/sub-merchant ID.
• If your integration stores or joins on merchant IDs from previous versions, you should treat this as a new canonical ID space.

​

Migration Notes

• Action required if you persist merchant IDs in your database, analytics model, or downstream joins.
• No action required if you only display merchant name/icon/category in responses.
• Recommended approach:
  • Store the new entities[].data.id as your canonical merchant key.
  • Re-map historical references over time by re-enriching recent transactions or by backfilling your local mappings.

​

Added

• Parent merchant deduplication: location/store variants of the same brand are grouped under one canonical merchant.
• Responses now return a consistent merchant identity (id) and canonical brand profile across transactions for the same brand.

​

Changed

• Merchant names and descriptions are now curated at the brand level when multiple merchant observations exist.
• You may see cleaner brand naming (less branch/store-specific noise) while keeping relevant merchant metadata.

​

Channel removal and merchant-detection improvements

​

Breaking

• Removed data.transaction.channel from enrichment responses.
• Removed channel-related enums and shared types from the public API contract and SDK type surface.

​

Added

• Platform-domain validation for merchant enrichment. Social/content platform domains are no longer assigned as merchant domains unless the merchant is the platform itself.
• URL-based merchant recovery in title dissection when a merchant is missing but a URL is present in the transaction title.
• New venue_or_attraction confidence reason for non-traditional merchants such as venues, attractions, and transport operators.

​

Changed

• Improved merchant confidence scoring for abbreviated and concatenated merchant names.
• Broadened merchant classification so payees that provide goods, services, entry, or transport are more consistently recognized as merchants.
• Improved broad_merchant_name tagging so known brand names are less likely to be marked as broad/generic.
• Improved merchant domain extraction to avoid selecting review sites, app stores, and social media pages as the merchant domain.

​

Merchant-location cross-checking and fallback improvements

​

Added

• Post-enrichment merchant-location cross-checking on POST /v1/transactions/enrich to detect merchant/location mismatches and automatically re-select better location candidates when available.
• Location recovery path for cases where location initially returns no match but a merchant-aligned place exists in search results.
• New location confidence reasons in responses: merchant_location_crosscheck_corrected, merchant_location_crosscheck_recovered, merchant_location_mismatch, and geo_mismatch.

​

Changed

• Improved fallback routing for non-P2P transactions: fallback classification now runs when merchant extraction ends in no match, and income classification runs only when a merchant is confidently found.
• More conservative fallback confidence calibration for ambiguous or reference-heavy titles, with stronger routing to Uncategorized or Other Income in low-confidence cases.
• Improved title dissection for separator-heavy and URL-containing transaction strings.
• Improved country handling with stricter ISO 3166-1 alpha-2 validation and broader country-name/address resolution for multilingual aliases.

​

Fixed

• Reduced wrong-branch location matches for similarly named merchants by cross-validating merchant identity against selected location evidence.
• Fixed cases where weak fallback evidence could inflate confidence or produce over-specific categories.

​

Intermediary alias inference improvements

​

Added

• Alias inference in intermediary post-processing to improve processor/platform recognition from variant names.

​

Changed

• Improved intermediary detection reliability for mixed and abbreviated transaction strings.

​

Merchant disambiguation and fallback confidence updates

​

Added

• Expanded merchant analysis signals with country-aware disambiguation and legal-entity marker handling.
• Expanded fallback confidence reason handling for ambiguous and reference-like titles.

​

Changed

• Improved title normalization for merchant analysis and fallback categorization.
• Improved fallback confidence scoring to better reflect uncertainty.

​

Fixed

• Negative fallback reason tags now take precedence over positive tags during confidence calibration.

​

Enrichment cache performance and observability updates

​

Changed

• Faster enrichment retrieval path with cache transaction lookups.
• Improved entity-cache lookup/save performance for lower enrichment latency.
• Added more granular cache phase tracking for enrichment observability.

​

New options field for enrichment endpoint

​

Added

• Enrichment options on POST /v1/transactions/enrich: new optional options field in the request body.
  • Filters (options.filters): set noMerchant, noIntermediary, or noLocation to true to skip extraction of that entity type. Useful when you already have the data or want faster responses.
  • Pre-filled merchant (options.merchant): supply id, name, or domain when you know the merchant. The API will use it directly instead of extracting from the title. IDs must exist in our system (returns 422 if not found); names and domains use best-effort lookup.
  • Pre-filled location (options.location): supply cityName, streetName, storeNumber, physicalLocation, or coordinates to improve location accuracy.
  • Pre-filled intermediaries (options.intermediaries): supply up to 5 intermediaries by id, name, or domain when you know the payment processor(s).
  • You cannot combine a filter (e.g. noMerchant) with pre-filled data for the same entity type; the request will return 422.

​

Changed

• Improved extraction accuracy for transaction titles that include country codes (e.g. NETFLIX NL).
• Improved handling of reference-like patterns (payment IDs, order numbers).
• When you pre-fill merchant and skip intermediary + location, the API may bypass title dissection for lower latency.

​

Fixed

• Titles ending in a country code (e.g. NETFLIX NL) are now parsed correctly instead of being treated as merchant-only.

​

Incremental accuracy and performance improvements

​

Changed

• Incremental accuracy and performance improvements across the enrichment pipeline.
• Improved entity detection for noisy transaction strings, reducing merchant false negatives.
• Faster cold-start behavior on POST /v1/transactions/enrich.
• Tuned confidence reason-tagging to make confidence scores more reliable, especially for merchant and location entities.
• Additional latency improvements in enrichment processing.