- Home
- All APIs
- Worldpay Total
- Transaction issues – EPOS server seems to be down
Transaction issues – EPOS server seems to be down
“EPOS server seems to be down” is shown in the logs.
This may cause the following issues:
Transaction times may take longer than normal.
You may see a higher amount of referred transactions where IPC prompts for voice authorisation.
You may see a higher amount of declines, particularly for Debit Cards and high value transactions.
20-Jun-2016 01:54:03,641 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.processUKTransaction@1819296,,1,Response code received : 01,
20-Jun-2016 01:54:03,641 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.processUKTransaction@1819296,,1,Go to Online,
20-Jun-2016 01:54:03,641 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,CPS Interface : doApproval.,
20-Jun-2016 01:54:03,641 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,Primary URL : https://194.72.158.227/soap/servlet/rpcrouter,
20-Jun-2016 01:54:03,641 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,Connection status currentTimeMillis After ::0,
20-Jun-2016 01:54:03,641 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,Connection status of Primary URL :false,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,secondary URL :
https://80.69.5.198/soap/servlet/rpcrouter,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,Connection status of Secondary URL :false,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.cps.YESEPOSServerConnectorForElavon@1407f5e,,1,EPOS Server seems to be down.,20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.StandInVerifier@13f5f26,,1,Reading Stand-in Action Codes,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.StandInVerifier@13f5f26,,1,Exception in getting Stand In tags null,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.StandInVerifier@13f5f26,,1,Stand In Value for AID A0000000031010 is null,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.StandInVerifier@13f5f26,,1,Stand In Value for AID is null,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.StandInVerifier@13f5f26,,1,Stand-in value is False/Null. Setting transaction result Declined_Offline,
20-Jun-2016 01:54:03,657 [Thread-38] ERROR [TID:22980012] C:\YESEFT/logs - yes.yeseft.services.processUKTransaction@1819296,,1, Inside UKprocessAuthDecision ,
Cause
IPC could not connect to one or both of the URLs for the Worldpay Payments Hub. In some cases, this may be because one or both of the URLs is not responding to IPC connection requests. The URLs in use are shown in the logs above.
Possible scenarios
If IPC can't connect to the primary URL it will try the secondary URL. Depending on the type of fault, IPC will try the primary URL until the configured timeout value expires. By default, this is set at 10 seconds.
If it can't connect, it will try the secondary URL. The net effect will be a delay to every transaction.
If IPC cannot connect to the primary URL or the secondary URL:
- Contactless transactions below the floor limit will be approved offline as normal.
- If there is no stand-in limit configured, contactless transactions above the offline limit, chip and PIN, and Magnetic Stripe Read (MSR will be referred. IPC will ask for the sales operator to enter a voice authorisation code.
- If a stand-in limit is configured, chip and PIN transactions up to the limit will approve offline (if the card allows it)
Contactless, MSR, Keyed, and Chip and PIN transactions which cannot be approved offline (such as Maestro and Electron) are referred for voice authorisation.
Solution
Check the internet connectivity from the IPC host machine to the primary / secondary URLs by using a browser on the computer hosting IPC.
If the connection succeeds you'll see this message in your browser:
Note: It is important to make sure that your browser's proxy settings are the same as those in IPC. The browser could be configured to connect through a proxy, whereas IPC is not.
You should also contact the Worldpay Support team to check if any issues are being experienced at the Worldpay Payments Hub.