Skip to content
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

Refactor /payment_methods to support a unified interface for vaulting use-cases #4933

Closed
Tracked by #4792
Sarthak1799 opened this issue Jun 10, 2024 · 0 comments · Fixed by #5812
Closed
Tracked by #4792

Refactor /payment_methods to support a unified interface for vaulting use-cases #4933

Sarthak1799 opened this issue Jun 10, 2024 · 0 comments · Fixed by #5812
Assignees
Labels
A-payment-methods Area: Payment Methods C-refactor Category: Refactor

Comments

@Sarthak1799
Copy link
Contributor

Sarthak1799 commented Jun 10, 2024

Feature Description

We want a unified interface to /payment_methods create APIs for vaulting a payment method. Request/Response types and their behavior should be same across the vaulting APIs.
Involved APIs would be PM create and PM save.

Possible Implementation

Can involve -

  • refactoring of Req/Res (and other relevant types) for vaulting APIs
  • refactoring of core logic for vaulting APIs
@Sarthak1799 Sarthak1799 self-assigned this Jun 10, 2024
@Sarthak1799 Sarthak1799 added A-payment-methods Area: Payment Methods C-refactor Category: Refactor labels Jun 10, 2024
@Sarthak1799 Sarthak1799 linked a pull request Jun 19, 2024 that will close this issue
14 tasks
@Sarthak1799 Sarthak1799 linked a pull request Sep 5, 2024 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-payment-methods Area: Payment Methods C-refactor Category: Refactor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant