Payment, delivery and discovery source are separate records
Guides
A blockchain settlement can confirm payment, while service logs confirm delivery and separate attribution evidence explains how a buyer found the service.
A payment record answers a narrow question: did value move under the stated network, asset, amount and recipient? It does not identify the purchased result by itself, prove that the result was delivered or reveal which marketplace led the buyer to the service.
Bind the payment to the service request with a stable purchase reference and request fingerprint. Store the selected route, normalized input, payment requirement and settlement response together. If that binding is absent, label the route assignment unknown instead of reconstructing it from price alone.
Delivery needs separate evidence. Record whether execution started, whether an upstream provider accepted the task, whether a result was stored and whether the buyer received or retrieved it. A successful settlement with a missing result remains an unresolved paid request.
Acquisition source is a third record. An explicit campaign or referral identifier carried into the request can support attribution. A directory listing, user agent or referrer is only a signal unless it is bound to the purchase. The existence of a marketplace entry does not prove that the marketplace generated a sale.
Collect only the technical fields needed for the decision and publish aggregate conclusions. Avoid turning wallet addresses or raw request data into marketing profiles. Keep the time window, method and unknown share visible so that later reports remain comparable.
A useful report therefore shows settlement, delivery and discovery attribution in separate columns. Reconcile the original purchase before retrying an unclear request, and preserve the evidence without sending private keys or seed phrases to support.