Update preauth response documentation #34
Merged
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
Lassejoe
commented
Sep 17, 2024
thejspr
approved these changes
Sep 17, 2024
Lassejoe
force-pushed
the
update-preauth-repsponse
branch
from
eb077d9 to
afc7ce8
Compare
|
Shouldn't these find their way into the reference documentation as well? I'd be curious to hear more about how to use these in relation to the existing ones too. |
|
@tjconcept we are in the process of adding support for 2.3.1, and once everything is in place we will add it to the reference documentation. |
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.
Due to https://github.com/clearhaus/issues-pci/issues/5039 we should update the preauth documentation.
The preauth response includes new additional fields.