[FEATURE]: [Coinbase] 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?

[Kota-Karthik]

@Sakilmostak @AkshayaFoiger
I am interested in doing this issue
so kindly assign me this
Thank You : )

[AkshayaFoiger]

Hey @Kota-Karthik, I see that you're already assigned to #2351. For now, we'll leave this issue open to any other interested contributors. You may pick this up once your work on #2351 is completed, and if no other contributors have expressed interest on this. I hope that's fine by you

[Ceres445]

I tried checking coinbase documentation and landed at this but it doesn't describe the data event properly or give any context as to what it uses as a reference id for the transaction. The structure also has different fields than the example provided in the documentation. Can anyone point me in the correct direction?

[AkshayaFoiger]

Hello @Ceres445,

I noticed you were referring to the webhook structure, and I recommend consulting Coinbase's API documentation for more detailed information. Additionally, while searching for the connector reference ID, please be aware that some connectors may not require a payment reference ID in their payment requests. However, it is expected that they will provide a payment-specific ID in their response, which should then be populated as the 'connector_reference_id,' as specified in the issue.

I trust that this information proves valuable. If you have any further inquiries, please feel free to reach out.

[Ceres445]

@AkshayaFoiger can you please assign me this issue

[AkshayaFoiger]

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

[VedantKhairnar]

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

[Ceres445]

I'm having some issues running the test script cargo test --package router --test connectors -- stripe:: --test-threads=1. But I've read the documentation mentioned above and made the changes.

[srujanchikke]

Hello @Ceres445 ,

No worries, Don't need to run the test script . Please raise a PR to main!