1. Commerce
  2. SuiteCommerce InStore (SCIS)
  3. SCIS 2.0 Release Guides
  4. SCIS 2.0 Payment Processing Comparison With SCIS 1.0

SCIS 2.0 Payment Processing Comparison With SCIS 1.0

Use this topic to compare payment–processing differences between SuiteCommerce InStore (SCIS) 1.0 and the refactored flows enabled using SCIS 2.0.

Single Payment

This payment type uses a single form of tender, such as cash or a credit card.

In SCIS 1.0

Cash Sale record is staged in application memory. Payment for items is tendered. Cash Sale is used to generate an Invoice and the Invoice is submitted. Then Customer Payment is created, submitted, and applied to the Invoice. Receipt is generated and displays.

For additional information about processing single payments using SCIS 1.0, see Cash Sales.

With SCIS 2.0

SCIS cart is ready with these records staged in application memory:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Begin transaction:

  1. Items are ready to be tendered.

  2. Payment is tendered.

  3. Payment is added to Customer Deposit.

Submit transaction:

  1. Customer Deposit with payment is submitted.

  2. Receipt is generated and displays.

    Customer interaction is complete.

Note:

To prevent delaying customer, receipt generation is not dependent on completing record submissions.

Prepare new records for next transaction:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Complete transaction in background:

  1. Sales Order is used to generate an Invoice.

  2. Sales Order is used to generate a Fulfillment Request and Store Pickup Fulfillment for the items.

  3. Payment from existing Customer Deposit is applied to Invoice.

Split Payment

Split payments involve two or more tenders, such as cash and an EMV-enabled credit card.

In SCIS 1.0

Cash Sale record is staged in application memory. First payment for items is tendered. Cash Sale is used to generate an Invoice and the Invoice is submitted. Then first Customer Payment is created, submitted, and applied to the Invoice.

Second payment is tendered. Second Customer Payment is created, submitted, and applied to the Invoice. Receipt is generated and displays.

For additional information about processing split payments using SCIS 1.0, see Invoices.

With SCIS 2.0

SCIS cart is ready with these records staged in application memory:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Begin transaction:

  1. Items are ready to be tendered.

  2. First payment is tendered.

  3. Payment is added to Customer Deposit.

  4. Second payment is tendered.

  5. Payment is added to the Customer Deposit.

    A new Customer Deposit is created for each partial payment. Process continues until total payments equal amount due.

Submit transaction:

  1. Customer Deposit with payments is submitted.

  2. Receipt is generated and displays.

    Customer interaction is complete.

Note:

To prevent delaying customer, receipt generation is not dependent on completing record submissions.

Prepare new records for next transaction:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Complete transaction in background:

  1. Sales Order is used to generate an Invoice.

  2. Sales Order is used to generate a Fulfillment Request and Store Pickup Fulfillment for the items.

  3. Payment from existing Customer Deposit is applied to Invoice.

Shipping or Pickup Order Payment

This payment type covers transactions where a purchase is shipped to the customer or delivered to the store and held for customer pickup.

In SCIS 1.0

Cash Sale record is staged in application memory. Payment is tendered and applied to Cash Sale. Sales Order is manually created using information from Cash Sale record. This Cash Sale record is then discarded. Sales Order is billed using:

  • New Cash Sale if tendered in full as a single payment

  • Invoice if tendered using multiple payments

Receipt is generated and displays.

For additional information about processing shipping or pickup order payments using SCIS 1.0, see Orders for Delivery.

With SCIS 2.0

SCIS cart is ready with these records staged in application memory:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Begin transaction:

  1. Items are ready to be tendered.

  2. Payment is tendered.

  3. Payment is added to Customer Deposit.

    If split-payment, a new Customer Deposit is created for each payment. This process continues until total payments equal amount due.

Submit transaction:

  1. Customer Deposit with payment is submitted.

  2. Receipt is generated and displays.

    Customer interaction is complete.

Note:

To prevent delaying customer, receipt generation is not dependent on completing record submissions.

Prepare new records for next transaction:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Complete transaction in background:

  1. Sales Order with the items is submitted.

  2. Sales Order is used to generate an Invoice.

    • If Invoice in Advance of Fulfillment enabled, the Invoice is created and payment is applied to the Invoice.

    • If Invoice in Advance of Fulfillment is disabled, Customer Deposit is applied to the Sales Order.

  3. Payment from existing Customer Deposit is applied to Invoice or Sales Order, based on:

    • If Invoice in Advance of Fulfillment is enabled, payment from existing Customer Deposit is applied to Invoice.

    • If Invoice in Advance of Fulfillment is disabled, payment from existing Customer Deposit is applied to Sales Order.

  4. Fulfillment process occurs:

    • If items are marked to be shipped, a fulfillment request is created.

    • If items are marked to be picked up on location (cash and carry), the order is automatically fulfilled.

Exchange Without Additional Payment

Rather than receive a cash or credit card refund, a customer can request an item exchange. This payment type covers transactions where the item being returned and the item received in exchange are the same price.

Tip:

With the exception of validating the return, the payment flows for validated and unvalidated exchanges are the same.

In SCIS 1.0

SCIS cart is ready with Cash Sale record staged in application memory. Return is validated and tendered. Cash Sale is used to generate an Invoice and the Invoice is submitted. Return items are added to a Credit Memo, with the memo applied to an Invoice and submitted. Receipt is generated and displays.

For additional information about processing exchanges without an additional payment using SCIS 1.0, see Refund by Exchange.

With SCIS 2.0

SCIS cart is ready with these records staged in application memory:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Begin transaction:

  1. Return is validated and items are ready to be tendered.

  2. Return items are added to Credit Memo.

  3. Exchange items are added to Sales Order.

  4. Payment of $0.00 is tendered.

Submit transaction:

  1. Sales Order is submitted.

  2. Credit Memo is submitted.

  3. Receipt is generated and displays.

    Customer interaction is complete.

Note:

To prevent delaying customer, receipt generation is not dependent on completing record submissions.

Prepare new records for next transaction:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Complete transaction in background:

  1. New Sales Order is created for next transaction.

  2. Sales Order is used to generate an Invoice.

  3. Credit Memo is applied to the Invoice.

Exchange With Additional Payment

This type of exchange occurs when the item being returned is priced less than the item received in exchange. In this scenario, the customer must tender payment to cover the price and tax difference.

Tip:

With the exception of validating the return, the payment flows for validated and unvalidated exchanges are the same.

In SCIS 1.0

SCIS cart is ready with Cash Sale record staged in application memory. Return is validated and payment is tendered. Cash Sale is used to generate an Invoice and the Invoice is submitted.

Return items are then added to a Credit Memo, with the memo applied to the Invoice and submitted. Customer Payment is created, submitted and applied to the Invoice. Receipt is generated and displays.

For additional information about processing exchanges with an additional payment using SCIS 1.0, see Refund by Exchange.

With SCIS 2.0

SCIS cart is ready with these records staged in application memory:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Begin transaction:

  1. Return is validated and items are ready to be tendered.

  2. Return items are added to Credit Memo.

  3. Exchange items are added to Sales Order.

  4. Payment equal to the difference of return items and exchange items is tendered.

Submit transaction:

  1. Sales Order is submitted.

  2. Credit Memo is submitted.

  3. Customer Deposit with payment is submitted.

  4. Receipt is generated and displays.

    Customer interaction is complete.

Note:

To prevent delaying customer, receipt generation is not dependent on completing record submissions.

Prepare new records for next transaction:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Complete transaction in background:

  1. Sales Order is used to generate an Invoice.

  2. Credit Memo is applied to the Invoice.

  3. Payment from existing Customer Deposit is applied to Invoice.

Refund Payment

A refund is given when a customer returns an item without receiving another item in exchange. The customer is given the amount that they paid for the returned item.

Tip:

With the exception of validating the return, the payment flows for validated and unvalidated refunds are the same.

In SCIS 1.0

SCIS cart is ready with Cash Sale record staged in application memory. Return is validated and refund is tendered. Cash Sale is used to generate an Invoice and the Invoice is submitted. Return items are then added to a Credit Memo, with the memo applied to the Invoice and submitted.

Credit Memo is applied to a Customer Refund. Customer is provided the refund amount. Receipt is generated and displays.

For additional information about processing refund payments using SCIS 1.0, see Validated Returns.

With SCIS 2.0

SCIS cart is ready with these records staged in application memory:

  • Credit Memo

  • Customer Deposit

  • Sales Order

Begin transaction:

  1. Return is validated and items are ready to be tendered.

  2. Refund payment is tendered.

Submit and complete transaction:

  1. Return Authorization is created.

  2. Return items are added to Return Authorization.

  3. Return Authorization is used to populate Credit Memo.

  4. Credit Memo is submitted.

  5. Customer Refund is created and submitted and linked to the Credit Memo.

  6. Receipt is generated and displays.

    Customer interaction is complete.

Note:

To prevent delaying customer, receipt generation is not dependent on completing record submissions.

Hold unused records for next transaction;

  • Customer Deposit

  • Sales Order

Prepare new record for next transaction:

  • Credit Memo

Related Topics

SCIS 2.0 Reliability, Performance, and Refactored Processing
SCIS 2.0 Frequently Asked Questions
SCIS 1.0 to 2.0 Upgrade Checklist
SCIS 2.0 Enabling a Mobile Device

General Notices