feat: exchange projectid validation #1075
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
chris13524
reviewed
May 16, 2025
chris13524
approved these changes
May 16, 2025
lukaisailovic
force-pushed
the
feat/exchange-projectid-validation
branch
from
77b57c9 to
e63cbc9
Compare
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.
Description
Added an allowlist for pay with exchange feature. Current implementation is based on what we already have in the code (balance denylist) and naively checks the projectId.
If we see the need, we can also implement the check for allowed origins in the future.
Resolves PAY-29
How Has This Been Tested?
Due Diligence