Reconcile a seller payment after a timeout
Inspect the original payment without resubmitting or claiming that a missing response was recovered.
Inspect the original seller payment
Use this when the reference Base buyer submitted a seller payment but did not retain the response. For a lost 402Signal checking response, use routing recovery instead.
The reference buyer requires Node 24 and private POSIX/SQLite storage. Preserve the original configuration, journal and job ID. Read-only reconciliation does not load the signing account or submit another payment.
cd integration/reference-buyer
npm ci --ignore-scripts
REFERENCE_BUYER_ACK=base-exact-only-once node operator.mjs confirm-seller /private/config.json ORIGINAL_JOB_IDThe path and job ID refer to your existing campaign. This command is not a new-job tutorial. An optional existing transaction hash can be supplied as the final argument. Do not invent a new ID or replace the journal.
A confirmed payment with no retained response means payment confirmed; response not retained. It does not recover the answer, prove useful output or issue a refund. While the job is unresolved, repeat submission and new jobs in that campaign remain blocked. Read the resulting journal status before any further action; confirmation is not permission to rerun the job.
The current reference seller request times out after 20 seconds. Read-only confirmation makes at most six observations within 15 seconds. HTTP timeout, payment-authorization validity and observation expiry are separate clocks. maxTimeoutSeconds is not a guaranteed response-delivery deadline.
Reconciliation itself creates no new payment authorization. Prior checking fees, seller payments and held reservations remain subject to their recorded outcomes. Independent wallet calls or replacing the campaign store bypass this workflow and are outside its protection.