hyperswitch icon indicating copy to clipboard operation
hyperswitch copied to clipboard

[FEATURE]: [Square] Use `connector_request_reference_id` as reference to the connector

Open Sakilmostak opened this issue 2 years ago • 14 comments

:memo: Feature Description

  • We transmit our reference id from Hyperswitch to the connector, enabling merchants to subsequently locate the payment within the connector dashboard.
  • Presently, there is a lack of uniformity in this process, as some implementations employ payment_id while others utilize attempt_id.
  • This inconsistency arises from the fact that payment_id and attempt_id correspond to two distinct entities within our system.

:hammer: Possible Implementation

  • To mitigate this confusion, we've introduced a new field called connector_request_reference_id in our RouterData.
  • This id should replace them as a reference id to the connector for payment request.
  • One might need to have exposure to api docs of the connector for which it is being implemented.
  • You can check this PR for further reference https://github.com/juspay/hyperswitch/pull/2052

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

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

  • [X] I checked and didn't find a similar issue

:package: Have you read the Contributing Guidelines?

:sparkles: Are you willing to submit a PR?

Sakilmostak avatar Sep 22 '23 13:09 Sakilmostak

Can I try this issue @Sakilmostak ?

Ln11211 avatar Oct 02 '23 17:10 Ln11211

Sure @Ln11211, I'll assign this to you. Let us know in case you have any questions, on this issue thread or on our Discord server.

SanchithHegde avatar Oct 02 '23 18:10 SanchithHegde

Hey @Ln11211 , Please let me know if you are working on it or shall we reassign it to someone else.

VedantKhairnar avatar Oct 10 '23 12:10 VedantKhairnar

I am unable to work on this and I ask you to please reassign this to someone else. Thank you for your time.

Ln11211 avatar Oct 10 '23 15:10 Ln11211

Hi, can I work on this if it's still up?

skoriop avatar Oct 17 '23 11:10 skoriop

Hey @skoriop , 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.

swangi-kumari avatar Oct 17 '23 18:10 swangi-kumari

Hey @skoriop Just checking in - are you working on it? Do you need help from our side?

deepanshu-iiitu avatar Oct 26 '23 12:10 deepanshu-iiitu

Hey please assign this issue to me

shivam-jainn avatar Oct 30 '23 03:10 shivam-jainn

Hello @skoriop , 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 @shivam-jainn , 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 avatar Oct 31 '23 10:10 deepanshu-iiitu

@deepanshu-iiitu can you check out #2767

hegdeadithyak avatar Nov 03 '23 14:11 hegdeadithyak

Hey @shivam-jainn , Are you still working on this issue?

swangi-kumari avatar Dec 12 '23 09:12 swangi-kumari

Hey @shivam-jainn , Are you still working on this issue?

Hey ! I stopped working on it since Adithya made a PR while I was working on it .

shivam-jainn avatar Dec 12 '23 10:12 shivam-jainn

Hey All, Freeing this Issue due to prolonged inactivity.

gorakhnathy7 avatar Oct 02 '24 09:10 gorakhnathy7

@gorakhnathy7 Please assign this issue to me. Thanks.

Rutam21 avatar Nov 08 '24 13:11 Rutam21

Feels like this one is kinda abandoned. I can take it, @swangi-kumari , @gorakhnathy7 Thanks!

daniloff200 avatar Oct 03 '25 23:10 daniloff200