Payment Instruments Records

After you enable the Payment Instruments feature, the following four records become available:

The ACH record provides the following fields:

Limit – The limit is the dollar amount limit per transaction for the account.
Bank Account Number – The bank account number consists of up to 20 digits.
Account Type – The account type distinguishes between checking, corporate checking, and savings accounts.
Routing Number – The routing number consists of nine digits.
Bank Name – The bank name is the name of the bank.
Account Owner Name – The account owner name is the name of the account owner.
Customer Consent – Customer consent is the customer consent message to be included with all ACH transactions using the account.

The Payment Card record provides the following fields:

Payment Card Number - Payment Card Number, or primary account number (PAN), consists of of 8 to 19 digits that identify a card.
Expiration Date - The card expires on the last day of the month that is specified as the Expiration Date in the MM/YY format. For example, a card with an expiration date 03/17 expires on March 31, 2017.
Card Brand - Card Brand is a compulsory field that specifies the card issuer.
Card Type - The Card Type optional field distinguishes between a credit card and a debit card for informational purposes only.
Cardholder Name - NetSuite enters the cardholder name from the default credit card on the customer's record

If the field contains no value or the wrong value, check the customer's record at Lists > Relationships > Customers. On the Financial subtab of the customer's record, verify that the Cardholder Name field contains the correct information.

Depending on the merchant, providing this information may make the transaction cheaper or less risky.
Card Street - NetSuite enters the street address from the customer's billing address, which is used in the address verification service (AVS).

If the field contains no value or the wrong value, check the customer's record at Lists > Relationships > Customers. On the Address subtab of the customer's record, verify that the default billing address contains the correct street address

Depending on the merchant, providing this information may make the transaction cheaper or less risky.

The Payment Card Token record provides the following fields:

Token - The Token field contains the alphanumeric string of the token. The string is issued by a payment gateway and has no extrinsic value.
Token Expiration Date - When issuing a token, the payment gateway can set the Token Expiration Date, which limits the token validity.

The way expired tokens are handled depends on the payment gateway.

If the token does not expire or has the same expiration date as the payment card that the token represents, then leave this field blank.
Token Family - Token Family is supplementary information that is set by the payment gateway to group similar tokens under the same label.

Consequently, tokens issued by one gateway are not offered to a profile of another gateway. Using the Token Family field helps avoid unwanted charge attempts.
Token Namespace - The payment gateway can use the Token Namespace field to identify the merchant account that issued a token. On the Payment Processing Profile, merchants can enable charging only tokens with a Token Namespace value that identifies a certain merchant.
Issuer Identification Number - The Issuer Identification Number (IIN), previously known as bank identification number (BIN), is the first six to nine digits of a payment card number.

The General Token record provides the following field:

Supported Operations - The Supported Operations field defines available operations for a retained general token.

For example, Automated Clearing House (ACH) does not support authorizations. Billing agreement from a common eWallet enables you to perform the authorization, sale, and capture operations.