-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(payment_method): add capability to store bank details using /payment_methods endpoint #3113
Merged
Conversation
This file contains 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
…ment_methods endpoint refactor(payouts): make non-required fields in payout method details to Optional
vspecky
requested changes
Dec 15, 2023
Sarthak1799
reviewed
Dec 15, 2023
…w payment methods for a customer
NishantJoshi00
previously approved these changes
Jan 9, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The request construction and and fields looks to be aligned with the locker schema
vspecky
previously approved these changes
Jan 10, 2024
ArjunKarthik
requested changes
Jan 16, 2024
ArjunKarthik
approved these changes
Jan 16, 2024
vspecky
approved these changes
Jan 16, 2024
pixincreate
added a commit
that referenced
this pull request
Jan 17, 2024
* 'main' of github.com:juspay/hyperswitch: refactor: [Noon] adding new field max_amount to mandate request (#3209) fix(events): fix event generation for paymentmethods list (#3337) chore(router): remove recon from default features (#3370) fix(core): add validation for authtype and metadata in update payment connector (#3305) refactor(connector): [cybersource] recurring mandate flow (#3354) feat(connector_events): added api to fetch connector event logs (#3319) feat(payment_method): add capability to store bank details using /payment_methods endpoint (#3113)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
Ref - Issue #3112
Additional Changes
Motivation and Context
How did you test it?
Tested locally
Postman collection - https://galactic-capsule-229427.postman.co/workspace/My-Workspace~2b563e0d-bad3-420f-8c0b-0fd5b278a4fe/collection/9906252-142ea0ea-f61f-48e7-8317-5f819dd535e9?action=share&creator=9906252
Test Cases
There are two major flows to be tested out which are fixed in this PR
auto_fulfill
falserecurring
true against a cusomter_idChecklist
cargo +nightly fmt --all
cargo clippy