Problem
When processing a refund (either from the Sales History screen or the Make a Sale screen), the integration fails when attempting to apply the refund to a credit card. The error message shown mentions that the integration is not configured to process blind credits.
Explanation
With credit card refunds, two different types of credits are available: referenced credits, or unreferenced/blind credits (a comparison can be found on our quick reference guide). Some merchant accounts are not permitted to process blind credits - therefore, the Blind Credit Processing option is disabled by default. However, depending on the type of transaction, the integration can detect that it may need to process a blind credit transaction to properly post to QuickBooks - seeing that it can't, it fails, and displays this error.
Solution
Two solutions are available, and should be followed from top-to-bottom.
Enable Blind Credit Processing option
1. Open QuickBooks Point of Sale.
Open QuickBooks Point of Sale. If prompted, sign in as a user with permissions to modify workstation settings and process refunds (if applicable).
2. Open the Processing Options for the integration.
Click on the green I Want To... menu, followed by PT-Settings. This will open the settings window for the integration - when available, click the Processing Options tab at the top of the window.
3. Enable Blind Credit Processing.
Check the box next to Blind Credit Processing. Then, click OK.
4. Reattempt an unreferenced refund.
Try processing an unreferenced refund (for instructions on how to do this, see our guide). The refund should process successfully.
If the above steps did not resolve the issue, try the below solution.
Enable ECC/blind credits on your merchant account
Depending on your gateway, your merchant account may not be configured to allow processing of blind credits (some gateways refer to this ability as Expanded Credit Capabilities, or ECC). To verify that these are enabled on your merchant account, please contact your merchant services provider.
Comments
0 comments
Article is closed for comments.