Ntropy Changelog

Behind the scenes — Updates, Latest News and Improvements
ALL
June 14, 2022
June 14, 2022
Ntropy product update 📝
By
Nare Vardanyan
,
CEO

Happy Tuesday ! Here’s what team Ntropy has been up to the last two weeks:

  • New field: merchant_id - a unique string that identifies each merchant
  • New field: recurrence_group - a list of transaction_ids that are recurrent together
  • 22.6% error reduction in merchant recognition for English transactions
  • Scalability and throughput upgrades for both single transactions and batches. Ask us if you need higher limits on your API key!
  • Reliable merchant confidence scores

We have a bunch of open roles. Software engineers, technical account executives, marketing! If you are someone or if you know someone, please do reach out ! We are excited to talk !

Happy Tuesday ! Here’s what team Ntropy has been up to the last two weeks:

  • New field: merchant_id - a unique string that identifies each merchant
  • New field: recurrence_group - a list of transaction_ids that are recurrent together
  • 22.6% error reduction in merchant recognition for English transactions
  • Scalability and throughput upgrades for both single transactions and batches. Ask us if you need higher limits on your API key!
  • Reliable merchant confidence scores

We have a bunch of open roles. Software engineers, technical account executives, marketing! If you are someone or if you know someone, please do reach out ! We are excited to talk !

May 30, 2022
May 30, 2022
(e)Ntropy and tides. We went surfing 🏄
By
Nare Vardanyan
,
CEO

Everyone has predicted the future and settled in the present. Most of us are downloading Excel and figuring out financial planning.

Meanwhile at Ntropy, business as usual. After all we should thrive in chaos, by design. 😜

If you are focusing on building or maintaining in-house categorization for lending, merchant management, automating tax or accounting, here is why you should not: https://ntropy.com/post/the-false-promise-of-general-transaction-categorization-and-the-inadequacy-of-in-house-models

Fintech Nexus was busy and exciting, while the product team has been head down shipping. The latest updates are below:

Everyone has predicted the future and settled in the present. Most of us are downloading Excel and figuring out financial planning.

Meanwhile at Ntropy, business as usual. After all we should thrive in chaos, by design. 😜

If you are focusing on building or maintaining in-house categorization for lending, merchant management, automating tax or accounting, here is why you should not: https://ntropy.com/post/the-false-promise-of-general-transaction-categorization-and-the-inadequacy-of-in-house-models

Fintech Nexus was busy and exciting, while the product team has been head down shipping. The latest updates are below:

May 16, 2022
May 16, 2022
Ntropy drop: when markets give you lemons 🍋
By
Nare Vardanyan
,
CEO

It's doomsday out there in terms of markets.

We love when our customers fund us and we are working days and nights to deliver the best transaction API experience possible.

If you are thinking of starting to integrate payments data into your workflows, do reach out.

Here's what's been cooking:

  • New version of our Python SDK is out: https://github.com/ntropy-network/ntropy-sdk
  • Ntropy Custom Models are now more robust to noise in the labels. Still have one or two spots for beta customers
  • Significant performance improvements on specific labels on consumer transactions, particularly for “income” and “fees”
  • New labels in the base hierarchy: “child support” (only for consumer transactions), “prenote” for authorizations
  • Confidence scores are now more accurate and available for each API key
  • 11.1% error rate reduction for English transactions
  • 30.4% error reduction on Spanish transactions
  • 13.8% error reduction on Portuguese transactions
  • For merchants without logos or transactions without merchants, we now return beautiful category-specific icons. So you do not have to figure it out yourself
  • General improvements to our developer docs: https://developers.ntropy.com
  • Ntropy is sponsoring PyData London this year. 17-19th June (https://pydata.org/london2022/). We will give a 45-min deepdive on how things work under the hood. Join us!

Last, but not least, if you know amazing marketing and product people, send our way!

It's doomsday out there in terms of markets.

We love when our customers fund us and we are working days and nights to deliver the best transaction API experience possible.

If you are thinking of starting to integrate payments data into your workflows, do reach out.

Here's what's been cooking:

  • New version of our Python SDK is out: https://github.com/ntropy-network/ntropy-sdk
  • Ntropy Custom Models are now more robust to noise in the labels. Still have one or two spots for beta customers
  • Significant performance improvements on specific labels on consumer transactions, particularly for “income” and “fees”
  • New labels in the base hierarchy: “child support” (only for consumer transactions), “prenote” for authorizations
  • Confidence scores are now more accurate and available for each API key
  • 11.1% error rate reduction for English transactions
  • 30.4% error reduction on Spanish transactions
  • 13.8% error reduction on Portuguese transactions
  • For merchants without logos or transactions without merchants, we now return beautiful category-specific icons. So you do not have to figure it out yourself
  • General improvements to our developer docs: https://developers.ntropy.com
  • Ntropy is sponsoring PyData London this year. 17-19th June (https://pydata.org/london2022/). We will give a 45-min deepdive on how things work under the hood. Join us!

Last, but not least, if you know amazing marketing and product people, send our way!

May 3, 2022
May 3, 2022
Custom models, new blog posts, massive error reductions and shiny new docs 💎
By
Nare Vardanyan
,
CEO

Seems like ages in terms of how much we have shipped, but it has only been two weeks!

First and foremost, if you ever debated whether to build something more specialized in-house or to use Ntropy, no more debating needed.

CUSTOM MODELS are here! Whether you're building in-house fraud models, underwriting, adapting to a specific vertical, Custom Models are made for you (literally), and a game changer.

Below are some more details and general updates from the team 🔥:

  1. Custom models now available for consumer transactions
  2. More transactions can now be used to train a custom model (50k, up from 8k)
  3. Recurrence now uses the history of past transactions as additional context. This has a latency cost and can be enabled upon request.
  4. 23% error reduction for merchant detection on English transactions
  5. 30% error reduction for merchant detection on German transactions
  6. 31% error reduction for merchant detection on French transactions
  7. Significant improvement in accuracy for business / personal spend detection (transaction_type field)
  8. Blog on customized transaction modeling (AKA Custom Models) by Jonny Kernes
  9. Blog on how we are using ML pipelines internally by Robin Kahlow
  10. Shiny new docs and dev portal at https://developers.ntropy.com/

Last but not least, for custom models private beta, drop us a line! IF you are in the real-time ACH space or have a use-case for vertical lending, we are already seeing lots of demand there.

Seems like ages in terms of how much we have shipped, but it has only been two weeks!

First and foremost, if you ever debated whether to build something more specialized in-house or to use Ntropy, no more debating needed.

CUSTOM MODELS are here! Whether you're building in-house fraud models, underwriting, adapting to a specific vertical, Custom Models are made for you (literally), and a game changer.

Below are some more details and general updates from the team 🔥:

  1. Custom models now available for consumer transactions
  2. More transactions can now be used to train a custom model (50k, up from 8k)
  3. Recurrence now uses the history of past transactions as additional context. This has a latency cost and can be enabled upon request.
  4. 23% error reduction for merchant detection on English transactions
  5. 30% error reduction for merchant detection on German transactions
  6. 31% error reduction for merchant detection on French transactions
  7. Significant improvement in accuracy for business / personal spend detection (transaction_type field)
  8. Blog on customized transaction modeling (AKA Custom Models) by Jonny Kernes
  9. Blog on how we are using ML pipelines internally by Robin Kahlow
  10. Shiny new docs and dev portal at https://developers.ntropy.com/

Last but not least, for custom models private beta, drop us a line! IF you are in the real-time ACH space or have a use-case for vertical lending, we are already seeing lots of demand there.

April 20, 2022
April 20, 2022
New SDK version with Custom Models, 12 new categories and more 🚀
By
Nare Vardanyan
,
CEO

We are moving and shipping fast. In addition to our regular improvements, we are excited to now return improved location information. And keep an eye out for more content next week...happy updating!

Product Announcements 📣

TXN Updates 📈

  • 12 new categories in our hierarchy
  • Improved coverage for loans, mortgages, rents
  • Improved location data: ability to match transactions to merchant address, where store_ID is present

Improvements 🚀

  • 8.1% error reduction for merchant extraction in english transactions
  • 13% error reduction for consumer transaction categorization

We are moving and shipping fast. In addition to our regular improvements, we are excited to now return improved location information. And keep an eye out for more content next week...happy updating!

Product Announcements 📣

TXN Updates 📈

  • 12 new categories in our hierarchy
  • Improved coverage for loans, mortgages, rents
  • Improved location data: ability to match transactions to merchant address, where store_ID is present

Improvements 🚀

  • 8.1% error reduction for merchant extraction in english transactions
  • 13% error reduction for consumer transaction categorization