Include the authorization in the capture response #23
Conversation
This file contains hidden or 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
Previously the authorization was not being included because an optional ordered parameter was being missed. This meant the authorization was passed to the wrong parameter and not recorded. Payments made using this, at least if autocapture is set to true, would never have their transaction ids recorded. Luckily we do record transaction ids on an associated record so no data is actually lost, but any payments made while this issue was in place would need to have their response codes manually updated in order to refund or void the charges.
AlistairNorman
force-pushed
the
alistair-response-capture-authorization
branch
from
319ef2e to
6e5e750
Compare
jarednorman
approved these changes
Jan 21, 2026
adammathys
approved these changes
Jan 21, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Previously the authorization was not being included because an optional ordered parameter was being missed. This meant the authorization was passed to the wrong parameter and not recorded. Payments made using this, at least if autocapture is set to true, would never have their transaction ids recorded. Luckily we do record transaction ids on an associated record so no data is actually lost, but any payments made while this issue was in place would need to have their response codes manually updated in order to refund or void the charges.