Resolve mismatched Toss payment results
Collect the store, customer, time, amount, terminal transaction identifier, and Laney purchase ID.
After this taskThe same transaction is recorded without another charge, or explicitly handed over as unresolved.
Starting conditions and inputs
Keep the original transaction identifiers; do not start another charge.
Values for this task
entry_url, merchant_id, transaction_id, purchase_id, amount, transaction_url
Command sequence
open "$entry_url" && snapshot -i
get text body
open "$transaction_url" && snapshot -i
get text body
# Outside browser: After confirming the original outcome, the recovery operator handles that reception. Do not request another payment while the result is unknown.
snapshot -i
reload && snapshot -i
get text bodyRef targets and expected results
| # | Command / ref | Target and verification |
|---|---|---|
| 1 | get text | Read the original reception ID, transaction ID and outcome. |
| 2 | open | Toss confirmation for the same transaction |
| 3 | get text | Compare approved, cancelled or unresolved state and amount. |
| 4 | Outside browser | After confirming the original outcome, the recovery operator handles that reception. Do not request another payment while the result is unknown. |
| 5 | reload | Reload the same reception record. |
| 6 | get text | Compare the original reception and transaction with the recovered purchase. |
Check the result
The same transaction is recorded without another charge, or explicitly handed over as unresolved.
Resuming after interruption
Check the original request ID and outcome first. Do not resubmit while its result remains unknown.
Identify the transaction
Collect the store, customer, time, amount, terminal transaction identifier, and Laney purchase ID. Distinguish nearby transactions. Confirm that the transaction originated in the plugin.
Compare approval and storage
Check the original approval result at the terminal or provider. Compare it with the Laney purchase amount and status. A stalled screen does not prove payment failure. Distinguish approved, rejected, and unknown results.
Recover without duplicating payment
If approval exists but storage is missing, do not charge the same amount again. Give the transaction identifiers to your connection contact for reconciliation. Retry only after checking the original state and duplicate prevention.
Check cancellation limits
Changing a purchase to voided does not execute a card refund. Confirm refunds and partial cancellations at the provider, then reconcile records. Do not assume every terminal cancellation is synchronized automatically.