How to configure payment processing for carry orders line flow

A) Creating Carry lines in Sterling.
Refer below Technote.
 Creating Order with Delivery Method CARRY in API Tester
 https://www.ibm.com/support/pages/creating-order-delivery-method-carry-api-tester

B) What are Carry lines ?
Carry lines are also called as "take" lines. These are designed for the customer who wants to visit the store and take or carry the items along with him. Customer can pay the bill there itself on the counter by cash, credit or debit card and so on.

C) Carry lines and Authorization
Since customer is visiting the store in person, so direct charging happens on his credit card, and no authorization is required in this case. So for Carry lines product does not create or process or support Authorization.

D) Order with mix lines
Order can be created with a Carry line and a SHP line together. If payment method is there on order, then payment agents would create Authorization only for SHP line. SHP line CHARGE's would be created using this Authorization. Carry line CHARGE's created would not use SHP line Authorizations.
Online or in store customer can also choose to CHARGE the order full upfront without any Authorizations. In this case in person or not in person CHARGE's both can be used by Carry and non Carry lines. For CHARGE's product support in person to not in person match and vice a versa.

E) More about Carry lines
 yfs_charge_transaction DB table stores payment-related information. Each entry of Carry line would have in_person = "Y" in this DB table. In this DB table for Carry lines, we populate postponed_amount.
postponed_amount is the amount for which Authorizations are not required.

F) LightInvoice attribute under createOrderInvoice API for Carry lines
 This attribute is present at order level and not at line level. The idea is that this invoice is created only for carry lines, so all lines under this invoice should be carry. So there is no need to add this at line level. If we try to create a non-Carry line invoice when LightInvoice="Y", then it throws error.

G) Invoicing Carry lines and non-Carry lines together.
As of now invoicing Carry lines and SHP lines is not supported in the product. Carry and non-Carry lines needs to be invoiced separately.

H) Payment collection agent or API cannot create CHARGE for Carry lines as Carry lines are in person lines. processOrderPayments API needs to be run by Store Assistant manually to create CHARGE for Carry line.