Verify transaction status
Find out the result of a payment when the response was lost, so you never charge twice.
If your ECR didn't get a response to a payment, the payment may still have been approved. Check its status before you try again, so the customer is never charged twice.
Requirements
| Requirement | Description |
|---|---|
| Integration | Local integration or Cloud integration |
| Before you start | Your ECR is connected and logged in. See Connect your ECR |
| Message | TransactionStatus |
How it works
If the connection breaks after you sent a request but before you got the response (ECR power failure, terminal power failure or a network problem), the result is unknown. It may have been approved.
- Reconnect if needed.
- Send TransactionStatus to get the result of the transaction.
- Only if it didn't go through, try again.
- TransactionStatus works only for payments (
MessageCategory=Payment). Leave outServiceIDto get the latest payment. To check a payment sent by another ECR, add itsSaleID. - If the response has no
RepeatedMessageResponse, the payment isn't finished yet. Don't treat it as failed, and don't start a new payment. Send TransactionStatus again. - The cashier can also check on the terminal. See Check the last transaction.
See the example request on TransactionStatus.
Testing
Break the connection during a payment: pull the network cable, or switch off the ECR or the terminal. After reconnecting, the ECR finds the result with TransactionStatus before it tries again. See Test and get approved.
Updated 14 days ago
Did this page help you?