Optionalcause: unknownOptionalspend: MppSpendReportOptional ReadonlycauseThe original error fetch (or the mint) rejected with.
Optional ReadonlycodeOptionalspendSpend accounting, set when this error was raised after a credential had
been minted and presented. Absent means nothing was spent. Prefer
mppSpendOf, which also reads it off a PaymentsError.
OptionalstackStaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticprepare
The buyer-side mirror of MppSettlementOutcomeUnknownError: raised when the retry that carries a credential fails at the transport level — a disconnect, a DNS failure, or the caller's own
AbortSignalfiring between the mint and the retry (init.signalis re-sent with it).The credential is on the wire by then, so the seller may already have verified and burned it. Left as the raw
TypeErrorthatfetchrejects with, the failure would escape thecatch (e) { if (e instanceof MppError) }pattern this module andmarkdown/mpp-integration.mdboth prescribe, and carry no accounting at all: spent, invisible, unrecoverable. Wrapped, it reaches the documented handler with MppSpendReport attached and the original error preserved oncause.A transport failure BEFORE any credential exists is not this error — it stays exactly as
fetchthrew it, because nothing was spent and wrapping it would only obscure a plain network fault.