sagepay

Why am I getting the error “4020 : Information received from an Invalid IP address.” from SagePay?

本小妞迷上赌 提交于 2019-12-13 13:41:53
问题 This is a PHP (Zend Framework 1.11) site, not using an off-the-shelf package. When the request to: https://live.sagepay.com/gateway/service/vspserver-register.vsp (with a TxType of PAYMENT ), I get the following response: 4020 : Information received from an Invalid IP address. I have logged in to the SagePay admin area and added the IP address of the live server to the Valid IPs section and I've made sure it's using the correct SagePay URL to post to and. An important note is that this issue

Direct Protocol 4.00: PDS2 - 5083: VpsTxId provided in callback does not match transaction in CRes

淺唱寂寞╮ 提交于 2019-12-13 02:55:49
问题 I can't complete a transaction via the SagePay Test Environment when attempting to run through the "challenge" flow. I'm supplying the new PDS2 fields and using VPS Direct Protocol 4.00 I've triple checked the VPSTxId to make sure it's the one I received in the response to the first stage transaction. The CReq is also present and valid (I've Base64 decoded it and it looks reasonable enough to me). Response from test system (first stage transaction): "Status" -> "3DAUTH" "3DSecureStatus" ->

Why are billing and delivery address fields required to setup SagePay transactions?

大城市里の小女人 提交于 2019-12-12 17:32:57
问题 As the title says, i have some questions about the mandatory valies required to register a server integration transaction. Questions Why are Billing Address fields and Delivery address fields required since protocol version 2.23? (seems odd as the transaction is for payment of a service already provided/delivered) Is there an alternative SagePay integration method that could be used to avoid having to provide these fields? Quick background about integration requirement I'm developing a

Sagepay 2.22 to 3.00 form upgrade - PHP update to AES encryption

谁说胖子不能爱 提交于 2019-12-12 03:35:07
问题 I've been trying with no avail to understand how to upgrade the encryption used in the code for my company's three ecommerce sites from simpleXor to an AES encryption. Without doing this, I cannot upgrade the rest of the code which means after July we won't be able to take any payments online. I've managed to update the crypt form codes in line with the upgrade to 3.00. I can identify the encryption code and have looked through the form integration demo download for PHP from Sagepay but can't

SagePay Form Integration V3.0 error - 3045 : The Currency field is missing

纵然是瞬间 提交于 2019-12-12 02:15:57
问题 Im having an issue while integrating sagepay form into a website. I have generated the form and its posting to the correct URL but i get 3045 : The Currency field is missing when it is set. Is there anything obviouse i may be missing here that i could check? This leads me to believe my encrypt function is incorrect? I may be wrong but here is my function i use to encrypt the data: public function encryptAndEncode($strIn, $vendorTxCode) { $strIV = $this->_password; $strIn = $this-

SagePay Protocol Violation Error

冷暖自知 提交于 2019-12-12 02:03:34
问题 since yesterday afternoon at 1.30pm, two separately written applications that access the SagePay payment gateway and the Reporting API Endpoint have both returned the following error: The server committed a protocol violation. Section=ResponseStatusLine This occurs in the code at the point of System.Net.HttpWebRequest.GetResponse() The payment application hasn't changed since 2009 and was written by an ex-member of staff and is ironically scheduled to be replaced in 3 weeks. The Reporting

Sagepay Direct 3D Secure Blank Page Issue

做~自己de王妃 提交于 2019-12-11 15:44:06
问题 I'm trying to implement Omnipay with Sagepay Direct but am really struggling with the 3D Secure bit. When I post the MD, PaReq and TermUrl to https://test.sagepay.com/mpitools/accesscontroler?action=pareq I just get a blank screen. These previous SO answers suggest removing spaces from the PaReq field solves the issue, but I don't have any spaces in my data. SagePay Direct 3DSecure checkout part returning blank page when redirecting out to bank Sage Pay test server won't load 3D Secure page

Sagepay - Payment Authorised despite 3dSecure Failure

风流意气都作罢 提交于 2019-12-11 15:13:32
问题 We're currently updating our SagePay integration to enforce 3DSecure in line with the EU regulations coming into force. However our tests have found that, even though 3DSecure is marked as a 'Fail', the payment was still authorised. We havent set up any specific rules in the Admin system other than the 3D Secure check. (none of the other 3d secure tick boxes are checked and there are no values in the min/max fields). We want to set up our system so that if 3Dsecure fails it does not authorise

Sagepay form Integration keeps giving error 5080 (Form transaction registration failed)

我的未来我决定 提交于 2019-12-11 04:45:42
问题 I have been trying to implement sage pay's form integration. Every time i submit a form i keep getting error code:5080 (Error description: transaction registration failed). I tried searching for error code in sagepays website (https://www.sagepay.co.uk/support/error-codes) but apparently this error code doesn't exist. If i type in the error description in sagepay's error code page, rather than the error code then i get the following result screenshot However both my success url and failure

Sage Pay test server won't load 3D Secure page

倾然丶 夕夏残阳落幕 提交于 2019-12-11 04:33:13
问题 I'm integrating Sage Pay Direct into a website. Currently I'm running everything in test mode, and everything works fine unless I test a payment using 3D Secure. I am using the first card details from the Sage Pay test cards here: http://www.sagepay.co.uk/support/12/36/test-card-details-for-your-test-transactions This causes my site to go to its 3D Secure page containing an iframe which loads Sage Pay's own 3D Secure page from their test server. However, it's just completely empty. It's a