Add playground API configuration setting - #14370
Draft
tjclawson-stripe wants to merge 2 commits into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Add a "Use ApiConfiguration" playground setting for PaymentSheet, FlowController, and Embedded Payment Element.
When enabled, the playground stores the publishable key and optional Stripe account ID returned by the backend and supplies them through each integration configuration instead of initializing process-wide
PaymentConfiguration. The standalone Embedded example also resolves credentials before configuration and reuses its prefetched intent result during confirmation.Expose the preview
PaymentSheet.Configuration.Builder.apiConfiguration()entry point so PaymentSheet and FlowController can opt into per-instance credentials alongside Embedded Payment Element.Committed and created by Codex.
Motivation
The playground should exercise API-configuration-only integrations and verify that PaymentSheet, FlowController, and Embedded Payment Element do not depend on global
PaymentConfigurationinitialization.Keeping the resolved credential pair in the playground snapshot preserves it across Activity recreation while ensuring each payment-element instance owns the credentials selected by its backend response.
Testing
Screenshots
Not applicable — playground configuration behavior only.
Changelog