Set up Stripe-initiated payments workflows
Learn how to set up Stripe-initiated payments workflows in Stripe Connector for NetSuite.
Warning
If you are migrating from SuiteSync to Stripe Connector for NetSuite, use the migration instructions.
Before you begin
- Install the SCN Stripe App and connect it to NetSuite.
- Configure the general settings and workflows in the SCN Stripe App.
How to use this guide
- Learn more about each workflow below and select which workflows fit your use case.
- Set up and test with the instructions for each workflow you select.
Stripe-initiated payments overview
Stripe Connector for NetSuite (SCN) lets you synchronize Charges from any native Stripe account to NetSuite with a variety of workflows. The synchronization of charges is the minimum required functionality to use Deposit automation, the connector’s fully automated bank reconciliation workflow. Learn more about how charges are reconciled.
Go to Stripe App > App Settings > General to learn about Always On settings that apply to these workflows.
Configurable General tab settings supported for all workflows on this page:
| General setting | Supported configurable options | Integration design notes |
|---|
| General | NetSuite subsidiary ID | Control which subsidiaries use these workflows |
| Refunds | NetSuite-initiated refunds | Commonly used with Payment Linker and Custom Payment Application workflows |
| Bank deposits | All options | Downstream of these workflows |
| Customers | All Stripe to NetSuite customer sync options | Required configuration for these workflows |
| Currency | All options | Required if NetSuite has Multiple currencies enabled |
Workflows that sync stand-alone payments to NetSuite
Use one of these workflows if you’re creating charges and their related Customers that you want to sync to NetSuite. You can create the charges in the Dashboard, with the Stripe API, or with any Stripe integration.
Configurable General tab settings supported for stand-alone payments workflows:
| General setting | Supported configurable options | Integration design notes |
|---|
| Record sync timing | Webook events, Allowlist, Denylist | Using default webhook events is most common for this workflow |
| Workflow Default | Description | Functionality | Complexity |
|---|
| Create unapplied customer payments | Create an unapplied customer payment in NetSuite for each standalone Stripe payment created in the Stripe Dashboard, through the Stripe API, or through a third party integration with Stripe. | Basic | No-code |
Set up the Create unapplied customer payments workflow
| Workflow | Description | Functionality | Complexity |
|---|
| Create invoices for payments | Create a one-line “inferred” invoice that summarizes the total amount of the payment. A customer payment is created and applied to the NetSuite invoice, which closes it. Use this configuration when you need to post each payment to a NetSuite income account. By default, a single global item is created and reused for all invoices created from this configuration. You can customize this functionality by configuring the dynamic standalone payment item linking fields. Learn more | Standard | Configure field ids |
Set up the Create invoices for payments workflow
Workflows that apply payments to transactions in NetSuite
You can use all of the workflows in this section simultaneously, if applicable to different processes in your integration.
Configurable General tab settings supported for workflows in this section:
| General setting | Supported configurable options | Integration design notes |
|---|
| Record sync timing | Allowlist, Denylist | Allowlist is most common. Denylist is required if also using a Stripe invoice workflow simultaneously in the same Stripe account. |
| Workflow | Description | Functionality | Complexity |
|---|
| Payment Linker - upfront invoice capture | Common with third-party billing or ecommerce use cases. A Stripe charge is created by a separate system that captures payment upfront, typically during an order or billing process. The connector creates a customer payment applied to a separately created invoice in NetSuite. It requires installation and configuration of the “Stripe Connector Add-ons” SuiteBundle ID 502910. | Intermediate | Integrate systems (no-code) |
| Workflow | Description | Functionality | Complexity |
|---|
| Payment Linker - upfront sales order capture | Common with ecommerce use cases. A Stripe charge is created by a separate system that captures payment upfront, typically during an order process. The connector creates a customer deposit related to a separately created sales order in NetSuite. Requires installation and configuration of the “Stripe Connector Add-ons” SuiteBundle ID 502910. | Intermediate | Integrate systems (no-code) |
| Workflow | Description | Functionality | Complexity |
|---|
| Payment Linker - authorization capture | Common with ecommerce use cases. A Stripe payment intent is created by a separate system that creates a payment authorization, typically during an order process. After the related sales order is billed, the connector creates a customer payment and applies it to the resulting NetSuite invoice. Advanced configurations are available in the bundle. It requires installation and configuration of the “Stripe Connector Add-ons” SuiteBundle ID 502910. | Advanced | Integrate systems (no-code) |
Set up any of the Payment Linker workflows
| Workflow | Description | Functionality | Complexity |
|---|
| Create NetSuite records by metadata mapping: | Custom payment application. It allows for custom integrations if your external systems are incompatible with the payment linker. Create NetSuite payment records and apply them to an invoice or sales order by manually or programmatically adding metadata to the Stripe charge. Learn more | Custom | Most coding |
| Workflow | Description | Functionality | Complexity |
|---|
| Link NetSuite records by metadata mapping: | Custom payment application. Existing NetSuite payment records can be linked to a Stripe payment through metadata on the Stripe record. Allows for custom integrations if your external systems are incompatible with the payment linker. Learn more | Custom | Most coding |
See also
