Trace_Inspector / invoice-created

Invoice creation succeeds

INVOICE CREATED

HTTP 200

Seeded Trace Sequence

invoice-created

AUTHENTICATIONSUCCESS

API key and scope accepted

The request carries a valid `spnd_` key with `invoices:write`.

VALIDATIONSUCCESS

Amount and asset validated

The handler accepts integer-like numeric input and a required asset symbol.

FIBER_GATESUCCESS

Fiber invoice created

The gateway calls the owned Fiber testnet node instead of a mock adapter.

PERSISTENCESUCCESS

Invoice and audit row persisted

The invoice is stored under the authenticated tenant and the action is recorded.

RESULT_PAYLOAD

{
  "id": "inv_2f0d8f",
  "paymentHash": "0x8f12...",
  "recipientAddress": "fibt1q...",
  "amount": "50",
  "assetSymbol": "USDT",
  "status": "PENDING"
}

Technical Summary

Tenant Context

sandbox-merchant

Auth Scopes

invoices:write

Demonstrates

- Invoice creation is a real backend route.

- Fiber integration and persistence are part of the same flow.

- The response shape matches the current handler, not a fake SDK surface.

REQUEST_BODY

POST /api/v1/invoices

{
  "amount": "50",
  "assetSymbol": "USDT",
  "description": "Agent payout",
  "externalReference": "ord_1001"
}

RESPONSE_BODY

Status 200

{
  "id": "inv_2f0d8f",
  "paymentHash": "0x8f12...",
  "recipientAddress": "fibt1q...",
  "amount": "50",
  "assetSymbol": "USDT",
  "status": "PENDING"
}

Submission Boundary Note

Seeded scenario derived from the current invoice-create handler. IDs and payment hashes are illustrative.