AML Analyst

MUNDI and Column partner for $150 million financing facility to accelerate growth in Mexico-U.S. Trade finance. MUNDI announced a new financing facility for up to $150 million from Column; its first financing partnership with a trade-finance-focused FinTech in Mexico This partnership [with Column] isn't just about more capital, it's about a fundamentally faster and more flexible way to fund Mexican exporters and their supply chain" - Martin Pustilnick MEXICO CITY, MEXICO CITY, MEXICO, August 20, 2026 /EINPresswire.com/ - MUNDI, the FinTech company powering export growth for Mexican firms and their supply chain, announced the completion of a new financing facility for up to $150 million from Column, a nationally chartered bank that provides regulated financial infrastructure for technology companies; marking Column's first financing partnership with a trade-finance-focused FinTech in Mexico. The facility strengthens MUNDI's funding capacity as it continues to scale its trade finance offering for companies across Mexico, and comes at a moment when Mexican businesspeople face uncertainty around the terms of cross-border trade under the ongoing USMCA review. The new facility adds to MUNDI's existing credit lines and together with other recent debt facility renewals, giving MUNDI the capacity to grow its receivables portfolio to up to $325 million, more than double its previous capacity. Mexican exporters have historically faced limited access to dollar-denominated financing, despite the country's growing role in North American trade: U.S. imports from Mexico reached $534.3 billion in 2025, with momentum continuing into 2026. Micro, small, and medium enterprises (MSMEs) are the backbone of Mexico's economy, yet they produce less than 7% of the country's exports, in part because formal financing remains underused: supplier financing is the most common source for Mexican companies, while financing from foreign-domiciled banks remains marginal. When financing does reach Mexican companies, the impact is significant: 7x more investment, 6x more revenue, 5x more production, and 4x more employment. This is the gap MUNDI was built to close, partnering with Column to accelerate growth in Mexico-U.S. trade finance by providing working capital solutions tailored to the realities of cross-border commerce. "This partnership isn't just about more capital, it's about a fundamentally faster and more flexible way to fund Mexican exporters and their supply chain," said Martin Pustilnick, co-Founder and CEO of MUNDI. "Column's platform lets us draw funding daily, in minutes. At a time when the rules of trade between Mexico and the U.S. are being renegotiated, having the capital and the speed to back our clients isn't a nice-to-have, it's essential. This partnership more than doubles our capacity to grow and gives us room to bring new products to market." "Cross-border trade is essential to the North American economy, and we're proud to put Column's powerful banking infrastructure to work connecting exporters with dollar funding," said Brian Fishbein, Chief Investment Officer at Column. "MUNDI is a champion of Mexican trade. Today's partnership will scale their capacity to quickly deploy reliable capital to Mexican exporters and supply chains, and build economic dynamism across North America." Access to fast, flexible, dollar-denominated financing is becoming a decisive factor for Mexican exporters' ability to compete and grow, particularly as the terms of North American trade are being renegotiated under the USMCA review. For exporters and their supply chains, working capital constraints can mean the difference between capturing new international demand and losing it to better-financed competitors. MUNDI is positioned to keep expanding access to that capital for a growing base of Mexican exporters and their supply chain with this new facility, while also using its added capacity to develop new products in the months ahead. Legal Disclaimer: EIN Presswire provides this news content "as is" without warranty of any kind. Today in New York do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.

Rebuilding Column's documentation. Tyson Rosage Software Designer Column has been busy. Rebuilding its documentation was always toward the bottom of the to-do list, partially because Column were dealing with an annoying (and common) problem: API documentation inevitably drifts from the API itself. A fix would take time and energy, but documentation is a kind of front lawn that signals a lot about how you live and work. So Column made time and came up with a solution: just make the docs and the API the same artifact. Column recently rebuilt its documentation to do just that, with two major changes: * The spec is the source of truth, and... * Its assumed audience is large language models Where Column started. When Column first launched the Column APIs, its product surface area was small enough that the documentation could be basic. Column wanted to ship something simple, so Column put everything on a single scrolling page, which conveniently doubled as a reason to skip building search - Cmd-F could handle anything users needed. That was the right shape for the API at the time. It worked less well as the API kept growing. The spec is the source of truth. That was the surface-level mess. Underneath it was a deeper one: the docs lived in a separate repository and on a separate site, with no real connection to the OpenAPI spec that defines the API. Column were maintaining the source of truth twice - once in the spec its API server already uses to generate types, and again in hand-written markdown in a different codebase entirely. Its fix was to move the docs into the same repo as the spec and write a generator: every build, the spec produces the complete API reference. A new endpoint and its documentation now arrive in the same pull request, get reviewed together, and ship in the same release. The two can't drift apart because they never ship apart. A nice side effect is that depending on the spec improved the spec. Every team thinks they have a singl source of truth until you ask which two repositories it lives in. Search and performance. With the structural problem solved, the rest of the rebuild was about the parts users feel directly - starting with search. The build produces a static index, the CDN serves it, the browser loads it once, and every query after that runs in memory. Everything is searchable now, from API references to written guides. Performance, meanwhile, is a function of shape. The new site is static HTML, one file per page, served from the same S3 and CloudFront Column were using before. Loading one endpoint loads one endpoint, and adding new content costs the new content rather than everyone else. The tradeoff is that build times grow with the corpus - at ten times its current content Column'll need to do builds incrementally, but not yet. Built for the way developers write code now. Those were the obvious upgrades. The bigger change was about who's actually reading the docs - increasingly, that isn't a developer in a browser but a language model the developer is talking to. Column has been on the receiving end of this often enough - wiring up someone else's API through an LLM ranges from genuinely helpful to comically bad. Column wanted ours on the helpful end, so Column made that workflow first-class rather than something developers had to work around. Every page is now published in two formats: the rendered version you see in the browser, and a clean markdown version alongside it with no UI components, no nav chrome, no JavaScript, just the text. A row of buttons on every page hands that markdown off: open in ChatGPT, open in Claude, or copy. The "open in" buttons launch a fresh chat with a prompt pointing the model at the markdown URL, so it reads its actual current content rather than guessing from its training data. In essence, Column'd rather your model read its docs than hallucinate them. Acknowledging that in 2026 feels about as weird as acknowledging mobile in 2012 - slightly awkward in the moment, fairly obvious in retrospect. Navigating an expansive API. Reading docs through a model is one thing. Reading them yourself is a different problem. Against an API with as many objects and parameters as ours, you more often find yourself stuck on finding the right thing to read than trying to decipher what something means. Every API page has a split layout, with parameter definitions on the left and a request/response example on the right. The two are wired together: hovering a parameter highlights the matching lines in the example, clicking one scrolls the example to that line, and clicking a line in the example scrolls back to the parameter's definition. After ten minutes of using it, a flat reference page feels oddly disconnected from itself. The stack, briefly. Fumadocs, Tailwind, one catch-all route. Adding a doc is adding a file. If it's an API reference, the spec generates it for you. Stack sections used to be the part engineers read most closely - these days they're mostly a list to paste into Claude and ask whether it would have picked the same. The result. The new docs keep pace with the API itself, surface what you're looking for, and meet you wherever you read them. If you're trying to understand how Column actually works, docs.column.com should now be the fastest way to get there. Take a look. Tyson Rosage Software Designer