[FEATURE]: [Worldpay] Use connector_response_reference_id as reference to merchant

[Sakilmostak]

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

• I have read the Contributing Guidelines

✨ Are you willing to submit a PR?

[TechWizard9999]

😊 "I'd be delighted to work on this issue! Could you please assign it to me?"

[AkshayaFoiger]

Hey @TechWizard9999 , 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

[imSanko]

@AkshayaFoiger I just want to work on this issue! Is it going to be alright if I send a PR or after you assign that to me?

[AkshayaFoiger]

Hello @imSanko,

This issue has already been assigned to @TechWizard9999. However, we have encountered similar issues with different connectors. I would suggest considering an attempt to address one of those.

[himanshuParashar0101]

i want to work on this issue could you please assign me to this issue

[AkshayaFoiger]

i want to work on this issue could you please assign me to this issue

Hi @himanshuParashar0101,

This issue has already been assigned to @TechWizard9999. However, we have encountered similar issues with different connectors. I would suggest considering an attempt to address one of these issues.

[VedantKhairnar]

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

[VedantKhairnar]

Hey @TechWizard9999 ,
Just checking in - are you working on it or shall we consider reassigning it to someone else?

[speedhs]

Can I work on this one if @TechWizard9999 is not currently work on this?

[VedantKhairnar]

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

[speedhs]

Hey! i went throught the file. I wanted to ask on thing. In the files attached for reference the customer response field is stored in a different way than that for worldpay. Can you clarify on the fields used in response.rs for worldpay?

[Sakilmostak]

Hello @speedhs, can be more specific about the "files attached for reference", might be able to help you out better. Anyways, if you are talking about how we are handling the response i.e. the try_from implementation for the response. To simplify it, We take the response from the connector, parsing it, and then convert it into suitable struct for our core to handle the response. You need to look into what parameters are present while parsing(related struct in response.rs) and which one of those can be used as connector_response_reference_id. (In case such parameter is not present, create on the basis of docs) Hope this helps

[swangi-kumari]

Hey @speedhs ,
Are you still working on this issue?
Please let us know if you need any help.