Payment Events

On the Billing subtab of a sales order, the Payment subtab displays a list of all payment event activity that has happened for the order with the most recent event at the top of the list. Each payment event has a link to view the payment event details. Payment event details include the request information, the response for the request, the payment status, and the raw transmission details.

Use the Payment subtab to review the summary information about the gateway communication requests and responses, such as the payment event, the result, and reason for the result. Drill down for full payment event details, including the response code, authorization code, address verification (AVS) and card security code (CSC) results, payment status, and the raw request and response transmission details.

Populating the invoice_number in the Request Details for MerchantE

If you select a MerchantE credit card processing profile, the invoice_number parameter is always populated in the request NetSuite sends to the gateway. Depending on the page where you record the customer payment, this parameter is populated by one of the following fields:

• On a Sales Order page:

  • PO#

  • Order#

  • Internal ID

  If the PO# field is empty, the parameter uses Order#. If the Order# field is empty, the parameter uses the internal ID of the record. For more information on the internal ID, see Finding Internal IDs of Records

• On an Invoice page or on a Customer Payment page:

  • PO#

  • Invoice#

  • Internal ID

  If the PO# field is empty, the parameter uses the Invoice#. If the Invoice# is empty, the parameter uses the internal ID of the record.

• On a Cash Sale page:

  • Check#

  • Sale#

  • Internal ID

  If the Check# field is empty, the parameter uses Sale#. If the Sale# field is empty, the parameter uses the internal ID of the record.

• On a Customer Deposit page:

  • Deposit#

  • Internal ID

  If the Deposit# field is empty, the parameter uses the internal ID of the record.

• On a Customer Refund page, the parameter uses the internal ID of the record.

Populating Level III Item Data with CyberSouce Decision Manager

If you use a CyberSource processing profile with Decision Manager enabled, line-level data is populated in the request NetSuite sends to the gateway. This includes the product name, product code, item name, and others. You can view these details in the Raw Request section of the payment event.

The following table lists some of the parameters populated in the request and their corresponding item fields.

Note:

The populated data vary depending on the transaction type.

Payment Event Parameter *	Item Field	Notes
item_#_productName	Display Name/Code
item_#_productSKU	Item Name/Number
item_#_productCode	UPC Code	If the UPC Code field is empty, item_#_productCode takes the value default.
item_#_productRisk	Fraud Risk	If the Fraud Risk field is empty, item_#_productRisk is not populated in the payment event.
* In the payment event, the # mark is replaced by a number that indicates the order of the line item.

Important:

With CyberSource Decision Manager, line-level data is sent only for the authorization request. To send line-level data with capture and sale requests, you must have the Purchase Card Data feature enabled. For more information, see Accepting Purchase Cards (Level II and Level III Credit Cards).

Understanding the P/N Ref. Field

The P/N Ref. field contains an identifier of the a request that NetSuite sends to a payment gateway. This identifier is unique. You can use this identifier to inquiry about a certain request at the gateway’s back office.

When NetSuite sends a request that references another request, NetSuite includes the P/N Ref. of the original request. For example, when NetSuite sends a capture request, the P/N Ref. of the original authorization request is included.

You can enter or edit a P/N Ref. manually to record requests that happened outside of NetSuite. To enter or edit a P/N Ref. manually, you must check the CC Approved box. For more information, see Recording Payment Events that Happened Outside of NetSuite.

Recording Payment Events that Happened Outside of NetSuite

To keep a record of authorizations or other payment transactions that happened outside of NetSuite, you can create cash sales, sales orders, or other payment transactions and manually enter the P/N Ref. and other payment details on the Payment subtab.

To record payment events for these transactions without the Payment Instruments enabled, you must check the CC Approved box. If you do not check the CC Approved box, a payment event is not created for the transaction, and the payment details are not preserved on the transaction. If you check the CC Approved box, you must provide either a payment card number or a P/N Ref identifier.

If you enable the Payment Instruments, the Handling mode field replaces the functionality of checking the Charge Credit Card and CC Approved boxes. Select Record External Event to create a NetSuite record of a payment event that took place outside of NetSuite, for example in an ecommerce solution that authorizes payments outside of NetSuite.

Note that although the Charge Credit Card and CC Approved fields are no longer visible on the transaction after you enable Payment Instruments, the fields remain available for scripting.

For information on other handling modes, see the help topic Using the Handling Mode Field.

Viewing Gateway Asynchronous Notifications

During payment processing, the communication between NetSuite and a payment gateway is sometimes asynchronous. For example, some alternative payment methods that use external checkout require asynchronous processing. The gateway can also send an asynchronous request to NetSuite to update the voiding status of a transaction.

To view a list of asynchronous notifications received from payment gateways, go to Transactions > Management > View Gateway Asynchronous Notifications.

Related Topics:

• Payment Card Number Security and Compliance
• Using CyberSource Decision Manager for Fraud Management
• Setting Up Customer Credit Card Soft Descriptors
• Maintaining Recurring Credit Card Payments
• Managing Payment Holds
• Viewing Customer Credit Card Transactions
• Setting Up Customer Credit Card Processing
• Transitioning to a New Gateway and Disabling the Old Gateway

• Credit Card Processing Gateway FAQ

• Customer Credit Card Processing

General Notices