Reconcile purchase status with payment

Starting conditions and inputs

Have real transaction evidence for the purchase status.

Values for this task

entry_url, purchase_id, provider_transaction_id, expected_status, transaction_url

Command sequence

open "$entry_url" && snapshot -i

click "$purchase_row" && snapshot -i

get text body

open "$transaction_url" && snapshot -i

get text body

Ref targets and expected results

#	Command / ref	Target and verification
1	`click` `$purchase_row`	Purchase record to inspect
2	`get text`	Read purchase ID, amount and current payment state.
3	`open`	Original transaction confirmation for this purchase
4	`get text`	Compare purchase and transaction IDs, approved amount and cancelled amount.

Check the result

Purchase state matches the source; changing a status is not itself a refund.

Resuming after interruption

Read the same source IDs again. Check organization and time range before treating an empty result as missing data.

Read purchase state

State	Meaning
`pending`	Requested or awaiting payment
`completed`	Recorded as completed
`voided`	Recorded as cancelled or void

These are stored states. Reconcile them with payment evidence before treating money as received.

Compare provider transaction ID, approval time, amount, and currency with the purchase. Use the organization’s evidence for in-person collection. Investigate mismatches before repeatedly changing completion state.

Separate voiding and refunds

Voiding a purchase does not request a card refund or partial cancellation. Verify actual refunds with the provider. Confirm support for external advertising-conversion adjustments separately.

Check connected records

Check that customer, reservation, and purchase identify the same transaction. Reservation completion and payment completion are independent. If using conversion tracking, reconcile the completed source with delivery evidence.