- 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.ThreeDSecureVersionis converted to a string, but an int will continue to be accepted.
-
EBANX
ThreeDSecure.DSTransIdreplacesThreeDSecure.TrxID.TrxIDwill continue to be accepted.
-
Elavon
ThreeDSecure.ThreeDSecureVersionhas been mapped tossl_3ds_message_versionThreeDSecure.ThreeDSServerTransIdhas been mapped tossl_3ds_server_trans_idThreeDSecure.TransactionStatushas been mapped tossl_3ds_trans_statusThreeDSecure.TransactionStatusReasonreplacesssl_3ds_trans_status_reasonThreeDSecure.DSTransIdhas been mapped tossl_dir_server_tran_idThreeDSecure.ProgramProtocolhas been mapped tossl_program_protocol
-
Payeezy
ThreeDSecure.DSTransIdreplacesThreeDSecure.DirectoryServerTransactionId.DirectoryServerTransactionIdwill continue to be accepted.ThreeDSecureVersionis unmapped. Replaced withThreeDSecure.ProgramProtocol.
-
Braintree
ThreeDSecure.DSTransIdreplacesThreeDSecure.DsTransactionId.DsTransactionIdwill 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
ThreeDSecure.DSTransIdhas been mapped toDirectoryServerTransactionIdThreeDSecure.ProgramProtocolhas been mapped toPaSpecificationVersion
-
Nuvei
ThreeDSecure.DSTransIdreplacesExternalMpi.DsTransId.ExternalMpi.DsTransIdwill continue to be accepted.ThreeDSecure.ProgramProtocolreplacesThreeDSecure.ExternalMpi.ThreeDProtocolVersion.ExternalMpi.ThreeDProtocolVersionwill continue to be accepted.
Transparent Gateway API v2
15981 - BUG: Transparent Gateway API v2 Status Code 500 errors
- Transparent Gateway API v2: When a TokenEx egress IP is not whitelisted on a destination third-party server, an "HttpRequestException" is returned, which was not being handled or caught and resulted in 500 and 9999 errors. The exception is now being handled and a Status Code 200 is returned with the ThirdPartyStatus code as 500.