Fix fingerprint set error on legacy checkout #3743
Merged
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.
Fixes #3718
Changes proposed in this Pull Request:
This PR fixes a fatal error being thrown when saving payment method tokens with the legacy checkout enabled. The error happens when setting the fingerprint property (used to identify duplicate tokens). The expected object structure was different from the actual format received (
fingerprint
exists inside the payment method details key, source).Testing instructions
You can follow the test instructions from the related issue:
wp_woocommerce_payment_tokens
to simulate the case where a card is defined in Stripe but not synced to the WC databasechangelog.txt
andreadme.txt
(or does not apply)Post merge