Skip to main content
GET
Why it’s useful: Use it to get a status update on every contribution you have submitted.

Payment Statuses

When Statuses Update

Status updates are not real-time. The status field is updated automatically by background processes as the payment moves through the clearing house. No action is required from your side.

Day 0 and the 4pm AEDT banking cut-off

The timeline below is counted in banking days from Day 0. Day 0 is set when the clearing house submits the debit request to the bank:
  • Submitted before 4pm AEDT on a banking day → Day 0 = that same day
  • Submitted at or after 4pm AEDT, or on a weekend/public holiday → Day 0 = next banking day
For example: submitting on a Friday at 5pm means Day 0 falls on the following Monday, since the 4pm cut-off is missed and the weekend is skipped — effectively pushing the entire timeline out by 3 days.

Summary Timeline

Note: The SuperStream process assumes all submissions succeed. The clearing house does not give us an exact settlement date, so the day range above — and the SETTLED / SETTLED_WITH_WARNING status itself — is only indicative. It is based on the super fund not rejecting the contribution within 3 business days of receiving it.

Field Reference

contributionDetails object

Stored at submission time and does not change.

statusHistory item

Fund Layer Response Fields

When processingLayer === 'FUND_LAYER' and the fund has responded, these fields are populated. They are null while the payment is in AWAITING_FUND_RESPONSE. Show fundResponseDescription and fundResponseDetailedDescription whenever any of the following are true:
  • status === 'SETTLED_WITH_WARNING'
  • status === 'REFUNDED'
  • fundResponseSeverity === 'WARNING' or 'ERROR'

Refund Fields

Populated when fundResponseType is MEMBER_REFUND, EMPLOYER_REFUND, or MEMBER_CONTRIBUTION_TYPE_REFUND. All five fields are null for NON_REFUND responses (i.e. SETTLED and SETTLED_WITH_WARNING).

Determining Completion

A payment record is fully complete (no further changes expected) when status is one of: SETTLED, SETTLED_WITH_WARNING, REFUNDED, FUND_TRANSFER_FAILED, DEBIT_FAILED, or CANCELLED.

Multi-fund submissions

One submission can include contributions to multiple funds. All records for a submission share the same transactionId. A submission is fully complete when every payment record for that transactionId has a terminal status. Use the transactionId query parameter on this endpoint to retrieve all records for a submission and check each one.

Multi-fund members

A member is fully complete when all their payment records have a terminal status. Filter by employeeId to retrieve all records across all funds for that member. Note: fundResponseReceivedAt is only populated for members with an explicit fund response — members settled silently will have fundResponseReceivedAt === null even when status === 'SETTLED'. Use the status-based check above instead.

Request Parameters

string
Filter to a specific clearing house transaction. Returns all payment records for that submission (one per fund).
string
Filter contributions by employer ID. When provided, returns contributions only for that employer and verifies the employer belongs to your client. When omitted, returns contributions from all employers belonging to your client.
string
Filter contributions by employee/member ID.
string
Created-at lower bound (ISO 8601). Only contributions submitted on or after this date will be returned.
string
Created-at upper bound (ISO 8601). Only contributions submitted on or before this date will be returned.
integer
Page number (default: 1)
integer
Page size (default: 10, max: 100)

Responses

Response fields

array
Array of payment records. One record per fund per submission.
object
Pagination metadata
boolean
Always false for error responses, indicating the operation did not succeed.
integer
HTTP status code indicating the type of error. Common values: 400 (Bad Request), 401 (Unauthorized), 404 (Not Found), 500 (Server Error)
string
Human-readable error message explaining what went wrong. May include specific details about which field or value caused the error.
integer
Superannuation clearing house-specific error code for programmatic error handling. Refer to the error code reference documentation for a complete list of codes.
Last modified on November 10, 2026