Re-order payment flow when verifyBuyer is activated - #267
Merged
cesar-sosa-hol merged 2 commits intoAug 18, 2026
Conversation
Armaxis
reviewed
Aug 17, 2026
Armaxis
reviewed
Aug 17, 2026
Armaxis
reviewed
Aug 17, 2026
Armaxis
reviewed
Aug 17, 2026
Armaxis
requested changes
Aug 17, 2026
Armaxis
force-pushed
the
DEVMOB-1149/iap-rn-plugin-2x-combined-buyer-verification-flows-verify-the-wrong
branch
from
August 18, 2026 17:08
e6801bb to
7b6b22d
Compare
Armaxis
approved these changes
Aug 18, 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
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.
In 2.0–2.1.0, combined *WithBuyerVerification methods ran 3DS on a caller-supplied paymentSourceId before opening card entry / Apple Pay / Google Pay, so the verification token could belong to a different payment source than the card the buyer actually used.
This PR restores the correct 1.x / Flutter order: collect the nonce first, then verify that nonce. paymentSourceId is removed from the four combined methods (kept only on startBuyerVerificationFlow); deprecated JS overloads still accept the old argument and ignore it.
Related issues
DEVMOB-1149
Changelog
Fix combined *WithBuyerVerification methods verifying the wrong payment source. They now collect the nonce first, then verify that nonce (matching 1.x). paymentSourceId is removed from these methods; only startBuyerVerificationFlow still takes it. Deprecated JS overloads still accept the old argument and ignore it.
Document the 2.x buyer-verification APIs in docs/reference.md.
Example app no longer passes the sandbox-only ccof:customer-card-id-requires-verification value into combined buyer-verification methods.