Authorize.Net: Support Accept.js PCI Tokens #4406
Closed
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
This helper contains two functions for adding Accept.js (PCI) tokenization support to the test suite. One, `accept_js_token` is a simple dummy/placeholder opaque data structure. The second, `get_sandbox_acceptjs_token_for_credit_card(credit_ard)` takes a test credit card object from ActiveMerchant and constructs an XML API request to the configured Authorize sandbox (in fixtures). This API request (securePaymentContainerRequest) is essentially what the Accept.js javascript code does. Since providing opaque data in the the test suite to validate gateway behavior for tokens requires opaque data from Authorize, we have to ask them for it as if we were using the Accept.js scriptsin a browser.
By renaming the helper method `add_accept_js` to `add_opaque_data`, we clarify that any payment details that produce `:opaque_data` are usable as payment data.
clintmiller
changed the title
|
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! |
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 is a PR that's not so dissimilar from other's I've seen in this project, like #3224 and #2422. There may be others I haven't found. One difference is that this work supports both the "main" gateway
AuthorizeNetGatewayand the "legacy/almost deprecated"AuthorizeNetCimGatewayin one PR. Maybe this is helpful for bringing support for these Accept.js tokens to ActiveMerchant.I was able to add a test helper that constructs a valid Accept.js token in the Authorize.net sandbox environment, which is essential for writing remote gateway tests against API calls using these tokens. That uses the same API that the Javascript Accept.js client-side library calls to obtain the token.