NetSuite B2B Payments with Stripe
Allow customers to pay NetSuite invoices and Sales Orders using a secure payment form. Use this form in emails, NetSuite-generated invoice PDFs, or manual outreach.
This workflow enables customers to pay NetSuite invoices and Sales Orders using a credit card, debit card, bank transfer (ACH), or European payment methods. This workflow is helpful for companies that have open invoices in NetSuite that are collected on using a manual process (check, phone, etc). This workflow can also be used to accept deposits on SalesOrders.
This payment form handles payment processing, cash application, cash reconciliation, and fee calculation.
Here's how it works:
- A field is added to each NetSuite invoice and/or Sales Order linking to a SuiteSync-hosted payment form
- The customer is sent the payment form link in an email, NetSuite-generated PDF invoice, etc
- The customer pays the NetSuite invoice (or SalesOrder) using the payment form
- The payment is pushed to NetSuite and applied against the corresponding invoice
- The payment is reconciled against the corresponding deposit. Processing fees are calculated and recorded.
- Disputes and refunds are handled as well.
Here are some cases where this is helpful:
- You have a quote-to-order to process in a separate system (like SalesForce) and send the order to NetSuite for collection. You are looking for a way to automate collecting on these invoices.
- You have a system that creates Invoices directly in NetSuite and you need a way to enable customers to pay these off.
- You have large invoices (or SalesOrders) where you would like to offer customers the option to pay with a bank transfer instead of a credit card.
Here’s an example of how the customer-facing page looks:
Here are some details:
- Bank transfer (ACH) payments are only supported for USD payments
- The payment link is generated immediately when a NetSuite Invoice or Sales Order is created, regardless of how it is created. For example, the payment link is present on invoices created through a CSV import, API integration, or manually through the NetSuite GUI.
- Customer payment information can be saved for future use in the auto-bill workflow. This is an optional feature.
- After the invoice is fully paid, the invoice payment link ceases to work. This prevents accidental double payment for invoices.
- The payment link is generated and available immediately after the invoice is created. You can use rely on the payment link field for any workflows or SuiteScripts immediately after the payment is saved.
- There are some customizations required to your NetSuite account in order to setup this form, which are detailed out here. If you create new transaction forms, take a look at the documentation to ensure the correct fields are set on the form.
- Invoices with less due than the Stripe processing minimum display an error page.
- Payments for Invoices are always captured immediately. There's an optional feature to authorize payments for Sales Orders instead of capturing immediately.
Deposits on SalesOrders
If a payment is processed for a SalesOrder it is created as a CustomerDeposit associated with the SalesOrder. When the SalesOrder is billed in NetSuite, an Invoice is created, and the deposit is automatically applied to the invoice.
There's an option available to authorize a charge (instead of capturing the charge up front) for a SalesOrder. This authorized charge can then later be captured using the auth-capture workflow
Refunds can be issued for payments received directly within the NetSuite interface. Learn more about issuing refunds.
Storing Payment Credentials for Future Use
There's an optional feature available that stores collected payment credentials for future use. A checkbox is added to the payment form which allows the customer to elect to save their payment credentials for future use.
Here's how this feature works:
- If the NetSuite customer is linked to a Stripe customer, payment credentials are added to that pre-existing Stripe customer.
- If the NetSuite customer is not linked to a Stripe customer, a new Stripe customer is created. The NetSuite customer is linked to this newly created Stripe customer.
- If no default payment source exists on the Stripe customer, the new payment credentials are set to be the default payment source.
- If the previous default payment credentials failed to successfully charge during an automatic billing workflow, the new payment credentials are set to be the new default payment method.
PCI Compliance and Security Considerations
All credit card, debit card, and bank account information is securely handled and stored via Stripe. SuiteSync’s systems, and your systems, are not in scope for PCI compliance.
The payment form is secured using HTTPS and is only available while the invoice is open (unpaid). By default, we display the email associated with the invoice on the form, but this can be disabled if this is a security concern to your business.
Stripe offers the ability to automatically send email receipts for payments. SuiteSync leverages this functionality, passing the invoice ID and NetSuite customer email over to Stripe to enable email receipts to be sent.
Testing Email Receipts
Email receipts are not sent in sandbox (test mode). In order to test receipts in test mode, you'll need to trigger the receipts manually in the Stripe dashboard.
Batch Payments Based on Invoice Due Date
SuiteSync can auto-pay NetSuite invoices based on the invoice due date using stored payment methods in Stripe.
Multiple Customer Currencies
The payment form is fully multi-currency aware. The payment in Stripe is created in the currency of the NetSuite Invoice, and the currency shown to the user changes based on the NetSuite Invoice currency and amount.
In addition, certain payment methods are automatically hidden if they are not available for a specific currency. For instance, ACH is only available for accounts tied to a US entity whose payments are in USD. The ACH bank transfer option is automatically hidden when these two conditions are not present.
You can customize the email and phone displayed at the bottom of the payment form, by editing your public Stripe information. Here are the elements that can be customized using Stripe:
- Company name
You can also customize some other aspects of the form through query strings. This enables you to dynamically change the content of form for each user. For instance, if you want to only allow ACH payment information based on customer information or logic contained in your NetSuite instance you can do so by appending query string parameters to the link.
Here are the options that are available:
card=falseThis disables credit card payments for the form.
store=trueThis defaults the checkbox which allows the user to store card information to checked.
There are additional customization options available. Contact us for a demo to walk through your specific use case.
Once your payment form is setup, you can test paying NetSuite invoices with either credit cards or ACH payments using the following payment details:
Credit or Debit Card
Card number: 4242 42424 4242 4242
Bank to use: PNC
Security question: tomato
How failures are handled
What if a processing a customers credit card fails?
If a customer's credit card fails to process, the invoice is not paid off and the user is notified immediately and asked to enter in valid payment credentials.
The form is reporting that the invoice is invalid or paid, but it's neither. What is going on?
The form reports that message to the user if there are some other issues with your setup.
Here are some other things to check if the form is failing:
- Valid NetSuite credentials
- Valid Stripe credentials
- For Invoices, the field "Amount Due" (sometimes called Amount Remaining) must be present on the form. Here's how to check this.
- The total on the invoice is less than 50 cents