- Introduction to Payments
- Standard Payment Processing
- Card Present Connect | Retail Processing
- Card Present Connect | Mass Transit Processing
- Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
- Airline Data Processing
- Japanese Payment Options Processing
- Processing Payments Using Credentials
- Using Stored Customer Credentials During a CIT
- Merchant-Initiated Delayed Transaction with PAN
- Merchant-Initiated Incremental Transaction with PAN
- Merchant-Initiated No-Show Transactions with PAN
- Merchant-Initiated Reauthorization Transactions with PAN
- Merchant-Initiated Resubmission Transaction with PAN
- Installment Payments
- Recurring Payments
- Token Management Service Processing
When the customer purchases a product that is not yet available, you can request two
authorizations and a capture. You will first request an authorization to ensure that funds are
available, and then you ship the available products. After the remaining products become
available, you will request follow-on authorization to ensure funds are still available. You
will 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.Step 1: Requesting an authorization
You will 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, you request a follow-on authorization to ensure that
funds are still available. The follow-on authorization request must include the
link-to-request field in addition to the basic fields required for every authorization
request. The link-to-request field in an authorization request triggers the split-shipment
functionality.
Set the link-to-request field to the request ID from the value returned in
the endpoint.
Field specific to requesting a follow-on authorization request:
First Authorization Response: The value is returned in the endpoint.
Follow-on Authorization
Request:
processingInformation.linkId=
Step 3:
Cybersource
attempts to link the follow-on authorization request
to the first authorization- If the link-to-request value is valid, the follow-on authorization is linked to the original authorization in the Business Center and in reports.
- If the link-to-request value is not valid, the follow-on authorization is not linked to the original authorization in the Business Center and in reports.
Step 4: Requesting a capture
You ship the product and request a capture. The capture request requires
only the basic fields as any capture request.
Step 5:
Cybersource
attempts to link the capture request to the other
transactions- If the link-to-request 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 link-to-request 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.