Hello,
This is randomly happening for some of the transaction, starting since yesterday, May5 2023:
We use cloverConnector.sale(...), up until couple days ago, the saleResponse object in onSaleResponse event we receive always consistently a sale. But now it's randomly sale or auth.
What do we suppose to handle if receiving an auth in sale response like that?
Thanks,
-Hung
Hello,
If you are receiving an "Auth" response instead of a "Sale" response in the onSaleResponse event when using cloverConnector.sale(...), it indicates that the transaction has been authorized but not settled yet. This can happen when the payment processor approves the transaction but delays the settlement process.
To handle this scenario, you can consider the following steps:
Check the PaymentResponse object received in the onSaleResponse event. Look for the result field or a similar field that indicates the status of the transaction.
If the result field is set to "Auth" instead of "Sale," it means the transaction is authorized but not settled.
Decide on the appropriate action based on your business logic and requirements. You can choose to wait for the settlement to occur or take additional steps to ensure the transaction is completed.
If you decide to wait for the settlement, you can periodically check the status of the transaction using the provided transaction ID or other relevant identifier. This allows you to determine when the transaction has been settled and completed. H‑E‑B Partner Services
If you require immediate payment confirmation, you might consider capturing the authorized amount manually using the cloverConnector.capturePreAuth(...) method. This action will initiate the settlement process and convert the authorization into a completed sale. Keep in mind that the capturePreAuth(...) method may not be available in all payment processor integrations, so consult the documentation or contact the payment processor for guidance.
6 People are following this question.
