checkout-v2-source-token-structure #5536
Open
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
|
To provide a cleaner slate for the maintenance of the library, this PR/Issue is being labeled stale after 60 days without activity. It will be closed in 14 days unless you comment with an update regarding its applicability to the current build. Thank you! |
Author
|
@pjhyett @brynary @lancecarlson @NZKoz Any thoughts? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I work at Dubizzle Labs, where we are using the ActiveMerchant gem in one of our products that I am leading. While migrating our Checkout.com payment gateway implementation from a custom service to ActiveMerchant, I encountered an issue with how token-based payments were structured in the request payload.
This PR aligns the Checkout V2 gateway payload with the Checkout.com API specification for token-based payments.
Previously, type and token were being added at the top level of the request which did not align with Checkout V2’s expected payload structure.
All tests were run locally, and no new test failures occurred after this change.