Skip to main content
GET
List / export the buyer’s unified payment record across all agents

Authorizations

Authorization
string
header
required

Your Nevermined API Key (starts with 'nvm:'). Get one at nevermined.app under Settings > API Keys.

Query Parameters

delegationId
string

Only payments spent against this delegation id. Ignored with requestId.

from
string

ISO-8601 lower bound on createdAt (inclusive). Ignored with requestId.

Example:

"2026-07-01T00:00:00Z"

to
string

ISO-8601 upper bound on createdAt (inclusive). Ignored with requestId.

Example:

"2026-07-31T23:59:59Z"

requestId
string

Exact, caller-scoped idempotency key: look up the one payment made with it. Matched exactly as you sent it, padding included. Percent-encode it (an unencoded + reads as a space). Selects the lookup envelope (RouterPaymentLookupDto); the other list filters are ignored.

Minimum string length: 1
Example:

"order-1234"

format
enum<string>

Response format. Defaults to JSON; csv returns a downloadable file.

Available options:
json,
csv

Response

A JSON array for a list; the lookup envelope (RouterPaymentLookupDto) with requestId; or a CSV file when format=csv.

id
string
required
Example:

"b1f9c2e4-3d5a-4c7e-9f21-6a8b0c4d2e13"

createdAt
string
required
Example:

"2026-07-01T09:00:55.605Z"

status
enum<string>
required
Available options:
Issued,
Settled,
Failed
Example:

"Settled"

protocol
string
required
Example:

"x402"

network
string
required
Example:

"base-sepolia"

amount
string
required

Amount in the asset’s smallest unit.

Example:

"1000"

merchantAddress
string
required

The merchant's pay-to identifier: a 0x address for the crypto rails (x402 / MPP evm / MPP-tempo), or the seller's Stripe network business profile id (profile_…) for the MPP-stripe / SPT card rail.

Example:

"0x209693Bc6afc0C5328bA36FaF03C514EF312287C"

delegationId
string | null
required

The delegation this payment was reserved against. Null on a payment funded by a Nevermined Subscription, which spends subscription credits and no delegation.

Example:

"5e7481c3-..."

deliveryStatus
enum<string>
required

Buyer-visible outcome: delivered when the request settled; charged_not_delivered when it failed and the merchant charge was observed; charged_unconfirmed when the charge was observed but delivery is unconfirmed; not_charged when reconciliation proved the merchant did not charge; not_delivered (API v1.70+; a client pinned lower reads pending) when the merchant answered the paid call with an error (an x402 or MPP evm exact payment, or an MPP-tempo charge), so nothing was delivered, and no merchant charge has been observed yet: the merchant can still redeem the payment until its authorization expires, and reconciliation decides, after that expiry, whether it becomes not_charged or a charged_ value; pending when the charge outcome is unknown. On a not_delivered delegation payment the amount stays reserved until reconciliation decides, except that a merchant 402 on an exact payment has its merchant reserve released at once when the chain shows the authorization unspent. A credits-funded payment reserves nothing against a delegation: read creditsStatus. On SPT and card rails, pending is not proof of no charge.

Available options:
delivered,
charged_not_delivered,
charged_unconfirmed,
not_charged,
not_delivered,
pending
Example:

"delivered"

upstreamBodyBytes
integer | null
required

API 1.91+: decoded buffered paid response bytes before JSON/text/base64 conversion or catalog error withholding. Zero means an empty body, including on a 2xx. Null means unmeasured, including older payments, mode A, streaming, or incomplete reads the transport detects. A nonzero count does not prove a complete or useful answer. JSON only; CSV is unchanged. No change to charges or refunds. The API omits this field for clients pinned below 1.91.

Required range: x >= 0
Example:

0

feeFailureReason
string | null
required

Why the routing fee did not collect, or — on a feeStatus: None row — fee-not-quoted: <why> when a fee rate is configured but none was quoted for this payment. Diagnostic text for a human, NOT a stable contract: branch on feeStatus, never on this string. Whitespace is collapsed and any embedded scheme://… URL is replaced with [url] before publication. null when no fee rate is configured, and while a quoted fee is still on its happy path; a non-null value does not on its own mean the fee went uncollected — feeStatus says what happened.

Example:

"HTTP 400: {\"errorReason\":\"amount_too_low\",\"network\":\"eip155:84532\",\"success\":false}"

merchantSettlementObservedAt
string | null
required

When on-chain reconciliation OBSERVED that the merchant was really paid for this call — the money really left the paying wallet for the merchant. Reconciliation records it on every rail that settles on a chain: an EIP-3009 exact authorization (x402, and an MPP evm charge) once its nonce is consumed, an MPP-tempo charge once its transfer is found, and an MPP-tempo session call once its channel closes having captured it. On the per-call rails (x402, MPP evm, MPP-tempo charge) it is null on the ordinary path: a payment that settled cleanly is anchored by txHash and never needs this. A session call is the exception: its money moves only when the channel closes, so every call the close captured carries it, Settled ones included. A null is NOT, on its own, proof you were not charged: it stays null until reconciliation reaches a verdict, it is always null on the MPP-stripe card rail, which has no on-chain leg to observe, and on the other rails reconciliation can stop on a payment whose on-chain outcome it could not determine, leaving this null. Read it together with status: status is what you GOT, this is what you PAID — status: Failed/Issued with this set means the merchant took the money and delivered nothing, which these rails cannot prevent (the merchant collects the payment itself, so it can always collect and then error). A non-null txHash on such a row does not mean the payment succeeded.

Example:

"2026-09-08T10:12:00.000Z"

paymentId
string
required

Alias of id, named explicitly for requestId reconciliation clients.

Example:

"b1f9c2e4-8a3d-4f27-9c6b-5d2e17a04f8b"

chargedMicros
string | null
required

Exact amount this payment still contributes to the delegation cap, in micros (1/10,000 of a cent). A merchant or fee share that was proven uncollected and released is excluded. null on legacy rows that predate exact micro-reserve columns.

Example:

"1020000"

resultUrl
string
required

Relative URL of the retained paid result. It may answer Pending while the call is running, or 404 after retention expires, for a mode-A payment, for an unknown payment, or for a payment owned by another caller. A 404 is not delivery evidence; use deliveryStatus.

Example:

"/api/v1/router/payments/b1f9c2e4-8a3d-4f27-9c6b-5d2e17a04f8b/result"

fundingSource
enum<string>
required

What paid for this payment: delegation (your delegation cap) or subscription (your Nevermined Subscription credits). On a subscription row Nevermined paid the merchant: delegationId is null, buyer is Nevermined's treasury, the fee fields are zero (feeStatus None) and chargedMicros is "0"; what it cost you is creditsCharged / creditsStatus.

Available options:
delegation,
subscription
Example:

"delegation"

creditsCharged
integer | null
required

The rate, in credits, of a subscription-funded payment — kept on the row when its credits are refunded, so it counts against your allowance only when creditsStatus is Committed. Null on a delegation payment.

Example:

null

creditsStatus
enum<string> | null
required

Where a subscription-funded payment’s credits stand: Committed (delivered), Reserved (still running, undelivered and marked for refund, or still being decided) or Refunded. Null on a delegation payment.

Available options:
Reserved,
Committed,
Refunded,
null
Example:

null

buyer
string
required

The buyer identity that funded the payment: the on-chain payer EOA (0x…) for the crypto rails (x402 / MPP evm / MPP-tempo), or the Stripe customer id (cus_…) for the MPP-stripe / SPT card rail.

Example:

"0x8D6A5233..."

asset
string | null

The settlement asset AS PERSISTED AT MINT, which differs per rail: a symbol (USDC/EURC) for x402 and for an MPP evm charge, the ERC-20 contract ADDRESS from the challenge for MPP-tempo, and an ISO currency code for MPP-stripe — so protocol: mpp alone does not tell you which. Prefer assetSymbol/assetDecimals below for display — they normalise all three. Kept as-is for consumers that already parse it.

Example:

"USDC"

assetSymbol
string | null

Ticker to display for asset, resolved from the asset address on this row’s chain — USDC, EURC, USDC.e, pathUSD. null when the asset is not one we recognise there; render the (truncated) asset instead, never a guess.

Example:

"USDC.e"

assetDecimals
number | null

Decimal scale of amount for this asset, so a client never has to assume one. null when the asset is unrecognised — treat amount as raw atomic units rather than defaulting the scale, which would render a wrong NUMBER rather than a wrong label.

Example:

6

txHash
string | null
Example:

"0xfc8af37b..."

requestId
string | null
resourceUrl
string | null
Example:

"https://agent.example/resource"

feeAtomic
string | null

Nevermined’s routing fee for this payment, in the settlement asset’s smallest unit. 0 when no fee applied; null on rows that predate the fee.

Example:

"0"

feeBps
number | null

Fee rate applied, in basis points over 10,000. null on rows that predate the fee.

Example:

0

feeCents
string | null

Cents the fee added to the delegation-cap reserve. Note amount on this record is the MERCHANT leg in atomic units, so the combined cap charge is not derivable from this resource alone — it is recorded as amountCents on GET /delegation/{delegationId}/transactions, where that same row breaks it out as feeCents / feeAtomic / feeBps, with feeReleased marking a fee already refunded to the cap.

Example:

"0"

feeStatus
enum<string> | null

Fee lifecycle, independent of the payment status.

Available options:
None,
Accrued,
Submitted,
Settled,
Failed,
Released,
null
Example:

"None"

feeTxHash
string | null

Settlement reference for the FEE leg — distinct from txHash, which is the MERCHANT leg’s. The two legs are independent movements that settle separately, so reconcile them separately. Presence does NOT mean the fee settled — check feeStatus for that. On the x402 rail — which here includes an MPP evm charge, whose fee leg is an x402 EIP-3009 fee authorization exactly as on x402 — it is normally null: Nevermined relays that leg itself as an ERC-4337 UserOp, whose artifact is a userOpHash rather than a transaction hash — a different kind of reference that resolves on no block explorer — and the reconciliation that resolves the fee reads the authorization nonce on-chain, which yields a boolean and no transaction. Only a leg settled through the facilitator instead (the fallback where Nevermined cannot relay on that chain) carries a value, reported verbatim by the facilitator (third-party text, not validated to a 0x shape) once the fee settles. On MPP-tempo it is the hash of the fee transaction Nevermined broadcasts, recorded when the transaction is SUBMITTED rather than when it is mined — so it is present while feeStatus is still Submitted, and it remains present on rows that end Failed or Released (the transaction was refused, reverted, or expired unmined). null when no fee applied, or before a fee leg is submitted. Do NOT poll this field to learn whether an x402 fee settled: read feeStatus.

Example:

"0x9c4d6f1e..."

feeNonce
string | null

EIP-3009 nonce of the fee leg, recorded when the leg is submitted. x402 rail only — which includes an MPP evm charge, whose fee leg is an x402 EIP-3009 fee authorization exactly as on x402. On that rail it is the key that ties an on-chain transfer back to this payment: authorizationState(buyer, feeNonce) answers definitively whether the leg was consumed, which is how a Submitted fee is resolved. null until the leg is submitted, and always null on MPP-tempo, whose fee leg is a native transaction with no EIP-3009 nonce — there the reconciliation key is feeTxHash instead. Not spendable on its own — the signed authorization is deliberately never stored.

Example:

"0x7b1e2c..."