[BWS] Fix: Ramp Network signed payment url params update - #4204
Merged
kajoseph merged 2 commits intoJul 23, 2026
Conversation
kajoseph
approved these changes
Jul 23, 2026
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
2 participants
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
Ramp deprecated the legacy per-flow search params in favor of a unified format.
Ref: https://docs.rampnetwork.com/search-params-migration
Older app versions still send the legacy fields, so we translate them into the new unified params here to keep those requests working going forward. If a newer client already sends the new params, those take precedence.
Changelog
In this PR, the old parameters are modified for the new format, and those that are no longer supported are removed, to avoid errors in the integration. (The
useSendCryptoCallbackVersion: 1param was removed, as it was causing errors in Offramp integration.)