DockMaster - Notice history

We are pleased to inform you that the payment processing issue has been resolved. You should be able to process payments normally now. We apologize for any inconvenience this issue may have caused you and your customers.

If you are still experiencing any issue with the payment processing service, please log out and back into the DockMaster Application. If restarting does not resolve it, reach out to our support team for assistance. They will help you update the offending workstation and troubleshoot any other problems.

USERS NEED TO LOG OUT & BACK INTO THE APPLICATION

We are happy to announce that we have deployed a fix to the issue that was affecting the payment processing service. This issue has been resolved and the service is now fully operational. However, to ensure that the fix takes effect, you will need to fully log out and back into the application. We apologize for any inconvenience this may have caused you and your customers.

We are close to a resolution on the issue that has affected the payment processing service.

We are still working to resolve the issue that is causing the payments service interruption. We apologize for any inconvenience this may cause you and appreciate your patience.

We are continuing to work on a fix for this incident.

Our engineers are working hard to resolve the root cause of the payment processing issue. We appreciate your patience and understanding as we work through this issue.

We are continuing to work on a fix for this incident.

We are continuing to work on a fix for the incident that is affecting our payment platform. Due to this issue, you may experience an error stating “Failed transaction with result:” when trying to process transactions.

We are still working diligently to fix the problem and restore full service as soon as possible. We appreciate your continued patience.

This incident has been resolved.

We implemented a fix and are currently monitoring the result.

We are continuing to work on a fix for this incident.

This incident has been resolved.

We implemented a fix and are currently monitoring the result.