bug fix bpay account #24
Merged
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.
Short Description / Link to Ticket
This pull request addresses a critical bug related to the BPay accounts endpoint configuration, ensuring that POST requests to create BPay accounts no longer fail with a 403 CloudFront error. The fix updates the endpoint used for BPay accounts to the correct one that supports all HTTP methods. The version is also incremented to 2.6.1 to reflect this fix.
Bug fix for BPay accounts:
lib/zai_payment.rbto use the:va_baseendpoint instead of:core_base, resolving the issue where POST requests failed with a 403 error due to endpoint restrictions.Documentation and versioning:
changelog.mdto document the fix for the BPay account endpoint configuration and the related error.lib/zai_payment/version.rb.Testing
Additional Notes