|
Createful
|
March 22, 2018 at 7:14 am
I’m getting a 4020 SagePay error that’s complaining about the uniqueness of transaction IDs generated from Event Espresso.
Is there any way I can add a unique prefix to the transaction IDs? Like the year, or a company code? Or perhaps begin the numbering again from a much higher number with more digits?
Thanks
|
|
Josh
|
March 22, 2018 at 7:26 am
Hi there,
A 4020 error from SagePay actually means the server’s IP address doesn’t match the IP address set in your SagePay account. Here are the instructions from SagePay that show how to fix:
https://www.sagepay.co.uk/support/error-codes?keyword=4020
|
|
Createful
|
March 22, 2018 at 7:36 am
Sorry – my bad! I’ve had so many codes I got them mixed up! The correct code should be 4042 and it reads:
The VendorTxCode has been used before for another transaction. All VendorTxCodes must be unique.
Thanks
|
|
Josh
|
March 22, 2018 at 8:17 am
The VendorTxCode value already has a unique prefix, so I’m not sure if adding more prefixes would help in this case.
If you were testing transactions on a dev server, then it’s possible the live server could have the same prefix from a transaction from the dev server. That said, the VendorTxCode would still be unique because a timestamp generated suffix gets appended to the field.
You can check what’s actually being sent as the VendorTxCode by going to Event Espresso > Payment Methods > Logs. Each transaction sent to Sagepay will have at least 3 log items and at least one of them will include the VendorTxCode value. Are there actually duplicates logged there?
|
|
Createful
|
March 22, 2018 at 9:34 am
Yes, looking in the logs I can see several duplicate transactions:
|
|
Createful
|
March 22, 2018 at 9:34 am
Can you see this link: https://imgur.com/a/wWPkv
|
|
Josh
|
March 22, 2018 at 9:42 am
Those are not duplicate transactions. Each transaction has many log items because there are more than one API call per transaction. If you check each log entry for a given Transaction you’ll see each API call has unique data.
|
|
Createful
|
March 23, 2018 at 2:30 am
So I think I know why it was triggering the VendorTxCode error – whenever I try to make a booking, I get the red “because of a technical error” message. So I refreshed the page and tried the same booking again. This triggered the TxCode error.
I just tried another booking, got the red technical error, but instead of refreshing I went back to start the booking again from scratch.
From the logs I can see the transactions are being added with unique txn codes, but nothing’s going through – Im just seeing the red technical error message.
Thanks
|
|
Josh
|
March 23, 2018 at 2:08 pm
Usually if you’re seeing the “A valid payment method could not be determined due to a technical issue” it’s because the gateway is set to “Debug Mode On”, but the gateway is using live account credentials. Do you have Debug Mode On to Yes or No, and which type of credentials are being used?
|
