Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
PicPay website screenshot

PicPay

PicPay is a Brazilian fintech super-app and digital bank serving over 67 million users with a digital wallet, payment account, credit and debit cards, personal loans, investments (Cofrinho / fixed income), insurance, and PIX-based money movement. Founded in 2012 and acquired by J&F Investimentos (the holding company behind JBS) in 2015, PicPay is controlled today by J&F Participações and in 2024 incorporated the retail customer base of Banco Original to consolidate the group's consumer banking strategy. For developers and merchants, PicPay Business exposes a set of REST APIs that let online stores accept the PicPay wallet, credit/debit cards, PIX, and payment links as payment methods. The historical Ecommerce Public API on appws.picpay.com is authenticated with the x-picpay-token / x-seller-token headers and remains in use for direct wallet checkout. A newer unified business developer portal at developers-business.picpay.com publishes the Gateway PicPay Checkout API, Carteira PicPay Wallet API, PIX API, and Payment Link API, all of which now use OAuth 2.0 client_credentials bearer JWTs minted at api.picpay.com/oauth2/token (5-minute TTL) and webhook callbacks for payment status notifications. PicPay also publishes GitHub repos for Magento, Shopify, and Wake ecommerce integrations, plus its open developer documentation for the wallet and PIX APIs under picpay.github.io. PicPay reported a return to profitability in 2023 and is reportedly working with Citigroup on a U.S. IPO.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles PicPay the way a machine reads it — 5 machine-readable artifacts across 4 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 — PicPay scores 22.8/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 22.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.8 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Regulatory · Banking & Open Finance 4.6 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile PicPay

Each block below is one kind of artifact we hold for PicPay. 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 4

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.

PicPay Ecommerce Checkout API

Public REST API on appws.picpay.com that lets merchants charge a PicPay user's wallet from an ecommerce checkout. Creates a payment with a referenceId, returns a payment URL plu...

PicPay Gateway Checkout API

Unified payment gateway API for accepting credit cards, PIX, and the PicPay wallet through transparent, standard, or lightbox checkout flows. Exposes charges, charge cancellatio...

PicPay PIX API

REST API for accepting PIX (Brazil's instant payment rail) as a payment method in ecommerce. Supports PIX cobrança (charge / QR code generation), payment confirmation, refunds, ...

PicPay Payment Link API

Lets merchants accept remote sales by generating a hosted PicPay checkout link that can be paid with credit card, PIX, or the PicPay wallet. Useful for social-commerce, invoicin...

Security Posture 1

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.

Picpay Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for PicPay — 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

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/picpay · machine-readable index on apis.io