SCR — Credit Information System

The SCR (Sistema de Informações de Crédito) is the Banco Central do Brasil's official registry of credit operations. Every financial institution in the country reports to it: loans, financing, limits, guarantees and co-obligations above R$200. It is the source itself, not a score inferred from it.

Pluggy exposes the SCR behind a connected Open Finance item. The item supplies the CPF or CNPJ and stands as the evidence of the account holder's consent.

Requirements#

Before the first call:

1. The SCR feature enabled on your subscription.
2. A connected Open Finance item. Direct connectors are not eligible.
3. That item's CPF or CNPJ known to us — it is what we query Bacen with.

An item that fails either of the last two returns SCR_ITEM_NOT_SUPPORTED.

Consult the SCR#

GET /items/{id}/scr

curl --request GET \
  --url 'https://api.pluggy.ai/items/d0e8448e-0156-4b4a-ae6c-3e2a6d9bff5c/scr?from=202604&to=202607' \
  --header 'X-API-KEY: YOUR_API_KEY'

Full parameter and schema detail lives in the API referenceAPI.

Base dates are months, and they lag#

The SCR does not work in days. Bacen consolidates one base date (data-base) per month, and each one only becomes complete a few months later — institutions are still delivering their reports in the meantime.

Two consequences worth designing around:

• Asking for the current month returns nothing. Bacen has not closed it yet.
• When you omit from and to, Pluggy consults the last 4 base dates, ending 2 months back from today. In September 2026 that is 202604 to 202607.

If you send only one bound, the window anchors on it: ?to=202501 returns 202410 through 202501.

Each base date carries docProc and volProc — the percentage of expected documents and volume already incorporated. A recent base date with low coverage is a partial picture, not an empty one.

Response#

The response is Bacen's own payload, forwarded unchanged. Field names, codes and structure are the SCR's, so a value you read here is the same value an institution reads at the source.

{
  "dtbConsult": "202604 a 202607",
  "cdCli": "11222333",
  "tpCli": "2",
  "lsDtb": [
    {
      "dtb": 202607,
      "docProc": "99.8",
      "volProc": "99.9",
      "qtdIfs": 4,
      "qtdCongFinc": 3,
      "dtbIniRel": "201803",
      "coobAss": 0,
      "coobRec": 0,
      "lsOp": [
        {
          "mod": "0203",
          "oriRec": "0101",
          "indx": "01",
          "varCamb": "00",
          "resVenc": { "v20": 12500.0, "v40": 12500.0, "v110": 37500.0 },
          "lsGar": [{ "tp": "0501", "qtd": 1 }]
        }
      ]
    }
  ]
}

Top level#

Inside a base date (lsDtb[])#

Inside an operation group (lsOp[])#

The SCR does not return contracts one by one. Operations are aggregated by the combination of modality, source of funds, index and exchange variation, so one entry can represent several contracts of the same nature.

The codes behind mod, oriRec, indx, varCamb and tp are Bacen's own. Their meaning is published in the DOC3040 reference — read them there rather than inferring them.

Maturity vertices (resVenc)#

resVenc distributes the group's balance across 30 vertices, in BRL. Only the vertices that carry a value are present. They fall into three families:

The exact window behind each individual vertex code is defined by the DOC3040 reference.

Errors#

A 502 carries a correlationId under data. Quote it when you report the failure to us — it is what lets us trace the exact consultation.

{
  "code": 502,
  "codeDescription": "SCR_SERVICE_UNAVAILABLE",
  "message": "Bacen's SCR service is temporarily unavailable. Please try again later.",
  "data": { "correlationId": "8047f6e9-bb9e-4b04-8515-e2210dc4c544" }
}