Don't duplicate requests to charge or void payments #31
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.
Fixes #30
Both the charge() and voidChargeTransaction() methods are currently sending duplicate requests, and then ignoring the first response.
This seemingly wasn't a problem before (just would delay overall method time), however today the subsequent requests started returning empty responses (#30), which results in transactions going through that appear to have failed on the client's end. I'm guessing the API changed today to start checking the request-id or something as an idempotency key, and ignoring duplicates.