Signed verification verdict

OpenTrust Verify (OTV) checks an incoming transfer and returns a signed verdict on whether the named recipient can spend what arrived.

That sentence is the product. A chain event can be observed without being a payment. A payment can be included without being spendable. The signed verification verdict is the record that says which of those is true for one claim.

What the API returns

POST /v1/verify/incoming accepts chain, network, transactionHash, and recipient. An asset and an expected amount are optional. The response schema id is otv.verdict.v1. Evidence is required. The status is one of OBSERVED, PENDING, EXECUTED, ASSET_CONFIRMED, BALANCE_CONFIRMED, FINAL, SPENDABLE, REJECTED, SUSPICIOUS, or UNVERIFIED.

Evidence the verdict carries

Blockchain transaction evidence stays itemized. The evidence types are TRANSACTION_INCLUDED, EXECUTION_SUCCESS, ASSET_MATCH, RECIPIENT_MATCH, AMOUNT_MATCH, BALANCE_DELTA, FINALITY, and SPENDABILITY. Each item has a boolean result. A true inclusion check is not execution, a transfer, a balance increase, finality, or spendable funds.

Who consumes it

Applications, merchants, and payment systems call the same HTTPS API. They can wait for the signed verdict before treating funds as spendable, or receive an HMAC-signed webhook when a verification is final, failed, or suspicious. OTV does not custody assets, accept a seed or private key, or broadcast the payment.

The entity

OpenTrust Verify is the product. OTV is its short name. Crypto payment verification is the category. Incoming cryptocurrency payments are the claims. Blockchain transaction evidence is what the chain adapters collect. The signed verification verdict is the result those callers can check.

Related

Scan a transaction · Look up a verdict · Explore documentation · Download the Android app