Refunds
Overview
A refund, also known as a follow-on credit, returns the payment amount from a completed capture or sale transaction. A refund is linked to the original transaction and requires the capture or sale request ID. This differs from a stand-alone credit, which does not require a prior transaction.
Supported Processors
Supported processors: Chase Paymentech Solutions, Elavon, FDC Nashville Global, UATP,
Supported processors: Chase Paymentech Solutions, FDC Nashville Global,
Endpoints
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor
Set the ccCreditService_run field to true, and set ccCreditService_captureRequestID to the request ID returned in the capture or sale response.
Processor-Specific Refund Information
Chase Paymentech Solutions
When you use a Diners Club card, you must also include airlineData_leg_#_flightNumber in addition to the required fields.
Elavon
When you use a Diners Club card, you must also include airlineData_leg_#_flightNumber in addition to the required fields.
airlineData_customerCode is optional only for Diners Club and Discover card types.
FDC Nashville Global
FDC Nashville Global does not require any fields beyond the default required fields for a refund.
UATP
You must request a refund within 180 days of the original capture or sale.
You must include a valid ticket document number in one of these fields:
airlineData_ticketNumber: set the value to the ticket number, which can be up to 12 digits. appends this value with your 3-digit International Air Transport Association (IATA) merchant code to send a 15-digit ticket document number to UATP.ccCreditService_reconciliationID: set this value to your 3-digit IATA merchant code followed by the ticket number, which can be up to 12 digits, for a total of 15 digits.
If you include both fields in the request, and you use the reconciliation ID for your own reconciliation rather than the ticket document number, you must set the value for airlineData_ticketNumber as described and ensure that the first three digits of the reconciliation ID do not include your IATA code.
Visa Platform Connect
Visa Platform Connect also requires billing and card fields for a refund: billTo_city, billTo_country, billTo_email, billTo_firstName, billTo_lastName, billTo_postalCode, billTo_state, billTo_street1, card_accountNumber, card_expirationMonth, and card_expirationYear.
Processor-Specific Refund Information
Chase Paymentech Solutions
When you use a Diners Club card, you must also include airlineData_leg_#_flightNumber in addition to the required fields.
FDC Nashville Global
FDC Nashville Global does not require any fields beyond the default required fields for a refund.
Visa Platform Connect
also requires billing and card fields for a refund: billTo_city, billTo_country, billTo_email, billTo_firstName, billTo_lastName, billTo_postalCode, billTo_state, billTo_street1, card_accountNumber, card_expirationMonth, and card_expirationYear.
Required Fields
Default Required Fields
ccCreditService_captureRequestID: set to the capture ID.ccCreditService_run: set the value totrue.merchantIDmerchantReferenceCode: set to themerchant_ref_numbervalue used in the corresponding capture request.purchaseTotals_currencypurchaseTotals_grandTotalAmount
Optional Fields
You can use these optional fields to include additional airline data with a refund:
airlineData_agentCodeairlineData_agentNameairlineData_arrivalDateairlineData_carrierNameairlineData_clearingCountairlineData_clearingSequenceairlineData_creditReasonIndicatorairlineData_customerCodeairlineData_documentType: for a list of possible values, see Airline Data Codes.airlineData_electronicTicketairlineData_exchangeTicketAmountairlineData_exchangeTicketFeeairlineData_numberOfPassengersairlineData_passengerName: value format:lastname/firstname.airlineData_purchaseType: set to one of these values:01(payment is for an airline ticket) or02(payment is for an ancillary purchase).airlineData_reservationSystem: available for Visa only.airlineData_restrictedTicketIndicatorairlineData_ticketIssueDateairlineData_ticketIssuerCityairlineData_ticketNumberairlineData_ticketRestrictionTextairlineData_ticketUpdateIndicatorairlineData_totalClearingAmountairlineData_totalFee
These optional fields apply to a ticket purchase and support up to four travel legs (airlineData_leg_#_*):
airlineData_leg_#_arrivalTimeairlineData_leg_#_arrivalTimeSegmentairlineData_leg_#_carrierCodeairlineData_leg_#_classairlineData_leg_#_conjunctionTicketairlineData_leg_#_couponNumberairlineData_leg_#_departureDateairlineData_leg_#_departureTimeairlineData_leg_#_departureTimeSegmentairlineData_leg_#_destinationairlineData_leg_#_endorsementsRestrictionsairlineData_leg_#_exchangeTicketairlineData_leg_#_fareairlineData_leg_#_fareBasisairlineData_leg_#_feeairlineData_leg_#_flightNumberairlineData_leg_#_originatingAirportCodeairlineData_leg_#_stopoverCodeairlineData_leg_#_tax
UATP Required Fields
airlineData_passengerNameairlineData_ticketNumber: see the ticket document number requirement.ccCreditService_reconciliationID: see the ticket document number requirement.
Required Fields
also requires these billing and card fields: billTo_city, billTo_country, billTo_email, billTo_firstName, billTo_lastName, billTo_postalCode, billTo_state, billTo_street1, card_accountNumber, card_expirationMonth, and card_expirationYear.
<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.86"> <merchantID>merchantID</merchantID> <merchantReferenceCode>merchantRefCode</merchantReferenceCode> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>149.00</grandTotalAmount> </purchaseTotals> <ccCreditService run="true"> <captureRequestID>captureRequestID</captureRequestID> </ccCreditService> <airlineData> <ticketNumber>987612345678</ticketNumber> <passengerName>John Doe</passengerName> </airlineData></requestMessage><c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.86"> <c:merchantReferenceCode>Postman-1666641056</c:merchantReferenceCode> <c:requestID>6666410568976150003010</c:requestID> <c:decision>ACCEPT</c:decision> <c:reasonCode>100</c:reasonCode> <c:purchaseTotals> <c:currency>USD</c:currency> </c:purchaseTotals> <c:ccCreditReply> <c:reasonCode>100</c:reasonCode> <c:requestDateTime>2026-10-24T19:50:57Z</c:requestDateTime> <c:amount>149.00</c:amount> <c:reconciliationID>6691571329CM5P99</c:reconciliationID> <c:authorizationCode>831111</c:authorizationCode> <c:processorResponse>00</c:processorResponse> <c:paymentNetworkTransactionID>222222222222222</c:paymentNetworkTransactionID> </c:ccCreditReply></c:replyMessage>Thanks for your feedback!
Last published: September 29, 2026