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

Integrate EFT as a Payment Method in Hyperswitch #7313

Open
Tracked by #7292
jarnura opened this issue Feb 19, 2025 · 0 comments · May be fixed by #7304
Open
Tracked by #7292

Integrate EFT as a Payment Method in Hyperswitch #7313

jarnura opened this issue Feb 19, 2025 · 0 comments · May be fixed by #7304
Assignees

Comments

@jarnura
Copy link
Member

jarnura commented Feb 19, 2025

Electronic Fund Transfer is a redirection flow, that falls under Bank Redirect in Hyperswitch. We have to add EFT as a payment method.

  • Add EFT under BankRedirectData enum in crates/api_models/src/payments.rs which has a structure:
Eft {
        /// The preferred eft provider
        #[schema(example = "ozow")]
        provider: String,
    }
  • Everywhere the enum BankRedirectData is used we have to put EFT there.
  • In the transformers.rs file of every connector, if the connector supports EFT we have to add implementations there otherwise we'll this as NotSupported or NotImplemented elsewhere.

Ref PR: #7304

@jarnura jarnura changed the title Add EFT as a Payment Method in Hyperswitch Integrate EFT as a Payment Method in Hyperswitch Feb 19, 2025
@ImSagnik007 ImSagnik007 self-assigned this Feb 19, 2025
@ImSagnik007 ImSagnik007 linked a pull request Feb 19, 2025 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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants