Processing Two Authorizations and a Capture for Multiple Products {#payments-processing-basic-split-ship-two-auth-cap-intro}
============================================================================================================================

When the customer purchases a product that is not yet available, you can request two authorizations and a capture. First request an authorization to ensure that funds are available, and then ship the available products. After the remaining products become available, request follow-on authorization to ensure funds are still available. Ship the remaining products, and request a capture. `Cybersource` links the follow-on authorization to the first authorization and the capture request to the other transactions.

#### Figure:

Processing Two Authorizations and a Capture for Multiple Products  
![](/content/dam/documentation/cybs/en-us/topics/payments-processing/card-processing/payments/images/payments-ss-scenario-two.svg/jcr:content/renditions/original)  
**Step 1: Requesting an authorization**  
Request an authorization to ensure that funds are available for one or more of the products that are available for immediate shipment. The authorization request requires no additional fields or requirements than a basic authorization.  
**Step 2: Requesting a follow-on authorization**  
After the product becomes available, request a follow-on authorization to ensure that funds are still available. The follow-on authorization request must include the requestID field in addition to the basic fields required for every authorization request. The requestID field in an authorization request triggers the split shipment functionality.  
Set the field to the value from the requestID field from the first authorization's response.  
**Field specific to requesting a follow-on authorization request:**  
First Authorization Response Message: `requestID=SWVdPS5IM`  
Follow-on Authorization Request: `linkToRequest=SWVdPS5IM`  
**Step 3: `Cybersource` attempts to link the follow-on authorization request to the first authorization**

* If the value is valid, the follow-on authorization is linked to the original authorization in the `Business Center` and in reports.
* If the value is not valid, the follow-on authorization is not linked to the original authorization in the `Business Center` and in reports.

{#payments-processing-basic-split-ship-two-auth-cap-intro_ul_nvp_44z_wwb}  
**Step 4: Requesting a capture**  
You ship the product and request a capture. The capture request must include the request ID in addition to the basic fields required as any capture request.  
**Field Specific to Processing a Capture after a Requesting a Follow-on Authorization:**  
Follow-on Authorization Response Message: `requestID=sl39cmdSlkJ`  
Capture Request: `authRequestID=sl39cmdSlkJ`  
**Step 5: `Cybersource` attempts to link the capture request to the other transactions**
* If the authRequestID value for the capture is valid, all three transactions (first authorization, follow-on authorization, capture) are linked together in the `Business Center` and in reports.
* If the authRequestID value for the capture is not valid, the follow-on authorization and capture are linked to each other in the `Business Center` and in reports, but they are not linked to the first authorization.
  See [Basic Authorization](/docs/cybs/en-us/payments/developer/ctv/so/payments/payments-processing-basic-intro/payments-processing-basic-auth-intro.md "") for information on how to process a basic authorization. See [Capture](/docs/cybs/en-us/payments/developer/ctv/so/payments/payments-processing-basic-intro/payments-processing-basic-capture-intro.md "") for information on how to process a capture.

