Skip to content

Update AddToWalletButton and canAddCardToWallet to support Google Wallet Unified Push Provisioning#2496

Merged
mfogel-stripe merged 5 commits into
masterfrom
issuing-upp
Jun 22, 2026
Merged

Update AddToWalletButton and canAddCardToWallet to support Google Wallet Unified Push Provisioning#2496
mfogel-stripe merged 5 commits into
masterfrom
issuing-upp

Conversation

@mfogel-stripe

@mfogel-stripe mfogel-stripe commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Updated Stripe Issuing Android Push Provisioning SDK from 1.1.0+ to 1.3.0+.
  • Updated Google Wallet Android Push Provisioning to the Unified Push Provisioning flow. This enables issued cards to be provisioned onto wearable devices via a mobile phone. canAddCardToWallet now requires cardBrand, and now checks if the card can be provisioned onto the mobile device or any connected wearable devices. See documentation for integration guide.
  • Added Issuing support for Google Wallet Bounce Provisioning via the isBounceProvisioned parameter on AddToWalletButton. See documentation for integration guide.

Motivation

Testing

  • I tested this manually
  • I added automated tests

Documentation

Select one:

  • I have added relevant documentation for my changes.
  • This PR does not result in any developer-facing changes.

@mfogel-stripe mfogel-stripe force-pushed the issuing-upp branch 8 times, most recently from 627c4f4 to 667e4a3 Compare June 18, 2026 06:06
@mfogel-stripe mfogel-stripe marked this pull request as ready for review June 18, 2026 17:03
@mfogel-stripe mfogel-stripe requested review from a team as code owners June 18, 2026 17:03
Comment thread src/types/PushProvisioning.ts

val requestClass = Class.forName("com.google.android.gms.tapandpay.issuer.HasEligibleTokenizationTargetRequest")
val tapAndPayClientClass = Class.forName("com.google.android.gms.tapandpay.TapAndPayClient")
val method = tapAndPayClientClass.getMethod("hasEligibleTokenizationTarget", requestClass)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably not for this PR but is there any way we can improve on this to not use reflection? Could Google's TapAndPay SDK be a compile-only SDK so we can use it at compile-time and not have to use a lot of reflection here or does Google not want any exposure of their SDK in a public repo?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a private SDK that you need approval from Google (and NDAs) to download, so it's best to limit any exposure here.

@mfogel-stripe mfogel-stripe merged commit 282c5e2 into master Jun 22, 2026
9 checks passed
@mfogel-stripe mfogel-stripe deleted the issuing-upp branch June 22, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants