Open sakksham7 opened 2 months ago
Hi, can I work on this issue?
Sure @Nupoor10 Assigning the issue to you, Thanks for your interest!
Hi @gorakhnathy7, I had some doubts. The issue mentions that I need to configure the payment method on the Hyperswitch dashboard, how can I do that since I do not see lawson listed under the connectors? The payment response for lawson returns the required fields object, are those the fields I have to render on the screen? And where should I add this dynamic field component, should it go under the Payments subfolder?
Hey @Nupoor10 ,
As I can see you are looking under the wrong direction. You need to add a Payment Method not a Connector.
Hyperswitch dashboard, how can I do that since I do not see lawson listed under the connectors?
So the correct path will be to look under is. Go to dashboard > Payment Processor > Adyen. There you can see the Lawson Payment Method under the Voucher section.
Link - https://app.hyperswitch.io/dashboard/connectors/new?name=adyen
The payment response for lawson returns the required fields object, are those the fields I have to render on the screen?
Yes you need to render those Payment Methods Required fields in the screen.
And where should I add this dynamic field component, should it go under the Payments subfolder?
Yes it should be under Payments Sub folder. Try these things out. Let us know if you still have any issues.
The Hyperswitch SDK is a versatile tool built to streamline payment integration for developers. It simplifies the process of adding multiple payment methods, allowing you to quickly implement support for various gateways without the need to manually integrate each one. With Hyperswitch, you can efficiently manage payments across platforms, reducing complexity and boosting development speed.
Getting started
Description:
We are looking to implement a new payment method in our WebSDK that supports dynamic field rendering. The goal is to allow the backend to define the fields required for the payment method and have the frontend WebSDK render these fields dynamically based on the response.
This feature should be flexible enough to handle different payment methods, each potentially requiring different types of input fields (e.g., text fields, dropdowns, checkboxes, etc.).
Requirements:
Payment Method Integration Details:
In this section, we provide details on the payment call response and the confirm call payload for the newly integrated payment method. Ensure you have configured the payment method at Hyperswitch Dashboard correctly. The backend already includes support for this payment method, so no additional configuration is needed.
Payment Method List Response for Lawson -
Confirm call Payload should look like:
Dynamic Field Rendering:
Contribution Guidelines:
Helpful Resources:
Submission Process:
Refer here for Terms and conditions for the contest.
If you have any questions or need help getting started, feel free to ask in the comments!