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 publishes 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 9 more developer resources.

🌐 Visit website 📡 Source on GitHub
23.5/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
1 APIs
PaymentsAustraliaReal-Time PaymentsAccount-to-AccountISO 20022Direct DebitMandatesNew Payments PlatformScheme OperatorOpen Banking

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 23.5/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 8.0 / 10
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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/payto: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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 3

The organization behind the API

Website
Website
 Blog
Blog
 LinkedIn
LinkedIn

Source (apis.yml)

apis.yml Raw ↑ 
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.'
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-07-24'
enriched: '2026-07-24'
specificationVersion: '0.19'
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
  - 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:
- 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