Industry practice transactions are follow-on transactions to a previous customer-initiated transaction. There are six types of Industry Practice transactions:
- Delayed charges
- Incremental charges
- Partial authorizations or partial shipments
- Reauthorizations
- Resubmissions
- No-shows
Merchant-Initiated Delayed Transaction
Delayed charge transaction is performed to process a supplemental account charge after original services have been rendered and respective payment has been processed.
Fields Specific to this Use Case
The following information is required with a standard authorization request:
- subsequentAuth–Indicate that this transaction is a merchant-initiated follow-on transaction. Set the field totrue.
- subsequentAuthReason–Include the reason for the transaction. Set the field to2.
Endpoint
Set the
ccAuthService_run
field to
true
.Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.Required Fields
- billTo_city
- billTo_country
- billTo_email
- billTo_firstName
- billTo_lastName
- billTo_postalCode
- billTo_state
- billTo_street1
- card_accountNumber
- card_expirationMonth
- card_expirationYear
- ccAuthService_run
- Set totrue.
- merchantID
- merchantReferenceCode
- purchaseTotals_currency
- purchaseTotals_grandTotalAmount
- subsequentAuth
- Set totrue.
- subsequentAuthReason
- Set to2.
- subsequentAuthTransactionID
Card-Specific Required Fields
Discover
The listed card requires additional field:
- subsequentAuthOriginalAmount
- Provide the original transaction amount.
SO Example: Merchant-Initiated Delayed Authorization Transaction
This example shows how to authorize a merchant-initiated delayed
transaction.
Request
billTo_city=Foster City billTo_country=USbillTo_email=null@cybersource.combillTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=2
Response
This example shows a sample response for a merchant-initiated
delayed transaction.
additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222
Merchant-Initiated Incremental Transaction
An incremental authorization is used to increase the total amount authorized for a
payment if the initial authorization does not cover the total cost of goods and
services. An incremental transaction is an additional amount to the original
authorization. The final authorized total includes amounts for both the initial and the
incremental authorizations.
Fields Specific to this Use Case
Include these fields with a standard authorization request:
- subsequentAuth–Set the field totrueto indicate this transaction is a merchant-initiated follow-on transaction.
- subsequentAuthReason–Set the reason field to5.
- subsequentAuthTransactionId– Provide the original transaction ID.
Endpoint
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.Required Fields
- ccIncrementalAuthService_authRequestID
- ccIncrementalAuthService_run
- Set totrue.
- merchantId
- merchantReferenceCode
- purchaseTotals_currency
- purchaseTotals_grandTotalAmount
- subsequentAuthReason
- Set to5.
- subsequentAuth
- Set totrue.
- subsequentAuthTransactionID
Card-Specific Required Fields
Discover
The listed card requires additional field:
- subsequentAuthOriginalAmount
- Provide the original transaction amount.
SO Example: Merchant-Initiated Incremental Authorization
This example shows how to authorize a merchant-initiated incremental
authorization.
Request
billTo_street1=201 S. Division St. billTo_city=Foster City billTo_country=US billTo_state=CA billTo_postalCode=94404 purchaseTotals_currency=USD card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111billTo_email=null@cybersource.combillTo_firstName=John billTo_lastName=Smith purchaseTotals_grandTotalAmount=100.00 ccIncrementalAuthService_run=true merchantID=pa_ctv_sg101 merchantReferenceCode=33557799 subsequentAuth=Y subsequentAuthTransactionID=016153570198200 ccIncrementalAuthService_authRequestID=6541079409780593413176
Response
Merchant-Initiated Reauthorization Transactions
A reauthorization occurs when the completion or fulfillment of the original order or
service extends beyond the authorized amount time limit. There are two common
reauthorization scenarios:
- Split or delayed shipments by a retailer
- Extended car rentals, hotel stays, or cruise line bookings
Fields Specific to this Use Case
Include these fields with a standard authorization request:
- subsequentAuth–Set the field totrueto indicate this transaction is a merchant-initiated follow-on transaction.
- subsequentAuthReason–Set the reason field to3.
Endpoint
Set the
ccAuthService_run
field to
true
.Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.Required Fields
- billTo_city
- billTo_country
- billTo_email
- billTo_firstName
- billTo_lastName
- billTo_postalCode
- billTo_state
- billTo_street1
- card_accountNumber
- card_expirationMonth
- card_expirationYear
- ccAuthService_run
- Set totrue.
- merchantID
- merchantReferenceCode
- purchaseTotals_currency
- purchaseTotals_grandTotalAmount
- subsequentAuthReason
- Set to3.
- subsequentAuth
- Set totrue.
- subsequentAuthTransactionID
Card-Specific Required Fields
Discover
The listed card requires additional field:
- subsequentAuthOriginalAmount
- Provide the original transaction amount.
SO Example: Merchant-Initiated Reauthorization Transaction
Request
billTo_city=Foster City billTo_country=USbillTo_email=null@cybersource.combillTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=3
Response
additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222
Merchant-Initiated Resubmission Transaction
A resubmission transaction is used when a merchant resubmits an authorization to recover
an outstanding debt from the customer. A common scenario is when a card was initially
declined due to insufficient funds, but the goods or services were already delivered to
the customer.
Specific Fields for this Use Case
Include
these fields with a standard authorization request:- subsequentAuth–
- Set the field totrueto indicate this transaction is a merchant-initiated follow-on transaction.
- subsequentAuthReason–Set the reason field to1.
Required Fields
- billTo_city
- billTo_country
- billTo_email
- billTo_firstName
- billTo_lastName
- billTo_postalCode
- billTo_state
- billTo_street1
- card_accountNumber
- card_expirationMonth
- card_expirationYear
- ccAuthService_run
- Set totrue.
- merchantID
- merchantReferenceCode
- purchaseTotals_currency
- purchaseTotals_grandTotalAmount
- subsequentAuthReason
- Set to1.
- subsequentAuth
- Set totrue.
- subsequentAuthTransactionID
Card-Specific Required Fields
Discover
The listed card requires additional field:
- subsequentAuthOriginalAmount
- Provide the original transaction amount.
SO Example: Merchant-Initiated Resubmitted Authorization Transaction
This example shows how to resubmit a merchant-initiated authorization
transaction.
Request
billTo_city=Foster City billTo_country=USbillTo_email=null@cybersource.combillTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=1
This example shows a sample response for a resubmitted merchant-initiated
authorization transaction.
Response
additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222
Merchant-Initiated No-Show Transactions
A no-show authorization occurs when a merchant charges a customer after the customer
makes a reservation, and does not show up to claim the reservation. In this situation,
the customer is charged an agreed upon fee for not showing up as expected.
Fields Specific to this Use Case
Include these fields with a standard authorization request:
- subsequentAuth–Set the field totrueto indicate this transaction is a merchant-initiated follow on transaction.
- subsequentAuthReason–Set the reason field to4.
Required Fields
- billTo_city
- billTo_country
- billTo_email
- billTo_firstName
- billTo_lastName
- billTo_postalCode
- billTo_state
- billTo_street1
- card_accountNumber
- card_expirationMonth
- card_expirationYear
- ccAuthService_run
- Set totrue.
- merchantID
- merchantReferenceCode
- purchaseTotals_currency
- purchaseTotals_grandTotalAmount
- subsequentAuthReason
- Set to4.
- subsequentAuth
- Set totrue.
- subsequentAuthTransactionID
Card-Specific Required Fields
Discover
The listed card requires additional field:
- subsequentAuthOriginalAmount
- Provide the original transaction amount.
SO Example: Merchant-Initiated No-Show Transaction
Request
billTo_city=Foster City billTo_country=USbillTo_email=null@cybersource.combillTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=4
Response
additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222