Skip to content
PromiseTrace

How PromiseTrace works, and what it does not do

Who it is for

An independent digital-service seller (for example a designer in India) and an overseas client who agree a specific piece of work over chat or email and pay through PayPal. Misunderstandings usually come from what was said in passing: which file formats, how many concepts, which timezone the deadline uses.

What each part relies on

  • AI (Claude, via the Anthropic API) proposes the structured brief and clarification questions. It must quote the source for every value; our code checks that the quote exists and mentions that value, or the value stays unknown. AI never decides whether a delivery is acceptable.
  • Deterministic code checks money arithmetic, PayPal status and reconciliation fields, file types (from file contents), counts, the deadline in the agreed timezone, and revision counts.
  • People approve the brief (both sides, same version) and decide whether the work is satisfactory. A download is never treated as acceptance.
  • PayPal is the source of truth for payment. At checkout PayPal places a hold (authorization) for the approved price; the agreement counts as funded only when PayPal returns it as CREATED with the expected amount. PayPal holds the payment at checkout. It is captured when the buyer accepts the delivery, or by the seller after a 5-day review period if code finds every agreed item met, nothing is flagged, no objection is open and nothing needs the buyer's confirmation. The seller can cancel and release the hold; the buyer can release it if the deadline passes with nothing delivered. A payment is shown as paid only when PayPal returns a COMPLETED capture with the expected amount and identifiers. A hold lasts up to 29 days. PayPal capture is most likely to succeed within the first three days of authorization. The 5-day review period puts any seller capture after that window, so it can fail; PromiseTrace records a failed capture instead of hiding it. Prompt buyer acceptance is the most reliable path. Reauthorization is not built.

Limits

  • PromiseTrace never holds funds itself: a payment hold is a PayPal authorization on the buyer's payment method, captured or released through PayPal's API. It does not lift PayPal account holds on a seller's balance, decide PayPal claims or guarantee Seller Protection. PayPal India's Seller Protection does not cover "Significantly Not as Described" claims; a record here does not change that.
  • Complaints recorded here are messages between the two parties, not PayPal disputes. Official PayPal dispute notifications, when received by verified webhook, are labelled as such.
  • File hashes show whether a file changed later. They do not show that the work is good or that it fulfils the brief.
  • This build uses the PayPal sandbox and ordinary single-merchant Checkout: payments go to the one merchant account configured on the server. A product for many sellers would need PayPal's partner (platform) onboarding.
  • Indian sellers can only receive international (not domestic INR) payments through PayPal, and need PAN verification, a bank account and a purpose code. A sandbox success says nothing about production eligibility.
  • Sources are pasted text. PDF import, other languages and scope-change suggestions are not built.

Data handling

Sources, versions, files and history are stored in the app database and visible only to the two participants. Exports omit email addresses and PayPal payer IDs. The seller can delete an agreement and its files at any time; this does not affect PayPal's records. Demo data in this project is fictional.