- Payment Services v2
- Transparent Gateway API v2
Payment Services v2
15242 - Standardize 3DS parameters
3DS parameters standardized across payment gateways. Non-breaking changes were implement across the following gateways: Adyen, EBANX, Elavon, Payeezy, Braintree, Cybersource and Nuvei.
-
Adyen
ThreeDSecure.ThreeDSecureVersion
is converted to a string, but an int will continue to be accepted.
-
EBANX
ThreeDSecure.DSTransId
replacesThreeDSecure.TrxID
.TrxID
will continue to be accepted.
-
Elavon
ThreeDSecure.ThreeDSecureVersion
-ssl_3ds_message_version
ThreeDSecure.ThreeDSServerTransId
-ssl_3ds_server_trans_id
ThreeDSecure.TransactionStatus
-ssl_3ds_trans_status
ThreeDSecure.TransactionStatusReason
-ssl_3ds_trans_status_reason
ThreeDSecure.DSTransId
-ssl_dir_server_tran_id
ThreeDSecure.ProgramProtocol
-ssl_program_protocol
-
Payeezy
- ThreeDSecure.DSTransId replaces ThreeDSecure.DirectoryServerTransactionId. DirectoryServerTransactionId will continue to be accepted.
- ThreeDSecureVersion is unmapped. Replaced with ThreeDSecure.ProgramProtocol.
-
Braintree
- ThreeDSecure.DSTransId replaces ThreeDSecure.DsTransactionId. DsTransactionId will continue to be accepted.
- ThreeDSecureVersion - sending 1 or 2 will translate the output to either 2.1.0 or 2.2.0 respectively. Any other values are sent along untransformed.
-
CyberSource gets two new mappings
- ThreeDSecure.DSTransId - DirectoryServerTransactionId
- ThreeDSecure.ProgramProtocol - PaSpecificationVersion
-
Nuvei
- ThreeDSecure.DSTransId replaces ExternalMpi.DsTransId. ExternalMpi.DsTransId will continue to be accepted.
- ThreeDSecure.ProgramProtocol replaces ThreeDSecure.ExternalMpi.ThreeDProtocolVersion.
- ExternalMpi.ThreeDProtocolVersion will continue to be accepted.
Transparent Gateway API v2
15981 - BUG - Transparent Gateway API v2 Status Code 500 errors.
- Transparent Gateway API v2: When TokenEx IP is not whitelisted on the Third party server (where we are trying to send a request), we were getting an exception "HttpRequestException" which was not being handled/caught on TokenEx side and was resulting in 500 & 9999 error. Since the exception is now being handled, Transparent Gateway API v2 is throwing a 200 with ThirdPartyStatus code as 500.