PulseExploreJournal ClubDebatesTrendingResearchersJournals
Instagram
HomeExploreJournal ClubTrending
Synapse
⌘+K
Synapse
February 8, 20260 citationsOpen Access

Execution-Time Chargeback Finality and Network Liability Determination Using Cryptographically Bound Evidence

View Full Paper
TGTony GiulianoCenterforce

Key Points

  • The research aims to define how execution-time evidence can be used to determine liability in card payment transactions.
  • Defines a framework for cryptographically verifiable evidence artifacts.
  • Specifies binding of execution-time evidence to payment authorization data.
  • Establishes clear acceptance criteria for transaction finality and liability allocation.
  • Absence of valid acceptance tokens indicates evidentiary insufficiency.
  • Any changes to token-based finality need explicit logging and auditing.
  • Specializes existing evidence mechanisms for improved chargeback resolution.

Abstract

This technical specification defines a domain-adapted application of Execution-Time Evidence Objects (ETEOs) to card payment authorization, settlement, and chargeback liability determination.The specification assumes the existence of an underlying execution-time evidence framework that generates cryptographically verifiable, non-repudiable evidence artifacts contemporaneous with transaction authorization. These artifacts are bound to pre-defined acceptance criteria and preserved with a verifiable chain of custody.This document specifies how execution-time evidence and acceptance tokens are cryptographically bound to payment network authorization data, settlement identifiers, and related transaction metadata to deterministically establish transaction finality and allocate network liability at execution time.Under this specification, absence of a valid execution-time acceptance token constitutes evidentiary insufficiency and cannot be cured through reconstructed logs, affidavits, screenshots, probabilistic risk scoring, post-hoc interpretation of cardholder intent, or subsequent merchant reclassification.Any rejection, reversal, or deviation from token-based finality requires an explicit, constrained override event that is immutably logged and independently auditable.This specification does not redefine evidence creation, chain-of-custody, or authority gating mechanisms, but instead specializes those primitives for card payment networks by binding execution-time evidence directly to chargeback eligibility, dispute resolution, and network liability determination.

Ask AI
Helpful
Bookmark
Share
View Full Paper

Cite This Study

Tony Giuliano (2026) studied this question.

synapsesocial.com/papers/698829520fc35cd7a884995ahttps://doi.org/10.5281/zenodo.18509158
Ask AI
Helpful
Bookmark
Share
View Full Paper