1. Commerce
  2. SuiteCommerce InStore (SCIS)
  3. SCIS Administrator Guide
  4. SCIS Configuration
  5. Setting Up Payment Services for SCIS
  6. Understanding Payment-device Processing

Understanding Payment-device Processing

This section provides an overview of the SuiteCommerce InStore (SCIS) flow used to tender credit card and other payments made through an EMV-enabled payment device.

It also covers the Payment Result Preview (PRP) feature you can use to reduce the time spent waiting for a payment to complete.

Payment Processing Flow

This diagram and corresponding steps illustrate how SCIS and NetSuite interact to process payments. Because processes can be customized or include options, the information is intended as a general overview.

  6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          

  1. Select payment device

    The sales associate uses SCIS to select a payment device. SCIS displays an informational message to the sales associate, indicating the payment device is being initialized.

  2. Request for payment

    The request for payment occurs between SCIS and the NetSuite account. At this time, a transaction record is created in NetSuite. SCIS begins to send requests for payment status periodically to the transaction record created in NetSuite.

  3. Initiate Plugin

    It is through the transaction record that the request for payment reaches the payment partner plugin. The payment partner plugin receives the request and starts communication with the payment partner gateway, if a gateway is configured. Alternately, the request goes directly to the payment device.

  4. Request for payment

    The payment partner plugin sends a request to the payment partner for payment device initialization and sends the request for the payment.

  5. Initialize PIN pad

    SCIS displays an informational message to the sales associate, "waiting for customer payment."

    Next, the shopper interacts with the payment device. If a payment gateway is configured, then data is exchanged between the payment device and the gateway. This communication is not monitored by SCIS.

  6. Payment confirmation

    The payment partner sends payment confirmation to NetSuite, and then the transaction record is updated. Through its continual requests, SCIS discovers the confirmed payment status. The sales transaction in SCIS is complete.

Payment Result Preview Processing

This processing boosts performance for credit card and other payments made through an EMV-enabled payment device.

Standard EMV payment processing creates and updates a transaction record in NetSuite. One update is saving the payment Pending status. Saving the Pending status occurs before processing the Accept or Reject result from the payment partner. This intermediate step can delay tendering a payment and providing a receipt.

Preview processing creates a Payment Result Preview (PRP) record in addition to the transaction record. The preview posts the Accept or Reject status from the payment partner without waiting for the Pending status to save in NetSuite. The PRP record uses fewer fields than a transaction record and does not execute scripts or work flows, so it is quicker to update.

Payment Result Preview Status

Payment Partner Setup

To realize the benefits of PRP processing, the payment partner handling your device-based payments must configure their processes to use the PRP record. If your payment partner is not configured, then the time to complete a payment will include waiting for the Pending status to save.

Role Setup

To include PRP processing when tendering payment, the sales associate or other employee performing the transaction must have View Payment Result Previews permitted in their role assignment. The SCIS Clerk role includes that permission by default, but custom roles usually require updating.

If an associate takes an EMV payment without this permission in their role, the behind-the-scenes processing includes the standard wait for NetSuite to save the Pending status.

Important:

To enable PRP at the point–of–sale (POS), the associate performing a transaction must have View Payment Result Previews permitted to their role. Review and update the roles you use at the POS, including your custom roles.

Assigning View Payment Result Previews to a role:

  1. Go to Setup > Users/Roles > Manage Roles.

  2. Locate the role and click Edit.

  3. Under the Permissions subtab, look for View Payment Result Previews.

  4. If View Payment Result Previews is not listed:

    1. Begin entering View Payment Result Previews.

    2. Select View Payment Result Previews.

    3. Click Add.

    Assigning Payment Result Previews

  5. If you made changes, click Save. Otherwise, click Cancel.

For more information about working with roles, see SCIS Roles and Permissions.

Reviewing Payment Result Preview Records

You can review the PRP records created for prior transactions through a Saved Search. The records are not viewable through the Transactions tab.

In NetSuite, go to Lists > Search > Saved Searches > New. Choose Payment Result Preview as the Search Type.

Related Topics

SCIS Configuration
Configuring SCIS Gateway Records
Configuring EMV Payment Services for SCIS
Configuring SCIS Payment Methods

General Notices