Liquido put the checkout in the chat

The revealing detail was the cash. Working on Latin American expansion at Uber and DiDi, Shanxiang Qi noticed how often passengers paid for rides with physical money. These were people using a sophisticated app to summon a car, then reaching for notes to finish the transaction. The phone had solved finding a driver. Paying remained a separate negotiation. Liquido, the company Qi started with MengKe “MK” Li, grew out of that awkward gap between what software could arrange and what customers could actually pay for.

01 A ride, a wallet, a mismatch

The founders brought different experience to the same problem. Qi had worked on payments and growth at DiDi. Li had worked at Google and Microsoft before becoming an investor. They started Liquido in early 2021, building for Latin America from a company headquartered in California. The geographic arrangement was unusual; the commercial question was straightforward. How could a merchant accept the way a customer preferred to pay without stitching together a different system for every option?

“I was struck by the prevalence of cash payments for rides.”

SHANXIANG QI · CO-FOUNDER · 2023

That observation matters because it changes the diagnosis. A person paying cash through an app has already crossed the supposed digital divide. The obstacle sits later in the journey. A checkout designed around a card can make a willing buyer look like an uninterested one.

02 One connection, local money

Liquido’s core product connects businesses to payment methods through an API. The details are less tidy than the phrase “Latin American payments” suggests. Its documentation lists Pix and boleto in Brazil, bank transfers and cash in Mexico, and PSE and Nequi in Colombia. The countries share a region, but their payment menus differ. The engineering job is to absorb those differences so merchants can offer locally useful choices.

Money also needs to travel in the opposite direction. Liquido supports payouts, including bank-transfer workflows for suppliers and payroll. This places it between merchants and financial infrastructure: a business service whose work is mostly invisible to the shopper. E-commerce companies, marketplaces and digital platforms are natural customers. Finsiders named the video platform Kwai as an early client.

03 The shop moves into the conversation

A payment connection still leaves a merchant with another problem: getting a customer through the purchase. Liquido introduced its Payment Plus Platform at its May 2023 public launch. Its first offering was a storefront inside WhatsApp, where shoppers could browse a catalog and buy. Merchants could set it up without writing code. The product stretched the company’s remit from accepting money to helping a sale happen.

The interesting response came from an early user. Rather than treating the WhatsApp store as an extra destination, the merchant sent Facebook and Instagram advertising directly into it. That connected customer acquisition with the shopping conversation. Pilot behavior helped inform the product’s direction. The practical lesson is appealingly small: watch where customers send your product before deciding where it belongs.

Shopify and Magento integrations also connected Liquido to existing merchant systems. A store owner need not share a payment engineer’s enthusiasm for APIs. A useful integration meets the owner inside the tools already running the business.

04 Give the unfinished payment another turn

Payment recovery addresses the sale that stalls. Liquido’s WhatsApp offering pairs messages with payment links and multiple payment choices. Its published approach includes testing alternative messages for conversion. The premise is that an unfinished purchase may need a better route back, rather than another advertising campaign. Recovery becomes part of payment operations.

For a merchant, the sequence changes what to investigate. An abandoned cart is an outcome, not an explanation. Did the customer lack the offered payment method? Did the payment fail? Or did the conversation simply stop? Liquido groups those problems near the checkout, giving operators several places to intervene rather than treating every departure as the same event.

Risk makes that proposition harder. Liquido’s developer documentation accepts context such as device identifiers, purchasing history and order details. These inputs help evaluate a payment beyond its amount. The product challenge is a balancing act: let legitimate customers through while catching suspicious activity. A more permissive checkout can look successful until fraud losses arrive. More approvals alone cannot settle the question.

05 The permission behind the product

The first documented constraint was institutional. Before obtaining its Brazilian payment institution license, Liquido concentrated on basic payment connectivity. In November 2023, the company announced that authorization, opening room for a broader range of services. A new interface cannot substitute for permission to operate. The license belonged in the product story as much as the WhatsApp catalog did.

Building the business required outside capital, too. Launch-era reporting put its early funding at $26 million across two rounds, with Index Ventures among the backers. By November, Liquido said cumulative payments processed had passed $1.5 billion. Those figures describe different things: investment financed the company; processing volume measured money passing through its infrastructure.

06 A bigger owner, the same local question

Liquido became part of Shift4 in 2025. Acquisition coverage appeared in February; Brazilian reporting described regulatory authorization involving the local unit in July. The sequence illustrates another feature of this market: a company sale and a local permission can run on different clocks.

Its alternatives include regional specialists such as EBANX and dLocal, alongside broader platforms such as Stripe. A buyer evaluating these services still has to examine the countries served, the methods supported and the settlement arrangements. Those practical differences determine whether the integration solves an actual operating problem. The appeal of fewer connections has to survive contact with the merchant’s particular market. One API is therefore a starting point for comparison. Liquido’s more distinctive proposition connects local payment access with commerce and recovery inside WhatsApp.

The copyable idea is to study the entire unfinished purchase. Identify the missing payment method, the unfamiliar screen or the interrupted conversation. Then test the smallest repair. That approach makes less sense when customers rarely use WhatsApp, or when payment access is already smooth. A storefront cannot repair poor delivery or an unwanted product. Liquido’s useful insight is narrower, and better for it: sometimes the buyer is ready, and the machinery needs to catch up.