Pinch Payments
Pinch Payments is an Australian, Brisbane-based payment orchestration and payment-facilitator platform that automates invoice collection and receivables for service businesses, bookkeepers, and software platforms across Australia and New Zealand. Marketing itself as "Aussie-Made Payments Infrastructure," Pinch lets merchants accept direct debit (bank account) and card payments (Visa, Mastercard, American Express), build payment plans and subscriptions, tokenise payment sources client-side with its CaptureJS library, and reconcile settlements back into Xero, QuickBooks, and MYOB. Its Glassbox / Managed Merchants offering is a Payfac-as-a-Service seam with KYC, compliance, and sub-merchant onboarding for platforms acting as aggregators or marketplaces. Pinch is genuinely API-first: it ships a fully documented REST API (JSON, OAuth2 client-credentials auth), a ReadMe-hosted developer portal with a live API explorer, per-product OpenAPI 3.1 definitions, a published Postman collection, an official .NET SDK, Zapier/n8n/viaSocket no-code connectors, webhooks for real-time events, and an llms.txt + docs MCP server for AI-assisted integration.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Pinch Payments the way a machine reads it — 43 machine-readable artifacts across 10 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 — Pinch Payments scores 55.0/100 (strong), with a separate agent-readiness read of 39/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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Pinch Payments'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/pinch-payments/"
title="Pinch Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pinch-payments.svg"
alt="Pinch Payments Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/pinch-payments/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pinch-payments/"
title="Pinch Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pinch-payments/card.svg"
alt="Pinch Payments 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 Pinch Payments
Each block below is one kind of artifact we hold for Pinch Payments. 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 17
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.
Pinch Payments Connect API
The Connect API from Pinch Payments — 1 operation(s) for connect.
Pinch Payments Contacts API
The Contacts API from Pinch Payments — 2 operation(s) for contacts.
Pinch Payments Events API
The Events API from Pinch Payments — 2 operation(s) for events.
Pinch Payments Fees API
The Fees API from Pinch Payments — 2 operation(s) for fees.
Pinch Payments Health API
The Health API from Pinch Payments — 1 operation(s) for health.
Pinch Payments Merchant Financial Data API
The Merchant Financial Data API from Pinch Payments — 2 operation(s) for merchant financial data.
Pinch Payments Merchants API
The Merchants API from Pinch Payments — 3 operation(s) for merchants.
Pinch Payments Payers API
The Payers API from Pinch Payments — 4 operation(s) for payers.
Pinch Payments Payment Links API
The Payment Links API from Pinch Payments — 3 operation(s) for payment links.
Pinch Payments Payments API
The Payments API from Pinch Payments — 7 operation(s) for payments.
Pinch Payments Plans API
The Plans API from Pinch Payments — 3 operation(s) for plans.
Pinch Payments Refund API
The Refund API from Pinch Payments — 1 operation(s) for refund.
Pinch Payments Refunds API
The Refunds API from Pinch Payments — 2 operation(s) for refunds.
Pinch Payments Subscriptions API
The Subscriptions API from Pinch Payments — 2 operation(s) for subscriptions.
Pinch Payments Tokens API
The Tokens API from Pinch Payments — 1 operation(s) for tokens.
Pinch Payments Transfers API
The Transfers API from Pinch Payments — 3 operation(s) for transfers.
Pinch Payments Webhooks API
The Webhooks API from Pinch Payments — 2 operation(s) for webhooks.
Scroll within the panel for all 17 ·
Postman Collections 10
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
authentication-api
POSTMANpinch-api-contacts
POSTMANpinch-api
POSTMANpinch-api-merchants
POSTMANpinch-api-payers
POSTMANpinch-api-payment-links
POSTMANpinch-api-payments
POSTMANpinch-api-transfers
POSTMANpinch-api-webhooks
POSTMANScroll within the panel for all 10 ·
Open Collections 10
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).
authentication-api
OPEN COLLECTIONpinch-api-contacts
OPEN COLLECTIONpinch-api
OPEN COLLECTIONpinch-api-merchant-financial-data
OPEN COLLECTIONpinch-api-merchants
OPEN COLLECTIONpinch-api-payers
OPEN COLLECTIONpinch-api-payment-links
OPEN COLLECTIONpinch-api-payments
OPEN COLLECTIONpinch-api-transfers
OPEN COLLECTIONpinch-api-webhooks
OPEN COLLECTIONScroll within the panel for all 10 ·
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.
Pinch API Docs MCP
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.
Pinch Payments 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Pinch Payments — 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 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
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/pinch-payments · machine-readable index on apis.io
This is an independent, third-party profile of Pinch Payments, 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.