Support Apple Pay #5
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
…oser and check in lock file.
…and regular card `PurchaseRequest` payload creation.
…k. Fix line length style violations.
GP-860 - Support Apple Pay
* Support more secure 'username', distinct from merchant code * Detect and handle errors better, especially generic CDATA text in an <error>
GP-860 - Port features from `comicrelief/omnipay-worldpay-cg-hosted`
Make applicationData optional to reflect Apple and Worldpay properties
…lement GP-860 - fix Apple Pay processing breaking due to blank attributes on `<session>`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This adds support for Apple Pay to the Direct XML adapter, in line with these instructions.
Note that you must also use Apple Pay JS and additional server logic to prove your server's identity to the JS and have Apple generate a valid payment token using the public part of your Payment Processing Certificate, the CSR for which can be generated from Worldpay admin.
The support added to this adapter is for the final step of the process: sending the token with encrypted
datakey to Worldpay, who own the private key from the Payment Processing Certificate and can use it to decrypt & process the payment token.