Sagepay 5006错误代码修复 [英] Sagepay 5006 error code fix

问题描述

任何人都可以让我知道为什么sagepay抛出5006(无法重定向到供应商的网站.)，我可以过帐到sagepay的交易，并且可以在sagepay的末端提供信用卡信息.但是，我的问题是，一旦它返回我的通知页面，就会引发错误5006.

Can any one please let me know why the sagepay throws the 5006 (Unable to redirect to Vendor's web site.), i can able to post transaction to sagepay and can able to give credit card information at sagepay's end. But, my problem is once it return back to my notification page it throws error 5006.

我无法达到成功或失败的URL.

and i could not reach my success or fail URLs at my end.

推荐答案

请参阅以下有关您的交易失败错误5006的建议:无法重定向到供应商的网站.供应商未能提供RedirectionURL.

Please see the below recommendations regarding your issue with your transactions failing error 5006: Unable to redirect to Vendor's web site. The Vendor failed to provide a RedirectionURL.

错误消息本身并不总是完全准确，因为当他们收到对您NotificationURL的回复时收到的Notification响应有任何问题时，都会显示该错误消息.以下是可以调查的各种已知问题的列表:

The error message itself is not always entirely accurate, as it is displayed when there is any kind of issue with the Notification response they receive in reply to their post to your NotificationURL. The following is a list of various known issues that you can investigate:

1)您可以确认状态为OK，INVALID或ERROR的事务响应的接收

1) You can acknowledge receipt of the transaction response with a Status of either OK, INVALID or ERROR

2)在将以上三个字段写入POST的Response对象之前，请确保您清除响应缓冲区以删除任何标头代码，注释或HTML. Sage Pay服务器期望"Status ="成为响应中的第一个字符.如果没有看到这些内容，则会将响应视为错误并导致事务失败！

2) Before writing the three fields above to the Response object of the POST, please ensure you clear your response buffer to remove any header code, comments or HTML. The Sage Pay Server is expecting "Status=" to be the first characters in the response. If it does not see these, it treats the response as though it is an error and fails the transaction!

3)您的通知页面应仅以状态字段，RedirectURL字段以及可选的StatusDetail字段作为响应.在这些字段之前或之后，不应包含其他HTML，标题，注释或文本. Sage Pay服务器会将所有此类文本视为错误，并导致交易失败

3) Your Notification Page should ONLY respond with a Status field, a RedirectURL field and optionally a StatusDetail field. No other HTML, headers, comments or text should be included either before or after these fields. The Sage Pay Server will treat all such text as an error and fail the transaction

4)无论状态如何，都必须将包含有效的完全合格URL(即以http://或https://开头的地址)的RedirectURL发送到您的网站上Sage Pay将要到达的最终完成页面发送您的客户

4) Regardless of status, the RedirectURL must be sent that contains a valid, Fully Qualified URL (i.e. an address starting http:// or https://) to the final completion page on your site to which Sage Pay will send your customer

5)编码必须为Name = Value字段，并用回车换行符(CRLF)分隔

5) Encoding must be as Name=Value fields separated by carriage-return-linefeeds (CRLF)

6)服务器上的通知页面可能正在崩溃"，您应检查以确保服务器上的通知页面可以正确处理Sage Pay发送的所有消息(确定，中止，未确认，拒绝，待处理和错误).

6) Your notification page on your server may be ‘crashing’ and you should check to ensure that the notification page on your server can handle correctly all the message sent by Sage Pay (OK, ABORT, NOTAUTHED, REJECTED, PENDING and ERROR).

7)在验证通知POST时没有发生任何错误的所有情况下，您都应发送OK，因此，即使Sage Pay向您发送状态为ABORT或NOTAUTHED，您也应使用OK和指向页面的RedirectURL进行答复.通知客户交易未完成.

7) You should send OK in all circumstances where no errors occur in validating the Notification POST, so even if Sage Pay send you a status of ABORT or NOTAUTHED, you should reply with an OK and a RedirectURL that points to a page informing the customer that the transaction did not complete.

8)Sage Pay网关在各种固定IP地址上运行，它们通常使用单独的IP地址来响应所有交易请求.

8) Sage Pay gateway operates on a variety of fixed IP addresses and they usually use separate IP addresses to respond to all transaction requests.

请确保在服务器或防火墙中允许使用以下所有IP地址:

Please ensure that all of the following IP addresses are allowed within your Server or Firewall:

对于到我们网关的出站流量:

For outbound traffic to our gateway:

195.170.169.9 – live.sagepay.com 195.170.169.8 – test.sagepay.com

195.170.169.9 – live.sagepay.com 195.170.169.8 – test.sagepay.com

对于入站流量，仅在使用SERVER时才需要将IP列入白名单，因为这是启动回叫的唯一解决方案.您无需将其应用于我们的FORM和DIRECT集成.我们回叫的IP地址是:

For inbound traffic you only need to whitelist IPs if you are using SERVER as this is the only solution that initiates call backs. You don’t need to apply this for our FORM and DIRECT integrations. The IPs from which we call back are:

195.170.169.14 195.170.169.18 195.170.169.15

195.170.169.14 195.170.169.18 195.170.169.15

Sage Pay使用的子网掩码是255.255.255.000.

The Subnet mask used by Sage Pay is 255.255.255.000.

确保您的防火墙允许出站端口443(仅HTTPS！)和入站端口443(以及可选的80 HTTP)访问权限，以便与我们的服务器进行通信(在Simulator/Test/Live上). 但是，总会有改变的余地. Sage Pay拥有整个195.170.169.0/255范围(256个IP).

Ensure that your firewalls allow outbound Port 443 (HTTPS only!) and inbound Ports 443 (and optionally 80 HTTP) access in order to communicate with our servers (on Simulator/Test/Live). There is however always scope for this to change. Sage Pay own the entire 195.170.169.0/255 range (256 IP’s).

9)您是否使用我们通过NextURL传递到通知页面的"SecurityKey"在数据库中正确匹配了交易

9) Are you matching the transaction correctly on your database using the ‘SecurityKey’ we passed to your notification page with the NextURL

10)如果MD5签名匹配，则您的通知脚本应以状态为OK的RedirectURL响应，并指向一个订单完成页面(如果状态为OK)或一个适当的订单失败页面(如果状态为NOTAUTHED)或错误).您可能希望ABORT消息将客户重定向到一个页面，为他们提供其他付款方式，或者询问他们为什么选择取消.如果签名不匹配，则应检查代码是否正确地重建了消息，并且如果确定是正确的，则应使用INVALID和RedirectURL响应所有此类消息，从而将用户指向失败页面.

10) If the MD5 signatures match, your Notification Script should respond with a Status of OK and a RedirectURL pointing to either an order completion page (if the Status was OK) or an appropriate order failure page (if the Status was NOTAUTHED or ERROR). You may wish ABORT messages to redirect the customer to a page providing them with alternative methods of payment, or asking them why they chose to cancel. If the signatures do not match, you should check that your code is rebuilding the message correctly, and if you are sure that it is, all such messages should be responded to with an INVALID and a RedirectURL pointing the user to a failure page.

这篇关于Sagepay 5006错误代码修复的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！