Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Versioning
Changelog
Upgrade your API version
Upgrade your SDK version
Developer tools
SDKs
API
Testing
Workbench
Event Destinations
Workflows
Stripe CLI
Stripe Shell
Developers Dashboard
Agent toolkit
Build with LLMsStripe for Visual Studio CodeStripe health alertsFile uploads
Security and privacy
Security
Extend Stripe
Stripe Apps
    Overview
    Get started
    Create an app
    How Stripe Apps work
    Sample apps
    Build an app
    Store secrets
    API authentication methods
    Authorization flows
    Server-side logic
    Listen to events
    Handle different modes
    Enable sandbox support
    App settings page
    Build a UI
    Onboarding
    Distribute your app
    Distribution options
    Upload your app
    Versions and releases
    Test your app
    Publish your app
    Promote your app
    Add deep links
    Create install links
    Assign roles in UI extensions
    Post-install actions
    App analytics
    Embedded components for Apps
    Embed third-party Stripe Apps
    Migrating to Stripe Apps
    Migrate or build an extension
    Migrate a plugin to Stripe Apps or Stripe Connect
    Reference
    App manifest
    CLI
    Extension SDK
    Permissions
    Viewports
    Design patterns
      Action buttons
      Activation flow
      Additional context
      Back link
      Communicating state
      Demo content
      Empty state
      Lists
      Loading
      Progress stepping
      Redirects
      Settings sign in
      Sign in template
      Sign out
      Waiting screens
    Components
Stripe Connectors
Partners
Partner ecosystem
Partner certification
HomeDeveloper toolsStripe AppsDesign patterns

Waiting screens for Stripe Apps

Learn how to use the waiting screen.

Copy page

Keep users informed throughout the entire onboarding process and set clear expectations of wait times and next steps with waiting screens.

Before you begin

Create an app.

Suggested use

  • If users navigate back to Stripe during the onboarding flow, keep them informed about what’s happening. For example:
A screen with a step to complete, supporting context, an action to complete, and affordance to start over
  • Only add a call-to-action if it leads users to the next step of the onboarding process, or to provide additional context they need to complete in the next step.
  • Keep language clear and concise. Avoid providing more context than what users might actually require. For example:
A screen that prompts users to complete an application or start over
  • If you must take users outside of Stripe to connect to your account (not recommended), use a waiting screen that clearly communicates this transition. For example:
A screen that prompts users to finish onboarding or start over

Example

The following sample shows a waiting screen built in a ContextView component:

import { Box, Button, ContextView, Icon, Inline, Link, } from "@stripe/ui-extension-sdk/ui"; const WaitingScreen = () => { return ( <ContextView title="Finish onboarding" footerContent={ <Box> <Button type="primary" css={{ width: "fill" }}> Finish onboarding </Button> <Box css={{ marginTop: "small", textAlign: "center", stack: "x", alignX: "center", gap: "small", }} > <Box>Want to go back?</Box> <Link>Start over.</Link> </Box> </Box> } > <Box css={{ marginBottom: "xlarge" }}> <Inline css={{ backgroundColor: "container", keyline: "neutral", borderRadius: "small", paddingX: "small", paddingTop: "small", paddingBottom: "xsmall", }} > <Icon name="clock" css={{ fill: "secondary" }} /> </Inline> </Box> <Box>Please finish onboarding to SuperTodo.</Box> </ContextView> ); };
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc