docs: document last4/network fields on ApplePayResult#105
Merged
Conversation
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
adarsh-jain-a
approved these changes
Jul 8, 2026
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.
Description
Follow-up to #101 (already merged), which forwards
last4/networkfrom the Apple Pay webview iframe to the merchant'sonCompletecallback. The README's documentedApplePayResultshape was stale — it never listednetwork(added in an earlier PR) and didn't get updated forlast4in #101, so the public docs undersold what the SDK actually returns.Changes:
ApplePayResulttype reference now listslast4?andnetwork?, with a note thatlast4is webview-mode only (native mode's decrypted PassKit payload never carries it).ApplePayprops table'sonCompletedescription to match.Testing
Docs-only change, no code touched.
Security Review
Important
A security review is required for every PR in this repository to comply with PCI requirements.
Security Impact Summary
Docs-only change — no code, data handling, or security-relevant behavior touched.