If your NetSuite customer records already hold a payment provider's customer identifier, Kolleno can read it during the customer synchronization and link that customer automatically. Once linked, Kolleno pulls in the payment methods the customer already holds with that provider, so mandates and cards created outside Kolleno appear in the app with no manual matching.
Supported payment service providers
Each provider has its own identifier, read from the NetSuite field you nominate:
Provider | Value read from NetSuite |
Stripe | stripe_customer_id |
Adyen | adyen_shopper_reference |
GoCardless | gocardless_customer_id |
What happens once the identifier is read
When the identifier first appears on a customer, or changes, Kolleno refreshes that customer's payment methods with the provider:
GoCardless: every mandate and bank account belonging to that payer is pulled. Active and pending mandates then appear under the customer's Payment Methods tab, in the Bank accounts column.
Stripe: saved cards and mandates are pulled.
Adyen: stored payment details are pulled.
There is no date limit on this pull, so payment methods set up long before you joined Kolleno are picked up as well.
How it is set up
Contact Kolleno support with the NetSuite field internal ID of the field that holds the identifier. Here is how to find it: Find a NetSuite field internal ID.
The mapping works for both standard customer records and billing account records, so let support know which applies to your NetSuite setup.
Setting codes, for reference when contacting Kolleno support: netsuite_custom_fields_customer and netsuite_customer_additional_fields_mapping.
Options
Which NetSuite field is used
Any NetSuite field that is readable by search can be the source, identified by its internal ID. We recommend a dedicated custom field rather than a general-purpose field such as Comments.
The mapping is two-way. Kolleno can also write the identifier back into the same field when it creates a payment provider customer for you, which is covered in Automatic write of PSP customer ID to a NetSuite. Using a shared free-text field for the identifier therefore risks that value being overwritten or cleared.
The field must be exposed to NetSuite search
Kolleno reads the field through a NetSuite search query. If the field is not available for search in your NetSuite account, the customer synchronization cannot read it and stops returning customer updates altogether. If customer data stops refreshing shortly after a new field is added, raise it with support so the field can be checked.
Clearing the field
If the identifier is removed from the NetSuite field, Kolleno treats the customer as no longer linked and marks their stored mandates or cards as removed. Leave the field populated unless you intend to unlink the customer.
Customers that are not changing in NetSuite
The routine synchronization only re-reads a customer record when that record changes in NetSuite. To bring identifiers in for customers that are otherwise untouched, ask support to run a full customer resynchronization.
If the identifiers are not held in NetSuite at all, a one-off spreadsheet import is available instead: One-Time GoCardless Customer ID Bulk Import.