You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is hinted at in documentation added for issue #130
When the user returns from the off-site Sage Pay Form, they return with the transactionId. The gateway should enforce a check to make sure it is the expected transactionId for the current session and basket/cart.
Most merchant sites will sensibly do this, but enforcing it in the driver will offer a further layer of security.
The text was updated successfully, but these errors were encountered:
This would be a breaking change for most sites, and that needs to happen to move to force some safer practices for the sites that don't do this check themselves.
judgej
added a commit
to academe/omnipay-sagepay
that referenced
this issue
Aug 24, 2019
This is hinted at in documentation added for issue #130
When the user returns from the off-site Sage Pay Form, they return with the
transactionId
. The gateway should enforce a check to make sure it is the expectedtransactionId
for the current session and basket/cart.Most merchant sites will sensibly do this, but enforcing it in the driver will offer a further layer of security.
The text was updated successfully, but these errors were encountered: