List Payments
Returns your Router payments (newest first, capped at 1000) across every agent and delegation —
the unified audit trail. Filter by delegationId and by from/to (ISO-8601, inclusive on
createdAt). format=csv returns a CSV file download instead of the JSON array.
Authorizations
Your Nevermined API Key (starts with 'nvm:'). Get one at nevermined.app under Settings > API Keys.
Query Parameters
Only payments spent against this delegation id.
ISO-8601 lower bound on createdAt (inclusive).
"2026-07-01T00:00:00Z"
ISO-8601 upper bound on createdAt (inclusive).
"2026-07-31T23:59:59Z"
Response format. Defaults to JSON; csv returns a downloadable file.
json, csv Response
The payment record — a JSON array (or a CSV file when format=csv).
"b1f9c2e4-3d5a-4c7e-9f21-6a8b0c4d2e13"
"2026-07-01T09:00:55.605Z"
Issued, Settled, Failed "Settled"
"x402"
"base-sepolia"
Amount in the asset’s smallest unit.
"1000"
The merchant's pay-to identifier: a 0x address for the crypto rails (x402 / MPP-tempo), or the seller's Stripe network business profile id (profile_…) for the MPP-stripe / SPT card rail.
"0x209693Bc6afc0C5328bA36FaF03C514EF312287C"
"5e7481c3-..."
The buyer identity that funded the payment: the on-chain payer EOA (0x…) for the crypto rails (x402 / MPP-tempo), or the Stripe customer id (cus_…) for the MPP-stripe / SPT card rail.
"0x8D6A5233..."
The settlement asset AS PERSISTED AT MINT, which differs per rail: a symbol for x402 (USDC/EURC), the ERC-20 contract ADDRESS from the challenge for MPP-tempo, and an ISO currency code for MPP-stripe. Prefer assetSymbol/assetDecimals below for display — they normalise all three. Kept as-is for consumers that already parse it.
"USDC"
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.
"USDC.e"
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.
6
"0xfc8af37b..."
"https://agent.example/resource"
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.
"0"
Fee rate applied, in basis points over 10,000. null on rows that predate the fee.
0
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, with this fee broken out in that row’s providerMetadata.
"0"
Fee lifecycle, independent of the payment status.
None, Accrued, Submitted, Settled, Failed, Released "None"
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. Reported verbatim by the facilitator (third-party text, not validated to a 0x shape). null until the fee actually settles.
"0x9c4d6f1e..."
EIP-3009 nonce of the fee leg, recorded when the leg is submitted. This is the only 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. Not spendable on its own — the signed authorization is deliberately never stored.
"0x7b1e2c..."
Related topics
Payment ledgerList Payment MethodsAPI ReferenceBuilding a Paid AI Agent with OpenClaw and NeverminedX402 Protocol