RyzeDeskRyzeDesk

Stripe

4105 articles

Install and configure the Stripe Connector Add-ons bundle


Install and configure the Stripe Connector Add-ons bundle

Learn about the prerequisite configuration steps for all features in the Stripe Connector Add-ons bundle.

Warning

If you’re migrating from SuiteSync to the Stripe Connector for NetSuite, use the migration instructions.

The instructions on this page explain how to install and configure the Stripe Connector Add-ons bundle, which is a prerequisite for any of the following Stripe Connector for NetSuite (SCN) workflows:

  • NetSuite auto pay
  • Payment linker
  • Paid out of band
  • NetSuite-initiated refunds

Install the bundle in NetSuite

  1. In NetSuite, go to Customization > SuiteBundler > Search & Install Bundles . You can type “bundles” in the global search bar to find this page.
  2. Search for 502910 to find and install the Stripe Connector Add-ons bundle. Click the bundle link in the search results.
  3. On the first page, click Install . Caution This bundle might take time to install because of the number of components included. Don’t alter any components in the bundle during installation.
  4. On the next page, click Install Bundle . When you’re redirected to the bundles list page, you can monitor the installation status of the installation by refreshing the page.

Configure the Stripe Account custom record

The bundle includes a custom record type called Stripe Account, which represents your actual Stripe account through an API key generated in the Stripe Dashboard. You must repeat this section for every Stripe account that you want to use the bundle.

Installing this bundle automatically creates a Stripe Custom Center tab in the colored bar on any NetSuite page. If you don’t see it, click the overflow menu (), which might also be hidden behind floating NetSuite elements. Bundle installation is specific to the NetSuite sandbox or production account you’re working in.

  1. Go to Stripe > Add-ons > Stripe Accounts > New.
  2. Click New Stripe Account.
  3. In the Name field, enter the name of the Stripe account. You can copy the name as it appears in the Stripe Dashboard, or you can customize the name for quick identification. Consider this if you have many accounts. For example, you can change Company ABC to Company ABC - US Sandbox.
  4. In a separate browser tab, open the Account details page and copy the value from the Account ID field. Return to the browser tab with NetSuite open that points to the Stripe Account custom record page. Paste the value in the Stripe Account ID field. Caution Make sure you copy the account ID from the correct Stripe account and mode: test mode, sandbox, or live mode. If the account details page displays “Some settings are hidden,” click View all settings to reveal the Account ID field.
  5. If this is the only Stripe account record you want to configure in either NetSuite sandbox or production, select Default Account. This sets the value to true. Note If you configure more than one Stripe account record, make sure one is set as the default account. Click the field name in NetSuite to reveal the hidden field description that explains this functionality.
  6. In NetSuite, click Save.
  7. Saving the page populates values in the the related setting KEY API the related setting ID and the related setting KEY API the related setting ID fields. Copy the full value from the field that corresponds to the mode you’re working in (test mode or sandbox, or live mode or production). For example, _stripe_addon_api_key_(test OR live)_acct_1NO668BmS92e2e2e.
  8. Click View API Secrets.
  9. On the next page, click Create New. In the Create New Secret modal, paste the full value you copied in the ID field.
  10. In the Name field, enter an easily identifiable name for the API secret. You can use the same name from the New Stripe Account page, or you can add “Stripe” to the name for quick identification in the NetSuite list of API secrets.
  11. The Password and Confirm Password fields have the same value, which is an API key generated in the Stripe Dashboard. In a new browser tab, open the API keys page.
  • Create a restricted key by clicking Create restricted key .
  • Select Providing this key to another website , and then click Continue .
  • In the Name field, type “NetSuite.”
  • Copy the beginning of your NetSuite account’s URL structure from any browser tab with a NetSuite page open. Make sure you’re in the correct NetSuite account (sandbox or production). For example, https://123456.app.netsuite.com/ . Paste the value in the URL field.
  • Click Create restricted key . Copy the key beginning with rk _ test _ or rk _ live _ , and proceed to the next step below.
  1. In the NetSuite Create New Secret window, paste the API key value you copied from Stripe in the Password and Confirm Password fields.
  2. On the Restrictions tab, select the related setting FOR ALL the related setting and the related setting FOR ALL the related setting. You can optionally change or add NetSuite users in the Owners field.
  3. Click Save. Confirm that the new API secret appears in the API Secrets list. If you don’t see it, make sure you didn’t apply a filter to the list.
  4. On the Stripe Account page you created in NetSuite earlier, click Validate API Keys.
  5. Verify that the status for the the related setting KEY the related setting or the related setting KEY the related setting has changed from Pending to Ready.

Troubleshooting

A Not Ready status indicates an error in your configuration. Review the records you created and make sure everything is aligned with these instructions. Most commonly, the Stripe account ID and mode don’t match the API key you used. This is because you mismatched test mode with live mode or you copied the wrong API key from Stripe.

When the status is Ready, your Stripe account custom record setup for this Stripe Account is complete. You must repeat these steps for your other Stripe accounts that use this bundle. You can set up the other Stripe accounts now or wait until you perform the migration instructions for each account.

Next steps

Proceed with installing the workflows that pertain to your use case.

Last verified 2026-09-27

Is this helpful?