Learn
What is destination verification?
Destination verification means your product backend — not Operator self-report — confirms that a defined outcome happened. BTheHype typically receives a server-to-server postback or track event, links it to the execution, and only then settles HYPEIT. Screenshots and bio checks are not canonical proof.
Last updated:
The confirmation path
After an Operator completes the required action, your destination system confirms the outcome — for example via POST webhook or track event with an idempotency key. BTheHype authenticates the signal, links it to the execution, and advances verification state.
What does not count
Screenshots, social bio checks, and self-attested completion are not canonical destination proof. Social amplification signals may exist as optional context, but they do not unlock HYPEIT settlement on their own.
Developer control
You define the desired human outcome and verification rules in a Growth Program. Your backend remains the source of truth for whether that outcome occurred in your product environment.
Settlement
Only after verification passes does HYPEIT settle to the Operator. That keeps developer escrow tied to confirmed outcomes and keeps Operator earnings aligned with real destination success.