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

[FEATURE] add endpoint for listing connector features #6784

Open
2 tasks done
AkshayaFoiger opened this issue Dec 10, 2024 · 0 comments · Fixed by #6612 · May be fixed by #6963
Open
2 tasks done

[FEATURE] add endpoint for listing connector features #6784

AkshayaFoiger opened this issue Dec 10, 2024 · 0 comments · Fixed by #6612 · May be fixed by #6963
Assignees
Labels
C-feature Category: Feature request or enhancement M-api-contract-changes Metadata: This PR involves API contract changes M-configuration-changes Metadata: This PR involves configuration changes

Comments

@AkshayaFoiger
Copy link
Contributor

AkshayaFoiger commented Dec 10, 2024

Feature Description

-> Why?
With new features being added, it is becoming increasingly difficult to track all the additions. This information is essential for accurately representing Hyperswitch's offerings. Having this solution will eliminate inconsistencies between the documentation and the actual implementation, ensuring clarity and alignment.

-> What?

Introduce an API endpoint that provides:
-> A list of all connectors.
-> The payment methods supported by each connector.
-> The status of these payment methods.
-> Features supported by the connector

Possible Implementation

-> ConnectorSpecifications Connector trait :
Function in this trait, will provide all the connector specific details like payment methods supported, refunds supported and etc.

-> Pre-validation for Payment Methods
Before invoking a connector to process a payment, this function will check if the specified payment_method is implemented, using the data provided in the ConnectorSpecifications trait. This ensures developers update the relevant functions during development and testing.

-> Unified API Endpoint:
Build an endpoint that collects information from all connectors and consolidates it into a unified JSON response. This will act as a single source of truth for supported features.

Have you spent some time checking if this feature request has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@AkshayaFoiger AkshayaFoiger added C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet M-configuration-changes Metadata: This PR involves configuration changes M-api-contract-changes Metadata: This PR involves API contract changes and removed S-awaiting-triage Status: New issues that have not been assessed yet labels Dec 10, 2024
@AkshayaFoiger AkshayaFoiger self-assigned this Dec 10, 2024
@AkshayaFoiger AkshayaFoiger linked a pull request Dec 10, 2024 that will close this issue
14 tasks
@AkshayaFoiger AkshayaFoiger reopened this Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: Feature request or enhancement M-api-contract-changes Metadata: This PR involves API contract changes M-configuration-changes Metadata: This PR involves configuration changes
Projects
None yet
1 participant