[FEATURE]: [NMI] 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 , I see that you're already assigned to #2352. For now, we'll leave this issue open to any other interested contributors. You may pick this up once your work on #2352 is completed, and if no other contributors have expressed interest on this. I hope that's fine by you

[parasss19]

Hey @AkshayaFoiger I want to work on this issue could you please assign this issue

[AkshayaFoiger]

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

[parasss19]

Hey @AkshayaFoiger is there any docs for NMI?

[AkshayaFoiger]

Hello @parasss19 , I kindly suggest that you consult NMI's API documentation for reference and guidance.

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

[VedantKhairnar]

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

[parasss19]

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

Yeah actually I am busy with some work I will send PR today

[VedantKhairnar]

Sure @parasss19
Let us know if you face any issues.

[VedantKhairnar]

Hey @parasss19 ,
Please let me know if you are working on it.
Thanks.

[deepanshu-iiitu]

Hello @parasss19 , 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.

[Hangsaai]

Hey @deepanshu-iiitu , can you assign this to me

[TejasMate]

@AkshayaFoiger @deepanshu-iiitu @VedantKhairnar @Sakilmostak
Could you please assign this issue to me? This will be my first contribution to this repo.

[deepanshu-iiitu]

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