FTPI-1018: Handle Trailing Zeros on Standard Request #46
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
corneliusyaovi
approved these changes
Jan 9, 2025
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.
WooCommerce merchants are currently unable to utilize the redirect integration method on their stores. This issue stems from a bug related to the handling of amounts with trailing zeros during the checksum verification process.
Issue
The presence of trailing zeros in the amount is causing the checksum validation to fail. This is due to the way WooCommerce processes and formats the amount, which impacts the hash generation.
Fix
To resolve this, cast the amount from WooCommerce to a float before generating the checksum hash. This will ensure that the trailing zeros are removed, and the hash is correctly calculated.