You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser and OS Chrome Version 127.0.6533.89 on MacOS 14.4.1
Issue description
We recently integrated braintree-web's ThreeDSecure (TypeScript version) into our checkout process and encountered an issue where certain interfaces do not include all the properties present in the corresponding data structures.
For example, in the lookup-complete callback, we receive data: ThreeDSecureVerificationData, where we need to access data.paymentMethod.threeDSecureInfo.status. However, TypeScript raises an error because the status property does not exist on the ThreeDSecureInfo type.
To resolve this, we extended the ThreeDSecureInfo interface to include the status property. While this workaround solves the issue temporarily, it is not an ideal long-term solution.
It would be highly beneficial if the types/interfaces were updated to reflect the complete structure, including the status property. Additionally, it would be helpful to expose enums such as ThreeDSecureEvent (among others) to improve clarity and consistency:
Hi there! We can't speak to the typescript library wrapper for braintree-web, as we don't own that, and unfortunately don't have one of our own. We encourage you to submit a PR against that library for changes, or raise the issue with them. Apologies I cannot be of more assistance.
General information
Issue description
We recently integrated braintree-web's ThreeDSecure (TypeScript version) into our checkout process and encountered an issue where certain interfaces do not include all the properties present in the corresponding data structures.
For example, in the
lookup-complete
callback, we receivedata: ThreeDSecureVerificationData
, where we need to accessdata.paymentMethod.threeDSecureInfo.status
. However, TypeScript raises an error because thestatus
property does not exist on the ThreeDSecureInfo type.To resolve this, we extended the
ThreeDSecureInfo
interface to include the status property. While this workaround solves the issue temporarily, it is not an ideal long-term solution.It would be highly beneficial if the types/interfaces were updated to reflect the complete structure, including the status property. Additionally, it would be helpful to expose enums such as ThreeDSecureEvent (among others) to improve clarity and consistency:
The text was updated successfully, but these errors were encountered: