fix: changed request payload of vault card flow#1639
Merged
Conversation
sakksham7
requested review from
AbhishekChorotiya,
ArushKapoorJuspay,
aritro2002 and
seekshiva
as code owners
|
Review changes with |
ArushKapoorJuspay
approved these changes
Jun 24, 2026
github-actions
Bot
added
the
Closed
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
3 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.
Type of Change
Description
#1638
Changed Request Body payload API contract for Vault related flows
For first time user -
vault_data_card -> vault_cardFor return user -
vault_card_token_data -> vault_card_tokenHow did you test it?
Tested via Running VGS Vault flows with new API Contract
Test Recording to be added
Checklist
npm run re:build