Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Features]: [Noon] Sync with Hyperswitch Reference #2904

Closed
2 tasks done
swangi-kumari opened this issue Nov 17, 2023 · 1 comment
Closed
2 tasks done

[Features]: [Noon] Sync with Hyperswitch Reference #2904

swangi-kumari opened this issue Nov 17, 2023 · 1 comment
Labels
A-connector-integration Area: Connector integration C-feature Category: Feature request or enhancement good first issue Good for newcomers help wanted Extra attention is needed

Comments

@swangi-kumari
Copy link
Contributor

📝 Feature Description

  • In Hyperswitch, we retrieve transaction status in two ways:
  1. Using transaction_id which is generated by Connectors
  2. 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.

🔨 Possible Implementation

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

✨ Are you willing to submit a PR?

@swangi-kumari swangi-kumari added A-connector-integration Area: Connector integration C-feature Category: Feature request or enhancement good first issue Good for newcomers labels Nov 17, 2023
@VedantKhairnar VedantKhairnar added the help wanted Extra attention is needed label Nov 23, 2023
@TwistingTwists
Copy link

Hi @swangi-kumari ,

Can you please explain the following questions ?

  1. How to know if connector supports connector_request_reference_id or not ?
  2. if answer to 1. cannot be known, should we add support for both connector_request_reference_id and connector_transaction_id. ?

Let me know if there is any other documentation related to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-connector-integration Area: Connector integration C-feature Category: Feature request or enhancement good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants