Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

PagBank — connector

Planned connector: reading PagBank charges does not exist yet because the API does not list account transactions — today the data enters via statement export to the receipt area.

On this page (16)

State: Roadmap — planned, still not implemented at this stage.

Read before: ../conectores.md (map of states) and fichas.md (index of fichas).


⚠️ Notice — Roadmap (not available)#

This connector is not implemented: configuration and execution are rejected by the product (nothing pretends to succeed).

The PagBank public API queries orders and charges by identifier and does not provide a paginated account listing — without a listing endpoint there is no way to extract on schedule.

The rest of this page describes the planned specification (fields and connection method), not an active feature.


What it is#

Planned connector: reading PagBank charges does not exist yet because the API does not list account transactions — today the data enters via statement export to the receipt area.

Supported ingestion modes:

  • We fetch — We fetch the data from your source.

Purpose#

Bring PagBank data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language question wizard.

When to use / when not to use#

Use when you need to consolidate this source in the datalake on a scheduled basis, with isolation per workspace.

Do not use for production today: the connector is on the Roadmap. Meanwhile, for files, use the "Você deposita" mode (upload files to the landing).

Plan and permissions#

  • Plan: core of the product (connectors are part of all plans; the limit is the number of sources in the plan).
  • Access: requires an active workspace — with the subscription overdue, suspended or canceled, the execution is blocked.
  • Shutdown: ingestion can be temporarily turned off (maintenance or incident). When this happens, the UI informs that the feature is unavailable at the moment.

Prerequisites#

  • A PagBank account with access to the data you want to ingest.
  • When the connector exists, the connection will use a PagBank API token (Integrações → Chaves). Today the API does not list account charges — it only queries by identifier — so configuration is rejected and the path is to export the statement to your environment's receipt area.

Credentials#

Authentication method: Access token pasted by you. It is encrypted (AES-256-GCM) and never shown again, nor appears in logs or error messages.

This connector does not require its own secrets (upload mode / no credential on the platform).

Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).

Form fields#

FieldLabelTypeRequiredNote
contaPagbankPagBank Account (informational)textnoOnly for registering interest — configuration is rejected while the connector does not exist.

Step by step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose PagBank in the catalog.
  3. Fill the form fields (see the table above).
  4. Use Testar conexão. The result is returned separated by Network (server reach), Authentication (user and password) and Read (list tables) — each with OK, Failed, Not applicable or Not tested.
  5. Use Salvar conexão. Saving DOES NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. On review, Publicar (agenda desligada) creates version 1 without executing anything. After that, Ativar agenda and Executar agora are separate actions.

In the current state (Roadmap), steps 4–5 are rejected by the product.

Example — connection test#

Sample configuration (all values are fictitious; secrets shown masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
contaPagbank = <contaPagbank>

Expected result#

The product refuses the configuration with a clear message that the connector is on the Roadmap.

Limits and costs#

  • Pagination: hard ceiling per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.3 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Scope by workspace: each customer reads and writes only to their own datalake (<prefix>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being persisted. The external credential vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
  • Production does not fake: a path that would fall into a mock triggers production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or missing the required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens on consecutive runs, open a support ticket indicating the connector and the resource.
  • Empty records path — the response arrived without records where expected. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network problems before scheduling.
  • Monitor the runs in the connector observability (error rate, p50/p95, freshness).
  • a schema change at the source is signaled by schema drift (new column = info; removed column/type changed = attention).

Related#


Last review: 2026-10-04. Card automatically generated from the product's connector catalog.

Related links