per recurly support, docs are wrong and canceling should give a state… #389
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aaron-junot
approved these changes
Dec 27, 2018
|
I am getting close to wrapping up my work using the new end points in the
recurly-client. Do we have a timeline on the next release of
recurly-client so we can get the capture/cancel endpoints?
Thanks,
Aaron Kennedy
…On Thu, Dec 27, 2018 at 4:17 PM Aaron Suarez ***@***.***> wrote:
Merged #389 <#389> into
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#389 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfwdMViayMPEYY-hisbCtknuinU4a5Pmks5u9UbjgaJpZM4Zi5Q3>
.
|
|
The next release is scheduled for the last week of January |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… of failed
Hi Aaron,
I'm glad you were able to get the purchase endpoint working with that transaction id. I apologize for the delay following up. I'd be more than happy to help further. I was testing this on my end and I believe what you were seeing in the response is correct. It appears that the invoice is being marked as 'failed'. I'd be more than happy to speak with our team to see if we can get the docs updated to reflect the correct response that is returned by the cancel authorization endpoint. I appreciate you bringing this to our attention. Please let me know if you have any further questions.
Thanks,
Justin
Recurly Support