Fix transaction ID handling in SnappPay gateway#348
Open
alissn wants to merge 1 commit into
Open
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
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.
Hi,
This PR fixes the issue of passing the TransactionId into the SnappPay gateway.
Changes made:
order_idkey exists in the invoice detailsorder_idis not set, the UUID is converted to an integer usingcrc32()and set as the new UUIDWhy this is needed:
Previously, the gateway was using
getTransactionId()directly, which caused issues because thetransactionIdfield is not populated until after thepurchase()method is called.Additional context:
This change synchronizes the SnappPay driver with the implementation used in other payment gateways, ensuring consistent behavior across the codebase.
Fixes: #338