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

[BUG] Retrieve Payment Id Throwing 4xx #5259

Closed
2 tasks done
inventvenkat opened this issue Jul 9, 2024 · 0 comments · Fixed by #5262
Closed
2 tasks done

[BUG] Retrieve Payment Id Throwing 4xx #5259

inventvenkat opened this issue Jul 9, 2024 · 0 comments · Fixed by #5262
Assignees
Labels
C-bug Category: Bug

Comments

@inventvenkat
Copy link
Contributor

Bug Description

For MIT transaction, using non MIT payment method Ids, throwing 400. When retreive this payment, it is throwing 422.

Expected Behavior

https://api-reference.hyperswitch.io/api-reference/payments/payments--retrieve

Actual Behavior

{
"error": {
"type": "invalid_request",
"message": "no customer id provided for the payment",
"code": "IR_23"
}
}

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

  1. Disable recurring from Adyen dashboard
  2. Create a recurring payment in Adyen via hyperswitch
  3. Hyperswitch sends a successful transaction and payment method id
  4. Use the payment_method_id, to do MIT transaction. It fails, genuine fails
  5. Try to retrieve the payment. It fails. this is the problem

Context For The Bug

No response

Environment

Are you using hyperswitch hosted version? Yes
If yes, please provide the value of the x-request-id response header to help us debug your issue.
x-request-id : 01909742-36b7-7e91-9e62-6f684418fb1c

Have you spent some time checking if this bug 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?

None

@inventvenkat inventvenkat added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels Jul 9, 2024
@Narayanbhat166 Narayanbhat166 linked a pull request Jul 9, 2024 that will close this issue
4 tasks
@pixincreate pixincreate removed the S-awaiting-triage Status: New issues that have not been assessed yet label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants