A support agent refunds $24 for a damaged item. The payment provider receives the request, but the connection drops before the console gets a receipt. The customer is still on the phone. An empty refund field tells the agent what the console knows. It says nothing about whether $24 has already moved.
The most valuable line in the integration brief is the one that describes what the agent sees at this moment. Give the attempt a durable reference, show the amount and currency, and offer a way to check its status. A fresh refund button leaves the hardest decision with the person who has the least evidence.
One customer decision can produce several network attempts
Consider a hypothetical $80 order with two damaged items. The agent first approves $24 for one item. That decision gets its own reference before the integration contacts the provider. If the response disappears, the console retains the reference and marks the outcome as unknown. A second agent opening the order sees the same pending attempt.
Some providers let a client resubmit the same operation under an idempotency key. The word describes a specific promise about repeated requests. Check which endpoint makes that promise, how long the provider retains the key, what happens if parameters change, and which errors it remembers. Stripe's API v1, for example, can return the stored result of an executed request, including a server error. Repeating a request can therefore reproduce the uncertainty. Stripe idempotent requests
Compare all three actions
Scroll horizontally to read the table.
| What support knows | Action to make available |
|---|---|
| The provider confirms the original $24 refund | Attach its receipt to the existing attempt and update the order. |
| No conclusive result, but the provider still guarantees a same-key retry for this exact request | Let the integration retry with the stored key and unchanged parameters. Keep the agent on the same attempt. |
| The retry guarantee has expired, or the provider has no matching lookup | Send the reference, amount, timestamp and order ID to the person who reconciles payments. Hold further action on this amount. |
A second $24 refund can be legitimate
Suppose the customer reports the other damaged item the following week. That is a new decision, even if the amount is identical. Using only the order number and amount as a deduplication key could silently suppress it. Link the second decision to the other item and give it a new operation reference. Check the remaining refundable balance, including unresolved attempts, before authorizing it.
For acceptance testing, ask the implementation partner to demonstrate a lost response, two agents clicking at once, and a later legitimate refund. Compare the support timeline with the provider's refund ledger. The first two tests should yield a single financial effect for the original decision. The third should produce a second receipt with its own reason. Those three records give support, engineering and finance something concrete to sign off together. Explore klaps software engineering services