Sep31Transaction Callback Not Supported Exception
Exception thrown when the Receiving Anchor returns HTTP 404 for callback registration.
Raised from PUT /transactions/:id/callback when the anchor returns HTTP 404. Per SEP-31 §"PUT Transaction Callback", a 404 on this endpoint indicates that the Receiving Anchor does not support callback-based status notifications. Note: the spec does not separately define a response code for an unknown transaction id on this endpoint, so a 404 here could in principle also reflect a transaction-not-found condition — the SDK maps every 404 on PUT /callback to this exception. Lookups against GET / PATCH /transactions/:id continue to surface unknown-transaction 404s as Sep31TransactionNotFoundException.
Recovery actions:
Switch to polling
GET /transactions/:idto track transaction statusConfirm callback support with the Receiving Anchor operator before retrying
Example - Handle callback not supported:
try {
sep31Service.putTransactionCallback(
id = "11111111-1111-1111-1111-111111111111",
callbackUrl = "https://example.org/sep31-callback",
jwt = jwt
)
} catch (e: Sep31TransactionCallbackNotSupportedException) {
println("Callback not supported (HTTP ${e.statusCode}): ${e.message}")
// Fall back to polling.
}See also:
Sep31Exception base class
Sep31TransactionNotFoundException for the transaction-id 404 path
Parameters
Sanitized error message describing the callback rejection.
Properties
Anchor response body for local debugging — see the rawResponseBody convention on Sep31Exception. null when no body was captured.
The HTTP status code returned by the Receiving Anchor (always 404 for this exception).