-
Notifications
You must be signed in to change notification settings - Fork 93
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 original_transaction_id for refunds #216
Comments
Yeah, that value is currently not returned by the API in the transaction response so there's nothing for the PHP client to return. |
@drewish thanks for the quick reply. How do I make a request to Recurly for them to make an API change that would add original_transaction_id field to the transaction response? |
@phpdave hey sorry for the silence, trying to get the API change queued up since it would be a nice addition. |
Just an update that we've got this on our next sprint plan so we should have something out in a couple of weeks. I appreciate your patience. |
@phpdave the original transaction id should be coming back in the API responses starting on Wednesday. Changes to the client will follow. |
Great can't wait for it! Thanks for your help in getting this implemented. |
So had to push this back a bit. Turns out it broke the ruby client so we had to revert the change. It'll come back in a new minor version of the API. |
Problem
I don't see a way to tie a refund transaction back to the original transaction via the PHP client
Suggested Solution
Recurly_Transaction::get($uuid)
should have an additional field returned that's called original_transaction_id for refund transactionsand/or
Successful Refund webhook notification xml (
Recurly_PushNotification
) should have the original_transaction_idReferences
From the exports overview doc:
original_transaction_id - For refunds, this field identifies the transaction being refunded.
https://docs.recurly.com/docs/export-overview
The text was updated successfully, but these errors were encountered: