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 have a unified Bank type #5058

Open
Tracked by #4792
Sarthak1799 opened this issue Jun 20, 2024 · 0 comments · May be fixed by #5099
Open
Tracked by #4792

Refactor payment methods to have a unified Bank type #5058

Sarthak1799 opened this issue Jun 20, 2024 · 0 comments · May be fixed by #5099
Assignees
Labels
A-payment-methods Area: Payment Methods C-refactor Category: Refactor

Comments

@Sarthak1799
Copy link
Contributor

Sarthak1799 commented Jun 20, 2024

Feature Description

We need to have a unified bank struct in payment methods. This particular bank type should ideally be used across the application.

Possible Implementation

Will need to implement a unified type for bank related data that would be flow agnostic and to be used across payments, payment_methods, payouts, etc.
We'd start with a unified type for PaymentMethods + Payouts, later on move it to domain models (and possible api models) for Payments as well.

@Sarthak1799 Sarthak1799 self-assigned this Jun 20, 2024
@Sarthak1799 Sarthak1799 added A-payment-methods Area: Payment Methods C-refactor Category: Refactor labels Jun 20, 2024
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