When using PaymentExpress_PxPay on my Expresso Store, it all works fine until I get returned from DPS with the below URL.
/?ACT=30&H=5c08b9f81972472bd8f0a7691a82388c?result=v5Z1giv_jYce6gai7Ng6XIMCiiGkz5I43snkE6WWVwfMmZMy9iGlWiDp3v4fiv-qYrY9n4YCoX8GC0QnrXLmu95MKZ16QRPLhNgzm7Glv3riSlyGCVNOHGdxSEQLDGxveHs6chn3pdo-osy1ElCqxlvCVBlp7t5P7g7MRsEnUS3tK2sR6tvuCOrkFZJ71reJGDn6jeqEq6LYz20vdeZPF3TtPHPAQaD5hX0_sSJ2fDnMESgsiupFvv5mU4zNoNXL5OlUxR4Z34Jq-ZNyK--NEvcGk8zZHvOkouriaVeeKhhJjCCB8SX64lCeyDgcsfRkofXcx2Qnr4R6qV2qjZkTt2YmdviXQCwxqzKRR5g-ZPTgiZTXn6bu68YE6fzCN94O1K_pFCO4aZ2lN2NR35Ced8eW41LuIkI4VDZYFvXOaG-h7EVETm3XWTARVm-f_rgtyyxwbAi2kJBrfMsp4w59KZx13ACqBRje6-&userid={my DPS user id}
Store can't extract the transaction hash out of the get data. (In Module.php, act_payment_return()) It looks for the index "H" which you can see below, but that drags "?result" and all the rest with it two as it's not properly. I seem to remember having some strange issues with processing DPS responses in the past when building my own payment processors, but as this is an out of the box product where this is already built I thought I better see if anyone else has had this issue.
EE V2.7.2, Store V2.0.6
