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

Recurly_Transaction::get should return HOST CODE for failed transactions #244

Closed
phpdave opened this issue Jun 28, 2016 · 6 comments
Closed
Labels
V2 V2 Client

Comments

@phpdave
Copy link

phpdave commented Jun 28, 2016

Problem

I need the Host Code value from a failed transaction via the PHP client/Recurly API. This information is displayed under "Parameters" on the transactions detail page at https://{mydomain}.recurly.com/transactions/{transactionid}

Suggested Solution

Recurly_Transaction::get($uuid) should have an additional field returned that's called host_code for failed transactions

and/or

Failed Payment webhook notification xml ( Recurly_PushNotification ) should have the host_code

Notes

My intermediary gateway is returning a 1000 gateway_error_code "unknown error", but my Processor is giving me more information in the Host_Code field (at the intermediary gateway this is referred to as the Response Code). I need this information to properly handle the failed payment as the Host Code # can be used to determine that the error is not unknown but that it was a decline.

@drewish
Copy link

drewish commented Jun 28, 2016

Let me look into that. It might require an API change since I don't think we're currently exposing it.

@drewish
Copy link

drewish commented Jun 28, 2016

@phpdave can you send an email to andrew at recurly dot com with your subdomain and a relevant transaction uuid so I can pull up an example?

@drewish
Copy link

drewish commented Jun 28, 2016

This sounds like something that we'd like to do but it would to go into the backlog so I can't give you any kind of a date on it. I'll leave this open for now.

@aaron-junot
Copy link

@phpdave Is this still an issue for you or have you found a suitable workaround?

@phpdave
Copy link
Author

phpdave commented Aug 22, 2018

Not an issue as much as this would allow me to enhance the error handling capabilities of the API consumer (me and everyone else using this). I’ll leave it up to you and your technical architect to determine if it’s work that is worth pursuing.

@aaron-junot
Copy link

After speaking with the team who would be the ones to implement this feature, we've decided not to pursue it at this time. If there are more requests for it through the proper channels, we may put it on the roadmap. I'm going to close out this issue as it has become stale.

@bhelx bhelx added the V2 V2 Client label Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
V2 V2 Client
Projects
None yet
Development

No branches or pull requests

4 participants