#diane_best-practices

1 messages · Page 1 of 1 (latest)

warm duneBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1433911973397008424

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

mild ruin
#

Hi there! What is your question?

odd sail
#

We’re implementing Stripe Identity in a React Native app and want to confirm the best-practice approach for handling session creation and verification status sync between the app, backend, and Stripe.

Here’s our current flow:
• The app calls our backend to start verification.
• The backend creates a Stripe verification session using the server SDK, retrieves the ephemeral key (client secret), and passes it back to the app without storing anything.
• The app presents the Stripe Identity modal via the React Native hook and receives a local result (completed, cancelled, or failed.)
• The app reports this status to the backend under the user context.
• Stripe sends webhook events to the backend with the authoritative verification status.
• The backend reconciles both inputs and treats Stripe’s webhook as the final source of truth.
• The app polls or listens to the backend for the latest verified status to display in the UI.

Could you confirm if this is the recommended architecture for Stripe Identity with React Native and ephemeral keys, and whether relying on webhooks (without persisting sessions in backend) is considered best practice?

Just making sure this approach aligns with Stripe’s intended flow.

mild ruin
#

I'm not super familiar with Stripe Identity, however I can confirm that relying on the events returned to the webhook endpoint is considered best practice and encouraged by Stripe.

odd sail
#

Is there someone who’s familiar with the identity implementation that can guide me on this flow?