Banks and fintech

Decide on the official record, not the form

Onboarding, origination, portfolio monitoring and collections query the same public records. Croma delivers them as one API so every credit decision carries its source.

Try it now

Free, no signup. The same query the API returns.

RUES lookup by NIT

Open the full tool

Digits only, without the verification digit. 4 to 15 digits.

Four moments when a bank needs the State

When onboarding a business customer you need to know whether it exists, who represents it and whether it is active. When originating, whether it is sanctioned, whether it is a state contractor and what figures it reported. With the loan placed, whether a debtor entered reorganization or appears in an enforcement case that has not reached the desk yet. And in collections, which court has the case, what was filed yesterday and which email receives notices.

Banco Finandina runs the court monitoring of its loan book on Croma: more than a hundred thousand cases reviewed every day against its portfolio, with every new filing detected within 24 hours. The other three moments use the same sources and the same key. Every signal arrives from its official registry, with provenance, ready for the decision engine or the analyst.

Workflow

What this team queries, and in what order

  1. 01

    Onboarding business customers

    RUES, Supersociedades and SICAAC in Colombia; SUNAT in Peru; SIEM in Mexico. Existence, representative, activity and reported figures by NIT or RUC.

    See the solution
  2. 02

    Screening at origination

    Contraloría, Procuraduría, Contaduría and SECOP sanctions in Colombia; OFAC for any counterparty. Records and lists before disbursing.

    See the solution
  3. 03

    Court monitoring of the loan book

    Rama Judicial, SAMAI and procedural publications against the debtor portfolio, with Croma Legal as the dashboard for the collections team.

    See the solution
  4. 04

    Vehicle collateral

    RUNT and SIMIT in Colombia; SOAT, SUTRAN and traffic tickets in Peru. The real state of the vehicle backing the loan.

    See the solution
Outcomes

What changes with the official record in the flow

  • Less friction at onboarding

    The NIT or RUC is enough to pull the full record. The customer never retypes what the State already knows.

  • Signals before the deterioration

    A new case against a debtor shows up in the monitoring the day it is published, not when the notice arrives.

  • One contract for five countries

    The same JSON in Colombia, Mexico, Peru, Brazil and the United States. One integration, one vendor, one SLA.

Compliance

What the compliance officer is going to ask

Every answer names the official source that produced it, so the file stays traceable. Lookups on individuals require a legitimate purpose under Ley 1581 de 2012 in Colombia (and its equivalents in each country); Croma runs the query against the source and the legal basis belongs to the institution. The API encrypts in transit, controls access by key and logs every request for audit.

  • Official sources only

    Every answer names the official registry that produced it. Nothing comes from purchased databases or third-party summaries.

  • Results that are never indexed

    In the free tools the query and the result live in your browser, never in a URL. In the API: encryption in transit, access control and audit logging.

  • Personal data, with rules

    Lookups on individuals require a legitimate purpose under each country's law: Ley 1581 in Colombia, LFPDPPP in Mexico, Ley 29733 in Peru, LGPD in Brazil. Croma delivers the record; the purpose and the legal basis are yours.

  • A stable contract

    Every field is documented in the OpenAPI, with a 90-day deprecation policy and Deprecation and Sunset headers before anything is retired.

What our customers say
The bank has saved hundreds of millions in just months with Croma.
Banco Finandina

Juan Pablo Santamaría · Director · Collections · Banco Finandina

Frequently asked questions

Yes. Every endpoint is an HTTP call with a JSON response documented in the OpenAPI. Origination engines consume the record like any other service; long jobs answer by webhook or status_url.

Croma Legal's monitoring reviews more than a hundred thousand cases a day against its customers' portfolios, detecting new filings within 24 hours. For large loan books you load the portfolio and receive the news; you do not query one by one.

Croma returns the public record the official source publishes for that identifier. The purpose, the data subject's authorization where it applies and the legal basis are the institution's responsibility, as with any direct query to the source. Nothing queried in the free tools is stored in a URL.

The endpoint answers with an explicit source-unavailable error, distinct from found: false, and the status page publishes incidents. Sources served from a dataset do not depend on the portal being up at query time.

Yes. Banco Finandina uses Croma for the court monitoring of its loan book. Book a demo and we show you the full flow with your own cases.

Bring the official record to every credit decision

One key covers onboarding, origination, monitoring and collections in five countries. Start with the free tool or book a demo with your portfolio.