Remove the ThreeDSecure property on Card which is not in the spec #1812
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This property can sometimes be a hash depending on the account's settings causing deserialization to sometimes fail. Since it's not in the spec anymore and has been removed from stripe-java let's remove it here too to be consistent.
ob-stripe
approved these changes
Oct 10, 2019
|
Released as 31.0.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This property can sometimes be a hash depending on the account's settings causing deserialization to sometimes fail. Since it's not in the spec anymore and has been removed from stripe-java let's remove it here too to be consistent.
r? @ob-stripe
cc @stripe/api-libraries