PayTo

PayTo is Australia's real-time mandated-payments service, operated by Australian Payments Plus (AP+) as an overlay on the New Payments Platform (NPP). It lets merchants, billers, and payment service providers establish digital, pre-authorised agreements (mandates) that debit a customer's bank account in real time using either a PayID or BSB and account number, with the mandate authorised, viewed, and managed by the account holder inside their own banking app. PayTo is positioned as the modern successor to the legacy BECS direct-debit rails, adding instant settlement, richer ISO 20022 data, and central mandate management via the NPP Mandate Management Service. As a domestic rail and scheme operator, AP+/NPP Australia is documentation- and rulebook-first: it publishes the NPP API Framework (v5.0, aligned to ISO 20022) that defines the mandatory data attributes and technical approach for PayTo and NPP APIs, but it does not itself host or offer a self-serve public API. The actual PayTo APIs are implemented and exposed by NPP Participants (banks) and connected payment service providers, so the company's public developer surface is a portal, framework, sandbox, and message specifications rather than a downloadable OpenAPI.

PayTo is listed with 1 API on the APIs.io network. Tagged areas include Payments, Australia, Real-Time Payments, Account-to-Account, and ISO 20022.

PayTo’s developer surface includes documentation, signup flow, engineering blog, support, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

18.6/100 emerging ▬ flat Agent 0/100 human only saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Payments Australia Real-Time Payments Account-to-Account ISO 20022 Direct Debit Mandates New Payments Platform Scheme Operator Open Banking

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 18.6/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.5 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.5 / 10

Discoverability 5.5 / 9

Regulatory Posture 2.3 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/payto/"><img src="https://apis.io/badge/payto/card.svg" alt="PayTo on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

13 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 26.2 — up to +14.8 composite points
Access Clarity scores 34.2 — up to +13.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/payto/apis.yml: open an issue on github.com/api-evangelist/payto to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Australia AFS, Credit and ADI Registers (ASIC + APRA licensing)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

ISO 20022

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

NPP and PayTo

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

PayTo / NPP Developer Resources

PayTo's public developer surface, published by Australian Payments Plus (AP+) and NPP Australia. Rather than a self-serve API hosted by the scheme, this covers the AP+ Developer...

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Payto Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

aid: payto
url: https://raw.githubusercontent.com/api-evangelist/payto/refs/heads/main/apis.yml
name: PayTo
kind: company
description: 'PayTo is Australia''s real-time mandated-payments service, operated by Australian Payments Plus (AP+) as an
  overlay on the New Payments Platform (NPP). It lets merchants, billers, and payment service providers establish digital,
  pre-authorised agreements (mandates) that debit a customer''s bank account in real time using either a PayID or BSB and
  account number, with the mandate authorised, viewed, and managed by the account holder inside their own banking app. PayTo
  is positioned as the modern successor to the legacy BECS direct-debit rails, adding instant settlement, richer ISO 20022
  data, and central mandate management via the NPP Mandate Management Service. As a domestic rail and scheme operator, AP+/NPP
  Australia is documentation- and rulebook-first: it publishes the NPP API Framework (v5.0, aligned to ISO 20022) that defines
  the mandatory data attributes and technical approach for PayTo and NPP APIs, but it does not itself host or offer a self-serve
  public API. The actual PayTo APIs are implemented and exposed by NPP Participants (banks) and connected payment service
  providers, so the company''s public developer surface is a portal, framework, sandbox, and message specifications rather
  than a downloadable OpenAPI.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- Australia
- Real-Time Payments
- Account-to-Account
- ISO 20022
- Direct Debit
- Mandates
- New Payments Platform
- Scheme Operator
- Open Banking
created: '2026-07-24'
modified: '2026-10-06'
enriched: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: payto:payto-npp-developer-resources
  name: PayTo / NPP Developer Resources
  description: PayTo's public developer surface, published by Australian Payments Plus (AP+) and NPP Australia. Rather than
    a self-serve API hosted by the scheme, this covers the AP+ Developer Portal (login-gated APIs and documentation sections),
    the NPP API Framework v5.0 that defines the ISO 20022-aligned data attributes and technical approach for PayTo agreements
    and payment initiation, and the NPP API sandbox for building and testing NPP-based solutions. The production PayTo APIs
    are implemented by NPP Participants and connected payment service providers, not by the scheme itself.
  humanURL: https://www.developers.auspayplus.com.au/
  tags:
  - PayTo
  - New Payments Platform
  - Mandates
  - ISO 20022
  tags_raw:
  - PayTo
  - NPP
  - Mandates
  - ISO 20022
  properties:
  - type: DeveloperPortal
    url: https://www.developers.auspayplus.com.au/
  - type: Documentation
    url: https://www.developers.auspayplus.com.au/docs/
  - type: Documentation
    url: https://www.auspayplus.com.au/brands/nppa-for-developers
  - type: Documentation
    url: https://www.auspayplus.com.au/solutions/npp-resources-faqs
  - type: SDKDocumentation
    url: https://www.auspayplus.com.au/wp-content/uploads/2024/06/NPP-API-Framework-v5.0.pdf
common:
- url: https://www.auspayplus.com.au/feed
  type: BlogRSS
- type: DomainSecurity
  url: security/payto-domain-security.yml
- type: Conformance
  url: conformance/payto-conformance.yml
- type: LLMsTxt
  url: llms/payto-llms.txt
- type: GitHubOrganization
  url: https://github.com/auspayplus
- type: Website
  url: https://www.auspayplus.com.au/brands/payto
- type: DeveloperPortal
  url: https://www.developers.auspayplus.com.au/
- type: Documentation
  url: https://www.developers.auspayplus.com.au/docs/
- type: SignUp
  url: https://www.developers.auspayplus.com.au/api/auth/signup/
- type: Blog
  url: https://www.auspayplus.com.au/news
- type: Support
  url: https://www.auspayplus.com.au/contact-us
- type: TermsOfService
  url: https://www.auspayplus.com.au/terms-of-use
- type: PrivacyPolicy
  url: https://www.auspayplus.com.au/privacy-policy
- type: LinkedIn
  url: https://www.linkedin.com/company/auspayplus
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

PayTo API — frequently asked questions

Does PayTo have an API?

Yes. APIs.io lists 1 API from PayTo, including PayTo / NPP Developer Resources.

Is the PayTo API ready for AI agents?

PayTo has a Kin Score of 18.6 out of 100 (emerging) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/payto"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/payto/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/payto/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.