SagePay orders downloading into “Pending payment service provider” with an error
If you are using SagePay as a PSP, and finding that every order you download appears on the "Pending payment service provider" tab in SellerDeck, and the error below occurs when you download orders, please make the following checks:
"An error occurred while reading a Payment Service Provider Authorisation. The file may have been corrupted in transfer from the server. Abort will cancel the download operation and leave the unprocessed PSP files on the
web. Retry will try to transfer the file again. If you choose to ignore this error, the PSP file will be lost. If you ignore this error, the associated order *****************, will be modified to have a payment method of "Send Credit Card Details Separately" and a status of "Waiting for CC Details."
Solutions:
1) The first thing to do is ask SagePay to reset and send you a new Encryption key and Password and ask them to email those details to you. Then copy and paste these details into Settings | Business Settings | Payment and security | Configure method. Then go to Web | Refresh website.
2) In SellerDeck, go to Web | Network setup. Click the test button. If the network settings test fails, this may be the cause of the problem. First make a backup of your current network settings Web | Network setup | Export and keep these safe. Then click the "Wizard" button and run the network settings wizard to see if your new network settings pass. If the network settings still fail, revert back to your backed up settings.
3) Request an error log from your server host. Compare the error log with your orders in SellerDeck and find what error occurs at the time of an order being placed being placed. If you see the following error "mod_security: Access denied with code 406", mod_security has possibly been misconfigured on your server, resulting in the PSP authorization callbacks being blocked. mod_security rejects packages with zero bytes in. With a proper configuration, this can be fixed by your server host. Please contact your server host and ask them to fix this problem.
If you are using SagePay as a PSP, and finding that every order you download appears on the "Pending payment service provider" tab in SellerDeck, and the error below occurs when you download orders, please make the following checks:
"An error occurred while reading a Payment Service Provider Authorisation. The file may have been corrupted in transfer from the server. Abort will cancel the download operation and leave the unprocessed PSP files on the
web. Retry will try to transfer the file again. If you choose to ignore this error, the PSP file will be lost. If you ignore this error, the associated order *****************, will be modified to have a payment method of "Send Credit Card Details Separately" and a status of "Waiting for CC Details."
Solutions:
1) The first thing to do is ask SagePay to reset and send you a new Encryption key and Password and ask them to email those details to you. Then copy and paste these details into Settings | Business Settings | Payment and security | Configure method. Then go to Web | Refresh website.
2) In SellerDeck, go to Web | Network setup. Click the test button. If the network settings test fails, this may be the cause of the problem. First make a backup of your current network settings Web | Network setup | Export and keep these safe. Then click the "Wizard" button and run the network settings wizard to see if your new network settings pass. If the network settings still fail, revert back to your backed up settings.
3) Request an error log from your server host. Compare the error log with your orders in SellerDeck and find what error occurs at the time of an order being placed being placed. If you see the following error "mod_security: Access denied with code 406", mod_security has possibly been misconfigured on your server, resulting in the PSP authorization callbacks being blocked. mod_security rejects packages with zero bytes in. With a proper configuration, this can be fixed by your server host. Please contact your server host and ask them to fix this problem.