Fix for issue #124
This allows isSuccessful()
to be used in the notification handler (acceptNotification
). That is the last contact point from the gateway to the merchant site with the result of the transaction, before the user to returned to the merchant site (using Sage Pay Server), and so this is where isSuccessful()
needs to be available.
No BC breaks - an existing method is moved up a level to a trait so it is accessible in a wider number of message classes.