HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network

Explorer & evidence

How do we connect a business payment to its transaction and proof?

3 min read

Preserve the references supplied by each part of the workflow so the business record can be traced to its payment, wallet context, and available settlement evidence. This helps explain the outcome without conflating different identifiers.

Preserve the chain of references

Start with the identifier your business uses, such as an order or payment request. Keep the returned provider and Hybrid-Chain references beside it, together with the network and asset context. Where an external transaction is published, retain that reference as a separate field. The goal is a traceable relationship, not one identifier reused everywhere. This lets support move from a customer’s question to the relevant technical evidence without asking the customer to understand every system involved.

Connect outcomes, not just hyperlinks

A useful support view explains what each linked record establishes: a request was accepted, a transfer was observed, a balance became available, or delivery completed. The exact stages depend on the integration. Do not label the business process complete merely because one associated API request returned successfully. Check the authoritative result for the stage that matters to the customer and show unresolved dependencies explicitly rather than hiding them behind a generic success badge.

Verify the mapping with a controlled case

Follow a representative request from beginning to end and ask a second person to reconstruct it from the saved references. Include an exception, such as a delayed response or missing external reference. Note which information is private and which may be shared publicly. The resulting reference map should match the actual response fields of your integration, not a guessed universal schema. Keep it with the operating procedure so finance, engineering, and support use the same names for the same records.

Illustrative example

A support view links a payment reference to the returned Hybrid record and, where published, its external-chain transaction.

In plain language

Why several reference numbers can describe one journey

A business request, a payment-provider record, a Hybrid-Chain event, and an external blockchain transaction can each have their own identifier. These are not competing names for the same database row. They identify different parts of a journey, just as an order number and a parcel tracking number describe related but different records. Keep the relationship between them rather than overwriting one with another. A hash is a compact cryptographic fingerprint used to identify or commit to data; a UUID is another kind of record identifier. Neither should be interpreted from its appearance alone. Use the label beside it and the system that issued it. When asking for help, include the network and the type of reference as well as the value. This makes it much easier to distinguish a missing link from a failed operation and avoids searching an external chain for an internal reference.

In plain language

A public record is evidence with a specific scope

An Explorer record is closer to a receipt or an entry in a logbook than to a live control panel. It describes something published about a particular event, object, or process. Some entries include links that let you examine the earlier steps or the underlying transaction. A record can remain useful after it becomes old: it may establish what was recorded at that time. It does not necessarily describe what the system can do now. Look at the record type, network, time, source, and stated verification result together. Missing information means the public view cannot establish that fact; it is not a reason to invent a positive or negative result. Private account records may contain additional context that is deliberately absent from Explorer. This is why a screenshot is a starting point for investigation, while the exact record and its supporting references are much more useful for reaching a conclusion.

Conditions & limitations

Do not assume every provider or operation publishes the same fields. A Hybrid hash is not a substitute for a base-layer transaction hash.

What to do next

Define the reference mapping from the exact API responses and verify it with a controlled end-to-end case.

Payments & Commerce ↗Transaction Explorer ↗