Question

很抱歉，这并不是与代码相关的问题。

我已经建立了协议v4.0的集成来处理3DSv2，但在与SagePay支持人员通话后，他们现在说一切都已延迟。然后我在网上找到了这个

FCA不会对不采取行动的公司采取执法行动自2019年9月14日起在以下地区满足SCA的相关要求如果有证据表明他们已经同意了计划采取了必要的步骤以符合计划。在末尾在18个月的期限内，FCA希望所有公司都做出必要的决定进行更改并进行了应用SCA所需的测试。

来源：https://www.fca.org.uk/news/press-releases/fca-agrees-plan-phased-implementation-strong-customer-authentication

并没有像SagePay所相信的那样延迟。所以我想知道SagePay何时真正在其LIVE服务器上将其全部打开？是否有更新-有人知道什么时候会出现吗？

Answer 1

我今天已经再次尝试过了，现在看来可以了（尽管我尝试过的银行降到了v1）。

Answer 2

我已通过电子邮件收到SagePay的最新通知。

3DSecure v2将于2019年9月14日上线。

"Last month, the Financial Conduct Authority announced a welcome 18 month 
extension to the 14 September 2019 Strong Customer Authentication deadline
giving businesses, banks and online account providers more time to roll-out 
the next phase in fraud protection technology. Businesses like yours now have 
until March 2021 to become compliant.

At Sage Pay we've been working to minimise the impact for our customers by 
upgrading our systems to support 3D Secure. While we expect a gradual transition 
to SCA enforcement by banks and issuers across the EU, in time for the deadline, 
there are steps we recommend you start to take now to prepare your business."

...

"We'll continue to work closely with acquirers and issuers across the industry to 
confirm 3D Secure 2 timelines applicable to Sage Pay customers. You can check 
our support pages for regular updates on industry developments."

"From 1 February 2020 issuers will begin to step up transactions. As SCA comes 
into force, banks will start to decline transactions that don't have appropriate 
authentication in place."

希望这会有所帮助。

编辑

我使用SagePay协议3.00将新的代码库上传到了实时站点，发现银行尚未要求输入挑战密码。付款通过3DAUTH支付。订单记录显示3DSecureStatus = OK。

这几乎是我对协议4.00的期望。

看起来银行正步入正轨。

Answer 3

今天在直播中进行了尝试。出现以下错误：

INVALID 3097 : The VPSProtocol value is outside the valid range. Should be between 2.00 and 3.00.

所以它还没有发布。

结果，我们联系了客户经理，告诉我们以下内容：

在所有收购方都同意之前，我们将无法启用支持SCA的协议，但这有望在未来几周内实现。

所以听起来很迫在眉睫。

何时在实时服务器上启用协议v4.0？

3 个答案: