Blankfactor fixes what the payment screen hides

The rewards app was in trouble before Blankfactor arrived. Its code was unstable, the experience was poor, and the client had barely involved its own IT team in the original build. There was no developer handover or documentation to ease the rescue. For a product meant to make spending points pleasant, this was an awkward collection of problems.

In Blankfactor’s published account, the client was one of the three largest global payment processors. The results narrative identifies Mastercard. The assignment began with stabilization, then extended to documentation, a platform migration, and the product roadmap. Think of a mechanic discovering that the car needs both repairs and a missing owner’s manual.

The company reports a 52-fold reduction in crashes and a $12 million annual increase in rewards redemption. Redemption measures rewards being used; it should never be mistaken for Blankfactor’s revenue. Still, the case supplies a useful opening question: how much of a financial product’s potential is trapped inside engineering work that nobody sees?

The rewards-app story offers a related purchasing lesson. The first failure described was basic product reliability, compounded by weak ownership of the original build. Before commissioning a bigger roadmap, a buyer can ask for documentation, an accountable technical counterpart, and explicit stability targets. That changes the conversation from how many features a team can ship to whether the organization can maintain what it already has.

01 / The machinery behind the tap

Blankfactor occupies the space between a financial institution’s ambition and its working software. A buyer can hire it to design a product, build its front and back ends, test it, move workloads to the cloud, or replace the data infrastructure underneath it. Its enterprise AI offering sits alongside those services. There is no single Blankfactor app that explains the business.

Its payments work includes the vocabulary consumers rarely encounter: issuing, acquiring, orchestration, settlement, reconciliation. These are the systems that help a transaction become an accurately recorded movement of money. An attractive interface can introduce a service. Keeping the records straight is what lets the service continue.

That promise becomes more concrete in the components described by its investor, Balance Point Capital: mobile wallets, ledgers, billing and pricing engines, settlement, and reconciliation. These accelerators suggest a way to reuse accumulated engineering work across customers. They also help explain the attraction of a sector specialist. A team familiar with the transaction lifecycle can begin a discussion with the operational problem, before debating which framework should implement it.

The commercial model follows that complexity. Blankfactor sells consulting and engineering engagements to businesses, including longer relationships that span several stages of a project. It describes its approach as outcome-based delivery. That is a positioning claim, not evidence that every contract carries the same fee arrangement. Buyers still need to define what completion means.

02 / Keep the learning. Repeat the execution.

Modern Treasury gives the model a particularly clear outline. In April 2025, the payment operations company formalized a partnership with Blankfactor to support enterprise implementations. Such customers can bring specialized payment rails and legacy systems, making integration a substantial technical assignment.

The revealing detail is how Modern Treasury divides the work. Its own team handles new implementations so that unfamiliar customer requirements can feed product improvements. Blankfactor helps with repeat integrations, extending delivery capacity around work the platform company already understands.

“For repeat integrations, Blankfactor acts as an extension of our technical team”Preet Narisetty · Modern Treasury · April 2025

That distinction is something another software business can copy. Preserve direct contact with novel problems. Once the implementation becomes repeatable, build a delivery process that can travel beyond the original team. The partnership makes specialization useful on both sides: Modern Treasury learns about its product; Blankfactor supplies implementation expertise.

03 / The old answers must survive the move

A separate wealth-management project shows what this looks like below the application layer. An unnamed client wanted to bring together analytics scattered across data sources and warehouses. Blankfactor describes a phased migration into a Snowflake-based data platform, with an ingestion framework designed to accommodate additional sources.

Most instructive was the checking. The engineers built automated tests that queried both the legacy and replacement warehouses, exposing discrepancies for investigation. They also designed access roles and trained the client to manage them. Faster data is useful only when the people receiving it can trust the answers and are entitled to see them.

The case also points to the limits of hiring an outside specialist. Business users still need to own rules for cleaning, classification, and governance. In practice, a client that cannot make those decisions leaves its engineers waiting for answers that architecture alone cannot supply. Buying a migration does not remove the work of understanding the business.

04 / A specialist gets a bigger home

Co-founders Michael Wear and Melody Pak built a geographically distributed organization. Blankfactor’s history records a Colombian operation in 2016 and a Sofia delivery center in early 2021. Its founding date is 2015 in that account. Pak’s background includes Yale and a Stanford master’s in Learning, Design, and Technology, an interesting preparation for translating ideas into usable products.

That organization also invests in teaching: its careers materials describe an internal learning platform, a Talent Academy, and a six-month funded internship. For a services business, developing engineers is closely connected to developing the product customers actually buy: the team’s judgment.

Globant announced its acquisition in September 2024; its accounts record an October closing. The announcement said Blankfactor served six of the ten largest payment processors, with more than 450 technology professionals spanning expertise from COBOL to AI. Blankfactor now operates within Globant’s North American Payments Studio.

The purchase had a substantial upfront component: Globant’s 2024 accounts identify about $141.2 million in cash and $69.2 million in shares for Blankfactor, with additional installment and contingent consideration. Those acquisition payments tell us what the buyer committed, not what a customer should budget for an engineering project.

Against large consultancies or an internal build, Blankfactor’s case rests on concentrated financial-services experience and hands-on execution. That makes it worth considering when the brief includes systems that must work together. A buyer seeking an immediately usable, off-the-shelf application has a different shopping list. For the rewards app, the immediate need was simpler: stop crashing, recover the missing knowledge, then give the product room to grow.