In Hyperswitch, we retrieve transaction status in two ways:
Using transaction_id which is generated by Connectors
Using our reference_id which can be passed to Connectors during payment creation
If supported, the request for retrieving Payments and Refunds should use the Hyperswitch's reference_id. This would assist in obtaining the payment/refund status in the event we failed to get it due to timeout, connection failure, etc.
:hammer: Possible Implementation
If the connector supports retrieving payments and refunds using our reference_id i.e connector_request_reference_id , we should utilize this functionality instead of exclusively relying on the connector_transaction_id.
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?
:memo: Feature Description
In Hyperswitch, we retrieve transaction status in two ways:
transaction_id
which is generated by Connectorsreference_id
which can be passed to Connectors during payment creationIf supported, the request for retrieving Payments and Refunds should use the Hyperswitch's
reference_id
. This would assist in obtaining the payment/refund status in the event we failed to get it due to timeout, connection failure, etc.:hammer: Possible Implementation
connector_request_reference_id
, we should utilize this functionality instead of exclusively relying on the connector_transaction_id.hyperswitch/crates/router/src/connector/
:package: Have you spent some time checking if this feature request has been raised before?
:package: Have you read the Contributing Guidelines?
:sparkles: Are you willing to submit a PR?