PayJoy
PayJoy is a fintech that provides financial access to underserved consumers in emerging markets through smartphone financing and a secured credit card that requires only a government ID. Its Partner Developer Portal exposes a REST Partner API (Sales Integration) so retail and OEM partners can integrate PayJoy point-of-sale financing: retrieve cart and sale information, list merchants and sales clerks, offer and process customer repayments, create and pay payment references, redeem and cancel vouchers, pay down payments, and pull transaction history for reconciliation. A separate E-commerce API supports online checkout and credit-application flows. Authentication is by API key; webhooks are HMAC-SHA256 signed. Founded 2015; backed by Greylock and Union Square Ventures.
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 PayJoy the way a machine reads it — 13 machine-readable artifacts across 9 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 — PayJoy scores 49.8/100 (developing), with a separate agent-readiness read of 65/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.
How we profile PayJoy
Each block below is one kind of artifact we hold for PayJoy. 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 9
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.
PayJoy E-commerce API
REST API for online checkout and credit-application flows: retrieve supported devices, begin a sale, and receive completion webhooks. Bearer-token authenticated plus a symmetric...
PayJoy Carts API
Retrieve cart information.
PayJoy Down Payments API
The Down Payments API from PayJoy — 1 operation(s) for down payments.
PayJoy Merchants API
Retrieve merchants information.
PayJoy Reconciliation API
The Reconciliation API from PayJoy — 1 operation(s) for reconciliation.
PayJoy Repayments API
The Repayments API from PayJoy — 3 operation(s) for repayments.
PayJoy SalesClerks API
Retrieve sales clerks information.
PayJoy Status API
Displays the status of the application.
PayJoy Vouchers API
Endpoints related to vouchers management
Scroll within the panel for all 9 ·
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.
payjoy-mcp.yml
MCP SERVEREvent 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.
Payjoy Webhooks
ASYNCAPISecurity 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.
Resources
Every other property we hold for PayJoy — 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 1
Reference material describing how the API behaves
Agent Surfaces 3
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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/payjoy · machine-readable index on apis.io