Updates to SecurePay for compliance

(Ryan Archer) #1

We have been using SecurePay payment gateway for some time to process payments on our corporate website. Recently securePay 'fell out' of compliancy with CBA (Commonwealth Bank of Australia).

 

Obviously the SecurePay team have been working hard to get that to happen and should meet the set deadline of September. Anyway, we have received an email from them to notify us of some changes and to ask developers who use SecurePay to perform some testing before 24 August, 2016.

 

I'm in the middle of performing numerous tests but I'm having issue with this particular request:

How to begin testing
The testing can be performed in the SecurePay test environment using your standard test transaction credentials.
To double-check that your system supports the change, your developer should configure your test system to send test transactions to the following URLs (relevant to your integration with SecurePay):

For ‘Direct Post’ submit tests to the following URL - https://test.securepay.com.au/directpost/authorise

I don't know how to send a test to https://test.securepay.com.au/directpost/authorise

I can only assume that Squiz Matrix does this form me when the form is put into "Test Mode"

 

Can anyone from Squiz please confirm that this is the correct test URL or if the SecurePay Squiz Matrix asset needs to be changed to accommodate this patch/update from SecurePay vendor?

 

Right now, I just did a test and it worked out OK, but I'm not even sure which URL it was sent to.

 

Please let me know if I can provide more details to assist in this matter.

(Ryan Archer) #2

I have looked many times over the SecurePay Direct Post Payment Gateway asset and I still can't see any way that I can expose the URL that is used to submit the form to in test mode. Is there any way possible to do this?

 

As I have previously mentioned, SecurePay are asking us (as customers) to perform test transactions and send info to this URL https://test.securepay.com.au/directpost/authorise.

 

Is there anyway possible to check this. I did several test transactions and I still cannot see anything - other than the transaction being successful. But I can only assume it is using an older TEST URL API.

(Marcus Fong) #3

I think you’re right - looking at the e-commerce package on a 5.3.4.1 system, there appears to be a hardcoded reference to a slightly different test URL in the SecurePay code.

If you need assistance with this in order to meet a deadline, then you may want to contact your Squiz account manager.