arcus.
THE PROPOSED FIRST PRODUCT

What is verified arrival?

Verified arrival evaluates whether an authorized arrival claim satisfies a defined place, time window, and evidence threshold. Arcus's proposed Verified Arrival / Proof-of-Presence API would return a graded result, reasons, and privacy-minimized audit references to an approved partner. The API is in development; public production access and self-service enrollment are not currently offered.

How is it different from a check-in?

A check-in records an assertion or observation. Verification evaluates whether that evidence meets the program's rules. An illustrative venue program might compare an authorized partner check-in and permissioned location observation with an eligibility window. The sources, freshness, and limitations matter as much as the event label.

Three different jobs in an arrival workflow
LayerQuestion it answers
Check-in evidenceWhat observation or assertion was recorded?
Verification decisionDoes this claim meet the named program policy?
Outcome recordWhat result and authorized next step should be retained?

What would a partner submit and receive?

The proposed first product would accept an authorized claim and supporting evidence from an approved partner. It would evaluate the claim under the applicable policy and return a graded decision with reason codes and privacy-minimized audit references. Evidence submission, portable proof, policy administration, and reporting form a proposed expansion path; they are not promises of features available today.

What happens when arrival cannot be corroborated?

Incomplete evidence should not become a verified arrival by default. Conflicting observations may require review. A pilot needs to define evidence sufficiency, uncertainty, escalation, and correction, together with which downstream actions each result permits. The homepage explorer illustrates these distinctions with examples rather than customer data.

What should a pilot establish first?

  • The qualifying location, time window, participant, and program purpose.
  • Permission to obtain and use each evidence source for that purpose.
  • The policy version, evidence threshold, exceptions, and review owner.
  • The result the receiving system needs, with minimum necessary disclosure.
  • Retention, correction, and operational acceptance criteria.

Does arrival verification require an incentive?

Arcus can support verification-only workflows and programs that attach rewards to qualifying arrivals. In a rewards program, the policy defines eligibility, campaign capacity, and the authorized reward; the record connects that issuance to the verified action. Linked to an intervention and suitable measurement, verified arrivals can also support evidence of improved participation and cost per outcome.