canonical: https://jentic.com/apis/nppa.swift.com/nppa-swift

# Nppa Swift NPP Australia API

Jentic publishes the only available OpenAPI specification for NPP Australia API, keeping it validated and agent-ready. The NPP Australia API provides programmatic access to the New Payments Platform, Australia's real-time, account-to-account payments rail operated under SWIFT. It exposes endpoints for submitting a payment instruction and retrieving the status of a previously sent payment, allowing financial institutions and authorized fintechs to settle funds within seconds, 24/7. Authentication is via an API key passed in the Authorization header.

## For AI agents

Submit and track real-time, account-to-account payments on Australia's New Payments Platform (NPP) for sub-minute settlement.

## Scope

Does not handle card payments, foreign-exchange conversion, or non-AUD rails - use for real-time account-to-account transfers within Australia only.

## Capabilities

- Submit a real-time NPP payment instruction between Australian bank accounts
- Retrieve the settlement status of a previously submitted NPP payment by id
- Authenticate API calls with a partner API key in the Authorization header
- Operate against the NPP rail's 24/7 clearing and settlement window

## Use cases

### Real-Time Disbursements to Australian Customers

Insurers, payroll providers, and marketplaces use NPP to credit Australian customer accounts within seconds rather than waiting for next-day batch settlement. The API takes a payment instruction with payer and payee details, returns an id, and exposes a status endpoint so the caller can confirm settlement before notifying the recipient.

Example prompt: Submit a payment of 250.00 AUD via POST /payments to a recipient BSB and account number, capture the returned id, then poll GET `/payments/{id}` until the status is settled.

### Payment Status Reconciliation

Treasury and operations teams reconcile outbound disbursements by polling the NPP status endpoint for each payment id captured during submission. Because NPP runs 24/7, status responses can be reconciled outside banking hours, which is critical for weekend payouts and incident response.

Example prompt: For each payment id queued in the last hour, call GET `/payments/{id}` and write the returned status into the treasury ledger.

### Agent-Driven Instant Payout Flow

An operations agent receives a refund or payout request, validates the payee account details, and uses Jentic to call the NPP submit endpoint without hand-coded API plumbing. The agent then watches the status endpoint and notifies the requester once settlement is confirmed.

Example prompt: Search Jentic for 'send a real-time australian payment', load the POST /payments schema, execute it with payer and payee fields, then load GET `/payments/{id}` and poll until status is final.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payments` | Send a real-time payment via the NPP rail |
| GET | `/payments/{id}` | Get the settlement status of a previously submitted payment |

## Key resources

- **Payments** — Submit a new NPP payment and retrieve the status of an existing one

## Why Jentic

- **Setup:** Wiring NPP Australia by hand means setting up its API key in the Authorization header against api.nppa.swift.com and satisfying the rules of a real-time payments rail on every call yourself. Through Jentic you install once, import the NPP Australia API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** NPP Australia submits a payment from the request body and exposes only a path-keyed read at `/payments/{id}`, so scope the agent to the operations it needs, such as reading a payment status. You choose that set, so submitting a new payment via POST /payments is not included unless you add it.
- **Credential handling:** Your NPP Australia API key is stored once, encrypted, by your own Jentic One instance and injected at execution time as the Authorization header. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a real-time Australian payment' or 'check a payment status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Global card and bank-payment platform; choose for international acceptance, not Australian-only real-time rails.
- **Adyen Account Service** — Multi-region payment platform with broad alternative-payment-method coverage.
- **PayPal Payouts** — Add a PayPal-wallet payout option for recipients without an Australian bank account.

## FAQ

### Why is there no official OpenAPI spec for NPP Australia API?

SWIFT does not publish an OpenAPI specification for the NPP Australia developer API. Jentic generates and maintains this spec so that AI agents and developers can call NPP Australia API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the NPP Australia API use?

The API uses an API key passed in the Authorization header (the spec defines a single ApiKeyAuth scheme). Jentic stores the partner API key encrypted and injects it into outbound requests, so agents never see the raw key. Access is restricted to financial institutions and approved fintechs onboarded by SWIFT.

### Can I send real-time payments to any Australian bank with the NPP Australia API?

POST /payments submits an instruction onto the NPP rail, which clears and settles between participating Australian financial institutions. The vast majority of Australian banks and credit unions participate, but a small number of older institutions may still rely on legacy rails - verify the payee BSB participates before relying on instant settlement.

### How do I check whether an NPP payment has settled through Jentic?

Search Jentic with 'check npp payment status', load GET `/payments/{id}`, and execute it with the id returned by your earlier POST /payments call. The response indicates whether the payment is pending, settled, or rejected.

### Does the NPP rail support 24/7 settlement?

Yes. NPP is designed for sub-minute settlement, 365 days a year, including weekends and public holidays. This is the main reason businesses move from legacy direct-entry batches to NPP for refunds, payroll-out-of-cycle, and emergency disbursements.

### Can I limit what my agent is allowed to do with the NPP Australia API?

Yes. Because Jentic One is self-hosted, you run the instance and your own rules decide which operations and credentials the agent may use. The NPP Australia API exposes just two operations, POST /payments to submit a real-time payment and GET `/payments/{id}` to read a payment's settlement status, so you can grant your agent only the read on `/payments/{id}` for reconciliation and monitoring. Submitting a new payment via POST /payments is not available to the agent unless you explicitly add it to the allowed set, and the stored API key is injected at execution time rather than exposed to the agent.