PPRO
PPRO is a local payments infrastructure company that lets payment service providers, acquirers, platforms and enterprise merchants accept the payment methods consumers actually use in their own market — bank redirects such as iDEAL, BLIK, Przelewy24 and Pay By Bank, wallets such as Alipay, WeChat Pay, Amazon Pay, Cash App Pay, TWINT and Swish, cash and voucher rails such as Boleto, OXXO, Multibanco and Indomaret, SEPA Direct Debit, Pix, UPI, BNPL and stablecoins — through a single REST integration. The PPRO Global API is an OpenAPI 3.1 platform built around four core objects (payment charges, payment instruments, payment agreements and payment sessions) plus captures, refunds, voids, fund statuses, disputes and chargebacks, with CloudEvents 1.0.2 webhooks, an idempotency-key contract, a documented token-bucket rate limit, a Drop-in Checkout component library and a hosted Model Context Protocol server so coding agents can call the platform directly.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles PPRO the way a machine reads it — 26 machine-readable artifacts across 21 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 — PPRO scores 54.0/100 (developing), with a separate agent-readiness read of 47/100 (agent native). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from PPRO's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ppro/"
title="PPRO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ppro.svg"
alt="PPRO Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ppro/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ppro/"
title="PPRO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ppro/card.svg"
alt="PPRO Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile PPRO
Each block below is one kind of artifact we hold for PPRO. 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 18
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.
PPRO Authorization Endpoints API
The Authorization Endpoints API from PPRO — 5 operation(s) for authorization endpoints.
PPRO Capture Endpoints API
The Capture Endpoints API from PPRO — 2 operation(s) for capture endpoints.
PPRO Dispute Reports API
Endpoints for generating and retrieving dispute reports
PPRO Disputes API
The Disputes API from PPRO — 6 operation(s) for disputes.
PPRO Enrollment Endpoints API
The Enrollment Endpoints API from PPRO — 2 operation(s) for enrollment endpoints.
PPRO Internal API
The Internal API from PPRO — 4 operation(s) for internal.
PPRO Merchants API
Merchant management
PPRO Payment Agreement Revocations API
The Payment Agreement Revocations API from PPRO — 1 operation(s) for payment agreement revocations.
PPRO Payment Agreements API
The Payment Agreements API from PPRO — 2 operation(s) for payment agreements.
PPRO Payment Charge Controller API
The payment-charge-controller API from PPRO — 1 operation(s) for payment-charge-controller.
PPRO Payment Charges API
The Payment Charges API from PPRO — 1 operation(s) for payment charges.
PPRO Payment Instruments API
The Payment Instruments API from PPRO — 2 operation(s) for payment instruments.
PPRO Payment Sessions API
The Payment Sessions API from PPRO — 3 operation(s) for payment sessions.
PPRO People API
Person management
PPRO Platforms API
Platform management
PPRO PS Ps API
PSP management
PPRO Refund Endpoints API
The Refund Endpoints API from PPRO — 2 operation(s) for refund endpoints.
PPRO Void Endpoints API
The Void Endpoints API from PPRO — 2 operation(s) for void endpoints.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
PPRO Global API MCP Server
PPRO publishes a first-party, hosted Model Context Protocol server that fronts the Global API. It is a streamable-HTTP MCP server (serverInfo global-api-mcp 1.0.0, protocolVersi...
MCP SERVERPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Ppro Plans Pricing
PLANSRate 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.
Ppro Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Ppro Webhooks
ASYNCAPISecurity Posture 4
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.
Resources
Every other property we hold for PPRO — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ppro · machine-readable index on apis.io
This is an independent, third-party profile of PPRO, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.