This instance couldn't reach its API specification on the last attempt, so this page shows the copy fetched before that. Anything added or changed since then is missing here, and the reference updates itself as soon as the specification is readable again. Last fetched 2026-11-12 05:58 UTC.
Moves the transaction to the requested outcome and publishes the same
`Transaction.AchStatusChanged` and `Transaction.Returned` events a real ACH lifecycle
produces, so an ACH webhook can be proven in one session instead of over several days. Sandbox
only: a key stamped for the live world is refused, so is a caller carrying no environment
stamp, and so is any transaction the simulator did not answer. Advancing the same transaction
to the same outcome twice delivers nothing the second time, because repeat deliveries of one
event id are dropped per destination.
Signed in, you can send this request to your own sandbox merchant from the console
and read the answer.
Sign in to try it.
Example request
Each example below is one request, shown in every language. Choose an example and a language, then replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.
The request body is a SandboxAchStatusAdvanceRequestDto. See the Request body section below for its fields.
Parameters
Name
In
Type
Description
idrequired
path
string (uuid)
The loopback ACH sale to advance. Must belong to the calling key's merchant.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
suppressNullsrequired
query
boolean
If true, omit properties with null values.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
The settlement status to drive the transaction to: a terminal outcome, or one of the
intermediate statuses a debit passes through on the way to one. Required.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
SettlementSucceeded
The debit cleared and the money moved. The ordinary success case.
SettlementRolledBack
The receiving bank returned the debit. Requires a NACHA return code and reason. Arriving after SettlementSucceeded makes it a late return, which the resulting Transaction.Returned event flags.
NotEligible
The entry was voided on the processor's side before it reached the ACH network.
SettlementFailed
The processor reported an error on the entry rather than accepting it.
Accepted
The processor accepted the entry and queued it for the next origination window. The first intermediate status.
Verifying
The processor is verifying the account before origination. Follows Accepted.
Originated
The entry was originated onto the ACH network and is in flight. Follows Verifying.
PartiallySettled
Part of the amount has settled. The last intermediate status; follows Originated.
nachaReturnCoderequired
string
The NACHA return code to record, for example `R01`. Required when
`targetStatus` is `SettlementRolledBack`, and
rejected otherwise: a code on a settlement would be persisted and then published as part of an
event that says the debit cleared.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
nachaReturnReasonrequired
string
The return reason to record, for example `Insufficient funds`. Required alongside
`nachaReturnCode`, and rejected on any other outcome for the same reason.nullablemax length 120
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
previousStatusrequired
string
The settlement status the transaction held before the advance, by its literal name.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
newStatusrequired
string
The settlement status the transaction now holds, by its literal name.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
isLateReturnrequired
boolean
Whether this return arrived after the debit had already settled. Always `false`
for an outcome that is not a return. Derived from the status the transaction actually held, not
from anything the request said.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
achStatusChangedPublishedrequired
boolean
Whether the `Transaction.AchStatusChanged` event was published.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
returnedPublishedrequired
boolean
Whether the `Transaction.Returned` event was published. Only a return publishes it.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
This response has no documented body fields.
The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
This response has no documented body fields.
400Bad RequestBad request. The request was malformed or failed validation. When validation rejected it, `error.validationErrors` names each member at fault and why.
401UnauthorizedUnauthorized. The request carried no API key or signed-in session, or the key it carried is invalid, revoked or expired.
403ForbiddenForbidden. The API key lacks the scope this operation needs, the signed-in user lacks the permission, or a business rule refused the request. The error code in the body names the reason.
404Not FoundNot found. The resource the request names does not exist or is not visible to the caller: a resource that belongs to a merchant or tenant outside the caller's scope is reported as not found.
500Internal Server ErrorInternal server error. The platform failed unexpectedly while handling the request. If it keeps failing, contact support and quote the correlation id, which the response carries in the `X-Correlation-Id` header and as `error.data.correlationId`.
501Not ImplementedNot implemented. The operation is declared but has no implementation on this deployment, so no request to it can succeed. Retrying does not help.
defaultThe request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. The error reference lists the values `error.code` can take.The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. The error reference lists the values `error.code` can take.