Loading post…
StripeDavid Edoh-BediTutorial
Testing Connect onboarding with Sandboxes
Summary
Stripe Connect testing can become unwieldy as platforms cover payment methods, US states, international countries, and merchant verification conditions, while the existing test mode stays synchronized with live settings. Sandboxes provide an isolated environment that can replicate a platform’s live configuration without affecting live payment traffic. The workflow covers creating a Sandbox, confirming that Connect settings such as negative-liability handling were preserved, and onboarding test connected accounts through Stripe-provided or custom flows. To reproduce a website-verification failure, a custom account can use “https://inaccessible.stripe.com”; after testing an update to “https://accessible.stripe.com” in the Sandbox, the platform can apply the fix to its production onboarding flow.
Context
Connect testing involves a potentially unwieldy matrix of payment methods, supported US states and international countries, and merchant verification conditions. The existing test mode also maintains synchronized settings with live mode, making independent testing difficult without affecting live payment traffic. Merchant verification problems, such as an unverifiable website, can block connected accounts from conducting business and receiving payments.
Approach / What changed
Create a separate Stripe Sandbox that replicates the live platform’s settings, then use its Connect dashboard to create test connected accounts and reproduce onboarding issues. The example uses a custom account with an inaccessible test website URL, updates that URL through the dashboard or Workbench API Explorer, and verifies the onboarding flow before applying the fix in production.
Takeaways
Sandboxes create an isolated environment that can replicate a live Stripe account’s settings, avoiding the need to configure a separate Connect platform manually.
A custom connected account using “https://inaccessible.stripe.com” can reproduce a website-verification failure during onboarding; “https://accessible.stripe.com” simulates a functioning website.
Workbench API Explorer or the dashboard can update the test URL after reproducing the failure, allowing the onboarding fix to be tested before directing the merchant to update the production account.
Source and freshness
- Source
- stripe.dev
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.