Feature/new endpoint payment setups #419
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
|
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.
This pull request introduces a new
PaymentSetupsAPI integration, allowing users to create, update, retrieve, and confirm payment setups as part of the checkout process. It also adds comprehensive integration tests for the new functionality and updates the main exports and class initialization to include the new API.PaymentSetups API integration:
PaymentSetupsclass insrc/api/payment-setups/payment-setups.jswith methods to create, update, get, and confirm payment setups, including error handling and input validation.PaymentSetupsAPI in the mainCheckoutclass (src/Checkout.js) and exported it from the library entry point (src/index.js). [1] [2]Testing and validation:
test/payment-setups/payment-setups-unit.js,test/payment-setups/payment-setups-it.jsto cover the lifecycle of payment setups (create, get, update, confirm) and error handling for invalid or missing data.