REST API

Added

• Added the mobilePaymentMethodSpecificInput.paymentProduct320SpecificInput.cardholderName property to the create payment API endpoint to be used with Google Pay (paymentProductId 320) for 3-D Secure in case of PAN_ONLY transactions.

• Fixed

  • Fixed an issue when redirecting the consumer related to a 3-D Secure challenge in the component handling the redirect (so not in the API itself)

Added

• Added the cardholderName property to the cardPaymentMethodSpecificOutput.card response object.
• Added the values urlIntent and desktopQRCode to property redirectPaymentMethodSpecificInput.paymentProduct4101SpecificInput.integrationType. The value urlIntent will replace the value mobile of property redirectPaymentMethodSpecificInput.paymentProduct4101SpecificInput.integrationType. 
• The order.references.descriptor property is now supported

Fixed

• Card products are now also marked as recurring payment products in Get Payment Product response. 
• Requesting a capture for a non-capturable payment now results in an ACTION_NOT_ALLOWED_ON_TRANSACTION error. 
• Calling get payment endpoint now returns a 404 instead of 500 when called with an invalid paymentId

Deprecated

• The value mobile of property redirectPaymentMethodSpecificInput.paymentProduct4101SpecificInput.integrationType is now deprecated.

Changed

• The property name.surname of CreatePaymentRequest, CreatePayoutRequest, and RefundRequest is now truncated if the value is longer than 25 characters.
• The properties address.houseNumber and address.additionalInfo of CreatePaymentRequest, RefundRequest and CreatePayoutRequest are now truncated if the value is longer than 10 characters.
• The properties order.customer.billingAddress.houseNumber and order.customer.billingAddress.additionalInfo of CreatePaymentRequest are now truncated if the value is longer than 10 characters.

Added

• Payment product group fields will now contain the validators overrides based on the platform routing used by the majority of the payment products within a group
• Added device fingerprinting information to the fraudResults.microsoftFraudResults response object

Fixed

• You can now create captures for 3-D Secure transactions.