|
[AlphaCommerceHub] The 3D Secure scenario is broken again since 2017-12-14: «Request failed, technical error»
|
|
1
|
674
|
December 14, 2017
|
|
[AlphaCommerceHub] A `SuccessURL` response to a bank card payment with a 3D Secure verification
|
|
1
|
879
|
November 18, 2017
|
|
[AlphaCommerceHub] What will happen if a not configured for 3D Secure merchant will pass `3DSecureBypass = Y` in an AlphaHPP request?
|
|
4
|
940
|
December 1, 2017
|
|
[AlphaCommerceHub] What will happen if a not configured for 3D Secure merchant will pass `3DSecureBypass = N` in an AlphaHPP request?
|
|
2
|
763
|
December 1, 2017
|
|
How can a merchant's store detect whether a bank card has been verified with 3D Secure or not?
|
|
1
|
597
|
December 1, 2017
|
|
[AlphaCommerceHub] How to get test data for a 3D Secure payment?
|
|
2
|
1218
|
November 22, 2017
|
|
Why the AlphaHPP responses to successfull bank card payments do not contain the `ChannelType` documented parameter?
|
|
2
|
801
|
November 20, 2017
|
|
[AlphaCommerceHub] Is `Y` the only allowed value of the `3DSecureBypass` parameter, or `N` (or an empty string) is also allowed?
|
|
2
|
803
|
November 3, 2017
|
|
[AlphaCommerceHub] Why does a manual 3D-secured `AuthPayment` request through the API Explorer with the default data fail with the message «Invalid Parameters - order.xid: Maximum length is 20»?
|
|
1
|
801
|
October 31, 2017
|
|
[AlphaCommerceHub] An `AuthPayment` request with 3D Secure
|
|
1
|
845
|
October 26, 2017
|