Prometeo has expanded its account-checking tools into a broader trust layer meant to give companies more certainty before they send money. The company announced Account Verification Boost on September 29, 2026, combining wider geographic reach, a new risk-intelligence product, and a rebuilt validation engine.
The goal is as follows: confirm that a destination account exists, that it belongs to the intended party, and that the person or firm behind it is appropriate to deal with.
Cross-border payments have long been treated as a connectivity problem.
Rails, local schemes, and APIs can move funds, but they do not by themselves answer whether an account is genuine or whether the counterparty is suitable.
Prometeo argues that businesses now need that pre-payment picture as much as they need settlement speed.
Banks, payment firms, remittance operators, marketplaces, treasury teams, and even AI agents can use one API and consistent logic instead of stitching together country-by-country checks.
Coverage is the first piece of the upgrade.
Account verification now spans more than 110 countries across five continents.
That scale is intended to let a single integration support onboarding, payouts, and payment flows without rebuilding validation for each market.
The company positions the service as AI-native infrastructure, so automated systems can apply the same checks that human operations teams use.
The second piece is Risk Intelligence, a new endpoint that can sit beside account verification or run on its own.
Clients submit a legal name and tax identifier.
In return they receive structured information on identity and legal standing, ownership, sanctions and other regulatory signals, adverse media, and corporate registry data.
The product is live in Brazil, Peru, Ecuador, and Chile, with planned expansion to Argentina, Colombia, Mexico, and the United States.
Prometeo says the feed is meant to speed investigations and support dynamic know-your-business work before a transfer is sent.
It is designed to inform a customer’s own compliance rules, not replace them.
Account Verification V2 is the third element.
The new engine adds configurable workflows, standardized responses, request tracing, a sandbox for moving off version one, and routing that can fail over to another eligible data source if one provider is down.
Teams can choose countries, data fields, and methods for each use case, including account existence, account-holder name, identity document, and currency.
Checks can run in real time or asynchronously.
Every request gets a unique identifier and a consistent response format, which should make it easier for product, engineering, and operations staff to debug failures and handle exceptions.
Co-CEO and co-founder Ximena Aleman framed the launch as a shift from a binary account check to operational certainty.
Firms that work across markets, she said, need to know an account is valid, that it belongs to the intended holder, and that the party behind it is appropriate to engage.
Prometeo’s recent pitch is basically that connecting to payment rails is no longer enough; companies also need a validation layer that is deeper, wider, and more intelligent about counterparties. Combined, the new coverage, risk data, and engine are meant to cut avoidable payment failures, manual cleanup, and operational drag before funds leave.