PagSeguro / PagBank
PagSeguro (operating consumer-facing under the PagBank brand) is one of Brazil's largest payment processors and digital-banking platforms. Originally spun out of UOL (Universo Online) and listed on the NYSE under PAGS, the company offers an end-to-end financial stack covering online payments, in-person card acceptance via the Moderninha and Minizinha terminal families, Pix instant payments, boleto, credit and debit cards, recurring subscriptions, marketplace split, payouts, account-as-a-service, and a digital bank with cards, credit, and investments. Its developer portal at developer.pagbank.com.br exposes a REST API surface (Orders, Charges, Public Keys, Checkout, Recurring, Connect/OAuth, Account Registration, EDI, Webhooks) backed by official SDKs in PHP, Java, Ruby, and .NET, plus WooCommerce, Magento/Adobe Commerce, and PrestaShop plugins.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles PagSeguro / PagBank the way a machine reads it — 40 machine-readable artifacts across 33 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — PagSeguro / PagBank scores 40.6/100 (thin), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile PagSeguro / PagBank
Each block below is one kind of artifact we hold for PagSeguro / PagBank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 33
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
PagBank Orders API
Core REST surface for creating and managing orders and their associated charges across credit card, debit card with 3DS, boleto, and Pix. Covers capture, cancel, refund, fees re...
PagBank Checkout & Payment Link API
Hosted checkout and shareable payment-link generation. Merchants create, activate, deactivate, and retrieve checkouts; PagBank renders the UI, handles payment-method selection a...
PagBank Public Keys API
Issues the public keys used for client-side card encryption in PagBank's transparent checkout. Lets merchants tokenise card data in the browser so raw PAN never reaches their se...
PagBank Recurring / Subscriptions API
Recurring-billing surface with plans, subscribers, subscriptions, invoices, coupons, refunds, and retry management. Supports activate, suspend, cancel, and per-subscriber paymen...
PagBank Pix API
Pix (Brazilian Central Bank instant-payment rail) charge creation and collection. Supports QR-code generation, due-date Pix (Pix Cobrança), and payment status retrieval, integra...
PagBank Boleto API
Boleto Bancário issuance and collection. Generates a printable / scannable boleto tied to an Order, with status callbacks once the buyer pays at a bank, lottery house, or via in...
PagBank Marketplace / Split API
Payment-division (split) settlement for marketplaces and platforms. Splits a single charge across multiple receivers (with optional custody / release control) so each seller is ...
PagBank Connect / OAuth API
OAuth-style authorisation surface that lets a third-party application act on behalf of a PagBank account holder. Includes SMS and challenge verification, access-token issuance, ...
PagBank Account Registration API
Lets PagBank partners create and query merchant accounts on behalf of third parties — the on-ramp for platforms that want to onboard sub-merchants into the PagBank ecosystem.
PagBank EDI API
Electronic Data Interchange surface for downloading transaction and settlement statements for reconciliation — a structured replacement for manual CSV/PDF statement processing.
PagBank Digital Certificate (mTLS) API
Issues digital certificates for mTLS authentication, layered on top of bearer-token auth for higher-trust integrations and sensitive payouts / Pix Bacen flows.
PagBank Webhooks / Notifications
Event-driven notifications for order, charge, subscription, refund, and checkout state changes. Webhooks are signed so receivers can verify authenticity end-to-end.
PagSeguro PHP SDK
Official PHP integration library for PagSeguro / PagBank.
PagSeguro Java SDK
Official Java integration library for PagSeguro / PagBank.
PagSeguro Ruby SDK
Official Ruby integration library for PagSeguro / PagBank.
PagSeguro .NET SDK
Official .NET / C# integration library for PagSeguro / PagBank.
PagBank PlugPag (Terminal Integration)
Bluetooth / Android terminal integration for PagBank's Moderninha and Minizinha card readers, enabling third-party apps to drive in-person card and Pix payments on PagBank hardw...
PagBank PlugPagServiceWrapper
Android service wrapper for integrating with the Moderninha / Minizinha terminal family — the official higher-level SDK on top of PlugPag.
PagBank for WooCommerce
Official WooCommerce plugin embedding PagBank checkout, Pix, boleto, and card payments in WordPress storefronts.
PagBank Payment for Magento / Adobe Commerce
Official Magento 2 / Adobe Commerce payment module for PagBank.
PagSeguro PrestaShop Module
Official PrestaShop transparent-checkout integration module for PagSeguro / PagBank.
PagSeguro / PagBank Accounts API
The Accounts API from PagSeguro / PagBank — 2 operation(s) for accounts.
PagSeguro / PagBank Charges API
The Charges API from PagSeguro / PagBank — 4 operation(s) for charges.
PagSeguro / PagBank Checkout API
The Checkout API from PagSeguro / PagBank — 4 operation(s) for checkout.
PagSeguro / PagBank Connect API
The Connect API from PagSeguro / PagBank — 6 operation(s) for connect.
PagSeguro / PagBank Coupons API
The Coupons API from PagSeguro / PagBank — 2 operation(s) for coupons.
PagSeguro / PagBank Invoices API
The Invoices API from PagSeguro / PagBank — 2 operation(s) for invoices.
PagSeguro / PagBank Orders API
The Orders API from PagSeguro / PagBank — 2 operation(s) for orders.
PagSeguro / PagBank Plans API
The Plans API from PagSeguro / PagBank — 4 operation(s) for plans.
PagSeguro / PagBank PublicKeys API
The PublicKeys API from PagSeguro / PagBank — 2 operation(s) for publickeys.
PagSeguro / PagBank Refunds API
The Refunds API from PagSeguro / PagBank — 2 operation(s) for refunds.
PagSeguro / PagBank Subscribers API
The Subscribers API from PagSeguro / PagBank — 3 operation(s) for subscribers.
PagSeguro / PagBank Subscriptions API
The Subscriptions API from PagSeguro / PagBank — 5 operation(s) for subscriptions.
Scroll within the panel for all 33 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
PagBank / PagSeguro REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Pagseguro Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Pagseguro Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for PagSeguro / PagBank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/pagseguro · machine-readable index on apis.io