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]: [Airwallex] Use connector_response_reference_id as reference to merchant #2322

Open
2 tasks done
Sakilmostak opened this issue Sep 22, 2023 · 11 comments · May be fixed by #2747
Open
2 tasks done

[FEATURE]: [Airwallex] Use connector_response_reference_id as reference to merchant #2322

Sakilmostak opened this issue Sep 22, 2023 · 11 comments · May be fixed by #2747
Assignees
Labels
A-connector-integration Area: Connector integration C-feature Category: Feature request or enhancement good first issue Good for newcomers hacktoberfest Issues that are up for grabs for Hacktoberfest participants

Comments

@Sakilmostak
Copy link
Contributor

📝 Feature Description

  • Reference id are used to map transactions in the connector’s dashboard.
  • Hyperswitch manages several reference ids, such as payment_id, attempt_id, and connector_transaction_id for a single transaction.
  • However, merchants may encounter uncertainty when determining which ID to utilize in the connector dashboard to identify the payment.

🔨 Possible Implementation

  • When we receive a response from the connector for the payment, we deserialize it and populate the response field in RouterData.
  • For the TransactionResponse type, we must fill the connector_response_reference_id with a corresponding reference id for the merchant to identify the transaction.
  • One might need to have exposure to api docs of the connector for which it is being implemented to decide what to fill in connector_response_reference_id.
  • You can check this PR for further reference feat(connector): [Stripe, Adyen, Checkout] Add reference ID support for retries #1735

🔖 Note: All the changes needed should be contained within hyperswitch/crates/router/src/connector/

📦 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?

@Sakilmostak Sakilmostak added A-connector-integration Area: Connector integration C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet labels Sep 22, 2023
@Sakilmostak Sakilmostak changed the title [FEATURE]: [Airwallex] Use connector_response_reference_id as reference to merchant [FEATURE]: [Airwallex] Use connector_response_reference_id as reference to merchant Sep 22, 2023
@Sakilmostak Sakilmostak added the hacktoberfest Issues that are up for grabs for Hacktoberfest participants label Sep 22, 2023
@VedantKhairnar VedantKhairnar added the good first issue Good for newcomers label Sep 28, 2023
@Aviraltech
Copy link

@VedantKhairnar @Sakilmostak I would be delighted to work on this issue
so kindly assign me this issue !

@AkshayaFoiger AkshayaFoiger removed the S-awaiting-triage Status: New issues that have not been assessed yet label Oct 3, 2023
@AkshayaFoiger
Copy link
Contributor

Hey @Aviraltech, sure! I've assigned this to you.

In case you have any queries, you can ask them on this issue thread, or on our discord server, or on slack whichever you are comfortable with

@srujanchikke
Copy link
Contributor

Hi @Aviraltech ,

Please refer api docs of airwallex here

@VedantKhairnar
Copy link
Collaborator

Hey @Aviraltech ,
Let us know if you face any issues. Happy to help! : )

@VedantKhairnar
Copy link
Collaborator

Hey @Aviraltech ,
Just checking in - are you working on it?
Let us know if you need any help.

@sccalabr
Copy link
Contributor

id be willing to pick this up

@deepanshu-iiitu
Copy link
Contributor

Hello @Aviraltech , we didn't hear back from you, so we are unassigning you from this issue. If you are interested, we will assign you with other issues, if the current one is taken.
Hey @sccalabr Are you still interested in picking this up?

@deepanshu-iiitu deepanshu-iiitu added the S-awaiting-triage Status: New issues that have not been assessed yet label Oct 25, 2023
@TejasMate
Copy link
Contributor

hey @deepanshu-iiitu
could you assign this issue to me?

@sahalsaad
Copy link
Contributor

Hi, can I work on this issue? Thank you

@sccalabr
Copy link
Contributor

Yes I am interested in picking this up

@deepanshu-iiitu
Copy link
Contributor

Hey @sccalabr , sure! I've assigned this to you.

In case you have any queries, you can ask them on this issue thread, or on our discord server, or on slack whichever you are comfortable with

@deepanshu-iiitu deepanshu-iiitu removed the S-awaiting-triage Status: New issues that have not been assessed yet label Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-connector-integration Area: Connector integration C-feature Category: Feature request or enhancement good first issue Good for newcomers hacktoberfest Issues that are up for grabs for Hacktoberfest participants
Projects
None yet
9 participants