Nppa Swift NPP Australia API

Name: NPP Australia API
Brand: NPP Australia API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayouts TransfersapiKey2 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the NPP Australia API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NPP Australia API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NPP Australia API.

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

GET STARTED

Start building with NPP Australia API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use NPP Australia API for, with concrete tasks.

★ 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.

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.

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.

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

2 endpoints — jentic publishes the only available openapi specification for npp australia api, keeping it validated and agent-ready.

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

POST

/payments

Send a real-time payment via the NPP rail

GET

/payments/{id}

Get the settlement status of a previously submitted payment

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The NPP Australia API key is stored encrypted in the Jentic vault and injected into the Authorization header at request time. The agent context never contains the raw key, which is essential for a regulated payments rail.

Intent-based discovery

Agents search Jentic with intents like 'send a real-time australian payment' and Jentic returns the POST /payments operation with its input schema — there are only two endpoints, so selection is unambiguous.

Time to first call

Direct NPP Australia integration: 3-5 days plus partner onboarding by SWIFT. Through Jentic: under 1 hour once the partner key is provisioned — search, load schema, execute.

FAQs

Specific to using NPP Australia API through Jentic.

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 at https://app.jentic.com/sign-up.

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.