How can I create a fully functional, non-restricted Stripe Connect account in test mode with dummy data?

When you create a Connect account in test mode, you can simulate a fully working account by prefilling the required information so that the account isn’t marked as "restricted." By default, if you create an account without providing the required fields (for example, business_profile details, representative information, or accepting the terms), the account’s object will show pending requirements that cause it to be restricted.

In test mode you’re free to use dummy data to prefill all required fields. For example, if you provide dummy values for fields that are normally required during onboarding (such as representative.first_name, representative.last_name, business_profile.url, and so on), the account will be created without triggering the typical “requirements.past_due” or “currently_due” issues that you would see if the data were missing.

Here’s a basic example of creating a Connect account with prefilled data in test mode:

JAVASCRIPTCopied
const stripe = require('stripe')('sk_test_...'); // Your secret test key

(async () => {
  const account = await stripe.accounts.create({
    type: 'custom', // or 'express' if appropriate
    country: 'US',
    email: 'jenny.rosen@example.com',
    business_type: 'individual',
    individual: {
      first_name: 'Jenny',
      last_name: 'Rosen',
      // Add additional required individual details here…
    },
    business_profile: {
      url: 'https://example.com',
      mcc: '5734'
      // Include other profile details as needed
    },
    tos_acceptance: {
      date: Math.floor(Date.now() / 1000),
      ip: '8.8.8.8' // Replace with the tester's IP
    }
  });

  console.log(account);
})();

A few points to keep in mind:

1. Test Mode Behavior: In test mode you can create tokens and accounts using dummy data with your secret test key or publishable key. This simulated account can be treated as “verified” when you provide all required fields.

2. Prefilling Information: If you prefill the account with correct dummy values for all the required fields during account creation, Connect Onboarding won’t ask for them again. This will help you bypass the restrictions that come with incomplete (restricted) account setups.

3. Requirements and Verification: Even in test mode, you will see certain fields in the account object like requirements.currently_due if you don’t pass the required dummy data. Make sure you match the structure of required information referenced in the documentation for a non-restricted account.

By following these best practices, you can create a “fake working” Connect account using fake data in test mode without it being restricted. If you need more specific field details based on your account type and region, refer to our API documentation for the Account object and Connect onboarding best practices.