NetSuite Payment Method To iPaaS.com Mapping Documentation

A NetSuite payment method can be captured into iPaaS.com as a payment method. The integration records the method name and a description and derives the iPaaS.com payment type from the NetSuite method type (for example, credit/debit card, or A/R for offline methods). Payment methods are a reference record used when transactions carry payments.

ID Format

Manual Sync ID Format

Enter the NetSuite payment method's internal ID on the Manual Sync page.

External ID Format

iPaaS.com records the NetSuite payment method's internal ID as the external-ID link, so later transfers update the existing payment method rather than creating a duplicate.

Deleted Record Support

There is a Delete NetSuite Payment Method TO iPaaS.com collection that removes the linked iPaaS.com payment method when the NetSuite method is deleted (driven by the external-ID link), when the corresponding delete event is enabled.

Mapping Collection Status

Status: Enabled (a single Add/Update collection).
Trigger Events: Create and Update. Captured on demand from Manual Sync and on the payment-method events enabled in Inbound Data Flows (see NetSuite Connections and Settings).

Duplicate or Conflicting Mappings

None. A single Add/Update collection captures payment methods.

Supported Child Collections

None.

System Caveats

iPaaS.com Caveats

Payment Method data type. This collection populates the iPaaS.com Payment Method entity.
Payment type is derived. The iPaaS.com payment type is computed from the NetSuite method type: a Payment Card becomes Credit Card (or Debit Card when flagged as a debit card), an Offline method becomes A/R, and any other method type passes through by name.

Setup Requirements

Inbound Data Flows + webhook scripts — enable the NetSuite payment-method events for automatic capture.

Authentication

The integration authenticates to NetSuite using the connection configured for the integration; the webhook scripts that emit NetSuite events are documented in NetSuite Connections and Settings.

Integration Flow

A NetSuite payment method is captured — on demand (internal ID) or on payment-method events when Inbound Data Flows and the webhook scripts are in place.
The integration creates or updates the iPaaS.com payment method with its name and a derived payment type and description.

Mappings

Add/Update NetSuite Payment Method TO iPaaS.com

iPaaS.com data type: Payment Method

Captures a NetSuite payment method into an iPaaS.com payment method.

Mapping Type	Source Field (NetSuite)	Destination Field (iPaaS.com)	Description
Field	Name	Name	Required. The payment method name.
Dynamic Formula	`if(MethodType_RefName != "Offline"){ if(MethodType_RefName == "Payment Card"){ if(IsDebitCard) return "Debit Card"; return "Credit Card"; } return MethodType_RefName; } else{ return "A/R"; }`	PaymentType	Required. The iPaaS.com payment type derived from the NetSuite method type (Credit/Debit Card, A/R for offline, or the method type name).
Dynamic Formula	`MethodType_RefName + " is the Payment Type from the NetSuite"`	Description	Optional. A human-readable description noting the source NetSuite method type.

Error Handling

None specific to this collection.

Testing & Validation

Test Scenarios

Capture a card method. Manually sync a NetSuite Payment Card method and confirm the iPaaS.com payment type is Credit Card (or Debit Card when flagged).
Capture an offline method. Confirm an Offline method maps to payment type A/R.

Validation Checklist

Payment methods referenced by transaction payments are established in iPaaS.com.

Additional Notes

Known limitations are collected in NetSuite Known Limitations.