API Fields SCMP
API Fields SCMP
API Fields SCMP
Cybersource Corporation (Cybersource) furnishes this document and the software described in this document under the applicable agreement between the reader of this document (You) and Cybersource
(Agreement). You may use this document and/or software only in accordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the information contained in this document is subject
to change without notice and therefore should not be interpreted in any way as a guarantee or warranty by Cybersource. Cybersource assumes no responsibility or liability for any errors that may appear in this
document. The copyrighted software that accompanies this document is licensed to You for use only in strict accordance with the Agreement. You should read the Agreement carefully before using the software.
Except as permitted by the Agreement, You may not reproduce any part of this document, store this document in a retrieval system, or transmit this document, in any form or by any means, electronic, mechanical,
recording, or otherwise, without the prior written consent of Cybersource.
For Government or defense agencies: Use, duplication, or disclosure by the Government or defense agencies is subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 and in similar clauses in the FAR and NASA FAR Supplement.
For civilian agencies: Use, reproduction, or disclosure is subject to restrictions set forth in subparagraphs (a) through (d) of the Commercial Computer Software Restricted Rights clause at 52.227-19 and the
limitations set forth in Cybersource Corporation's standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States.
Trademarks
Authorize.Net, eCheck.Net, and The Power of Payment are registered trademarks of Cybersource Corporation. Cybersource, Cybersource Payment Manager, Cybersource Risk Manager, Cybersource Decision Manager,
and Cybersource Connect are trademarks and/or service marks of Cybersource Corporation. Visa, Visa International, Cybersource, the Visa logo, and the Cybersource logo are the registered trademarks of Visa
International in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners.
Identifier for the issuing bank that provided the customer’s encoded account number.
This field is supported only on Chase Paymentech Solutions. Contact the processor to obtain the bank’s ID.
Specifications
• Data Length: 3
Mapping Information
Specifications
• Data Length: 15
Mapping Information
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_acs_transaction_id response field.
Specifications
• Data Length: 36
Mapping Information
Additional amount.
Specifications
• Data Length: 12
Mapping Information
Specifications
• Data Length: 3
Mapping Information
Specifications
Mapping Information
• Japanese issuers
• Credit Mutuel-CIC—the value returned in this field is a processor transaction ID required for troubleshooting. The associated detail error code is in the auth_auth_response
field or the auth_reversal_auth_response field, depending on which service you requested.
Specifications
• Credit Mutuel-CIC:
◦ Data Length: 36
◦ Data Length: 3
Fee the issuer charges when the recipient’s currency is not the same as the sender’s currency. When this fee is charged, the grand total amount must include the fee.
Specifications
• Data Length: 12
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Fee you are charging for the transaction. When this fee is charged, the grand total amount must include the fee.
Specifications
• Data Length: 12
Mapping Information
Flag for a mass transit transaction that indicates whether the authorization is aggregated.
Possible values:
• Y: Aggregated
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 150-151
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
FDC Compass
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 95-105
Specifications
• Data Type:
• Data Length:
◦ Cielo: 11
◦ FDC Compass: 20
◦ Getnet: 11
◦ Rede: 11
◦ Software Express: 20
Mapping Information
◦ ccAuthService_aggregatorID
◦ ccCaptureService_aggregatorID
◦ ccCreditService_aggregatorID
◦ octService_aggregatorID
FDC Compass
Getnet
This value must consist of uppercase letters. Special characters are not allowed.
The value for this field does not map to the TC 33 capture file.
Specifications
• Type: String
• Length:
◦ American Express Direct: Maximum length of the aggregator name depends on the length of the sub-merchant name. The combined length for both values must not
exceed 37 characters.
◦ FDC Compass: Maximum length of the aggregator name depends on the length of the sub-merchant name. The combined length for both values must not exceed 37
characters.
◦ Software Express: 37
◦ Visa Platform Connect: With American Express, the maximum length of the aggregator name depends on the length of the sub-merchant name. The combined length
for both values must not exceed 36 characters. Not used with other card types.
Mapping Information
◦ ccAuthService_aggregatorName
◦ ccCaptureService_aggregatorName
◦ ccCreditService_aggregatorName
International Air Transport Association (IATA) code for the carrier for this leg of the trip.
Payer Authentication
Payer Authentication services only use the first leg of the trip.
Specifications
• Data Type:String
• Data Length:2
Mapping Information
International Air Transport Association (IATA) code for the destination airport for this leg of the trip.
Payer Authentication
Payer Authentication services only use the first leg of the trip.
Specifications
• Data Length: 5
Mapping Information
Format: YYYYMMDD.
Payer Authentication
The numbered element name should contain 0 instead of #. Payer Authentication services only use the first leg of the trip.
Specifications
• Data Length: 8
Mapping Information
International Air Transport Association (IATA) code for the originating airport for the first leg of the trip.
Specifications
• Data Length: 5
Mapping Information
If you do not include this field in your request, Cybersource uses a default value of 1.
Specifications
• Data Length: 3
Mapping Information
If there are multiple passengers, include all listed on the ticket. Do not include special characters such as commas, hyphens, or apostrophes. Only ASCII characters are supported.
Specifications
• Data Length: 60
Mapping Information
If there are multiple passengers, include all listed on the ticket. Do not include special characters such as commas, hyphens, or apostrophes. Only ASCII characters are supported.
Specifications
• Data Length: 60
Mapping Information
Important:
Do not confuse this offer-level field with the alternate_tax_amount order-level field.
Mastercard: Tax amount collected for a special type of tax. Do not set this field to 0 (zero).
Specifications
• Data Length: 13
Worldpay VAP
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
OmniPay Direct
• Data Length: 12
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Important:
Do not confuse this order-level field with the alternative_tax_amount offer-level field.
The total should not include the local tax amount (tax_amount field) and national tax (national_tax field) incluced in the total tax (tax_amount field).
GPN
Specifications
• Data Length: 10
• Data Length: 12
FDC Compass
• Data Length: 10
• Data Length: 11
GPN
• Data Length: 12
• Data Length: 10
Mapping Information
The following list the processors using this field and the corresponding processor field name:
A flag that indicates whether an alternative tax amount (alternate_tax_amount) is included in the request.
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
Elavon Americas
• Data Length: 15
• Data Length: 15
• Data Length: 15
• Data Length: 15
Worldpay VAP
• Data Length: 20
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 15
FDC Compass
• Data Length: 15
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
OmniPay Direct
This rate is used to generate the value of the alternate_tax_amount Offer-level field.
Whe you include the alternate_tax_amount Offer-level field or the national_tax request field, do not include the alternate_tax_rate field. The national_tax request field rate will
be set using the following equation:
Specifications
• Data Length: 5
• Data Length: 5
OmniPay Direct
• Data Length: 4
Worldpay VAP
• Data Length: 8
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
For Mastercard: flag that defines tax categories for domestic processing in certain locations.
Specifications
• Data Length: 4
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Possible values:
• 00: unknown
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
These fields provide a description to display on the customer’s American Express card statement. When you provide TAA fields, start with amexdata_taa1, then ...taa2, and so on.
Skipping a TAA field causes subsequent TAA fields to be ignored.
Before using these fields, contact customer support to have your account enabled for this feature.
Releated Inforamation
Specifications
This field is supported for the following Level II and Level III transactions:
• Data Length: 40
• Data Length: 40
FDC Compass
• Data Length: 40
• Data Length: 40
Worldpay VAP
• Data Length: 26
◦ amexdata_taa1
◦ amexdata_taa2
◦ amexdata_taa3
◦ amexdata_taa4
◦ invoiceHeader_amexDataTAA1
◦ invoiceHeader_amexDataTAA2
◦ invoiceHeader_amexDataTAA3
◦ invoiceHeader_amexDataTAA4
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
◦ TAA1
◦ TAA2
◦ TAA3
• FDC Compass:
◦ TAA1
◦ TAA2
◦ TAA3
◦ TAA4
◦ amexDataTAA1
◦ amexDataTAA2
◦ amexDataTAA3
◦ amexDataTAA4
This value cannot be negative. You can include a decimal point (.), but you cannot include any other special characters. The amount is truncated to the correct number of decimal
places.
Important: Some processors have specific requirements and limitations, such as maximum amounts and maximum field lengths.
Important: Visa Platform Connect limits authorization and capture amounts to 999999999999 (twelve 9s).
Set this field to the converted amount that was returned by the DCC provider. You must include either this field or grand_total_amount in a request.
If your processor supports zero amount authorizations, you can set this field to 0 for an authorization to find out whether the card is lost or stolen.
Specifications
GPN
• Data Length: 10
JCN Gateway
• Data Length: 10
Other Processors
• Data Length: 15
Mapping Information
Authorized amount.
Specifications
• Data Length: 15
Mapping Information
Specifications
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Specifications
Mapping Information
Service
Specifications
Mapping Information
Possible value:
Specifications
• Data Length: 15
Mapping Information
Code from the alternative payment processor that describes why the authorization is pending or failed.
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Request ID of the authorization for which you are requesting this service.
Specifications
• Data Length: 26
Mapping Information
◦ apAuthReversalService_authRequestID
◦ apCaptureService_authRequestID
Specifications
• Data Length: 5
Mapping Information
Authorized amount.
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Possible values:
Specifications
• Data Length: 15
Mapping Information
Code from the alternative payment processor that describes why the authorization reversal is pending or failed.
Specifications
• Data Length: 5
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Possible values:
Specifications
• Data Length: 15
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Specifications
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Authorized amount.
Specifications
• Data Length: 15
Mapping Information
Possible values:
Specifications
• Data Length: 15
Mapping Information
Code from the alternative payment processor that describes why the capture is pending or failed.
Specifications
• Data Length: 5
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Transaction identifier (TID) that is used to identify and track a transaction throughout its life cycle.
Specifications
• Data Length: 15
Mapping Information
Possible values:
Specifications
• Data Length: 15
Mapping Information
Code from the alternative payment processor that describes why the request is pending or failed.
Specifications
• Data Length: 5
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Request ID of the authorization, authorization reversal, capture, sale, or credit service for which you are requesting the check status service.
Specifications
• Data Length: 26
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Possible values:
• ABANDONED
• FAILED
• PENDING
• REFUNDED
• REFUND_INITIATED
• REFUND_REJECTED
• RETURNED
• SETTLED
• SETTLEMENT_ACCEPTED
• SETTLEMENT_INITIATED
• SETTLE_REJECTED
Specifications
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Example:
option0=id:1^name:Currency
option1=id:2^name:USD
option2=id:3^name:Minimum Amount
option3=id:4^name:1.00
option4=id:5^name:Maximum Amount
option5=id:6^name:1000.00
Specifications
• Data Length: 34
Mapping Information
Example:
option0=id:1^name:Currency
option1=id:2^name:USD
option2=id:3^name:Minimum Amount
option3=id:4^name:1.00
option4=id:5^name:Maximum Amount
option5=id:6^name:1000.00
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 3
Mapping Information
The maximum number of options to be retrieved from the processor and displayed to the consumer.
Possible values: 1-250.
Specifications
• Data Length: 3
Mapping Information
Offset from the first item in the list of options received from the processor.
If you want to display the options in multiple lists, this number represents the first option displayed in each list. Possible values: 0-9999
Specifications
• Data Length: 4
Mapping Information
Offset from the first item in the list of options received from the processor.
If you want to display the options in multiple lists, this number represents the first option displayed in each list. Possible values: 0-9999
Specifications
• Data Length: 4
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Possible values:
Specifications
• Data Length: 3
Mapping Information
Authorized amount.
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Possible values:
Specifications
• Data Length: 15
Mapping Information
Code from the alternative payment processor that describes why the refund is pending or failed.
Specifications
• Data Length: 5
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Request ID of the sale or capture for which you are requesting the credit service.
Specifications
• Data Length: 26
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 32
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Transaction identifier (TID) that is used to identify and track a transaction throughout its life cycle.
Specifications
• Data Length: 15
Mapping Information
Authorized amount.
Specifications
• Data Length: 15
Mapping Information
Specifications
Mapping Information
Specifications
Mapping Information
Service
Specifications
Mapping Information
Possible values:
Specifications
• Data Length: 15
Mapping Information
Code from the alternative payment processor that describes why the sale is pending or failed.
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Service
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Specifications
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 12
Mapping Information
Specifications
• Data Length: 5
Mapping Information
This field is returned only when the processor sends this value.
Possible values:
• positive
• negative
Specifications
• Type: String
• Length: 8
Mapping Information
Type of account.
Authorization
Possible values:
Specifications
• Type: String
• Length: 2
Mapping Information
Affluence indicator.
On Chase Paymentech Solutions, this field is returned for Visa, Mastercard, Discover, and Diners Club.
This information enables you to market high cost items to these customers and to understand the kinds of cards that high income customers are using.
Possible values:
Worldpay VAP
Flag that indicates whether a Visa customer or Mastercard customer is in one of the affluent categories.
Possible values:
• AFFLUENT: High income customer with high spending pattern (>100k USD annual income and >40k USD annual card usage).
◦ Type: String
◦ Length: 1
• Worldpay VAP:
◦ Type: String
◦ Length: 13
Mapping Information
Type of amount.
• 02: Current available balance, which is typically the ledger balance minus outstanding authorizations. Some depository institutions also include pending deposits and the
credit or overdraft line associated with the account.
Specifications
• Type: String
• Length: 2
Specifications
• Data Length: 15
Mapping Information
AVS result.
Specifications
• Type: String
• Length: 1
Mapping Information
Authorization code.
This field is returned only when the processor sends this value.
Specifications
• Type: String
• Length: 7
Mapping Information
This field is returned only when the processor sends this value.
Important: Do not use this field to evaluate the result of the request.
AIBMS
When this value is 08, you can accept the transaction if the customer provides you with identification.
Atos
This value is the response code sent from Atos and it might also include the response code from the bank.
Format: aa,bb with the two values separated by a comma and where:
Comercio Latino
This value is the status code and the error or response code received from the processor separated by a colon.
Example: 2:R06
Processor-defined detail error code. The associated response category code is in the additional_processor_response field.
Specifications
• JCN Gateway:
◦ Data Length: 3
Mapping Information
Specifications
• Length: 20
Mapping Information
This field is returned only when the processor sends this value.
Important: Do not use this value to evaluate the AVS result. Use this value only when debugging your order management system.
Specifications
• Data Length: 10
Mapping Information
Format: MMDD
Specifications
• Data Length: 4
Mapping Information
Card category.
GPN
GPX
Possible values:
• B: Business card.
• O: Noncommercial card.
• R: Corporate card.
• S: Purchase card.
Important: Before using this field on Worldpay VAP, you must contact customer support to have your account configured for this feature.
Specifications
◦ Data Length: 3
• GPN:
◦ Data Length: 3
• GPX:
◦ Data Length: 3
◦ Data Length: 1
• Worldpay VAP:
◦ Data Length: 7
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Possible values:
• B: Business card.
• R: Corporate card.
• S: Purchasing card.
• 0: Noncommercial card.
Specifications
• Data Length: 1
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
This field is returned only for Visa, Mastercard, Discover, Diners Club, JCB, and Maestro (International) on Chase Paymentech Solutions.
This information enables you to determine whether the card was issued domestically or internationally.
Specifications
• Data Length: 3
Mapping Information
This field indicates whether the card is eligible for Level III interchange fees.
This field is returned only for Visa and Mastercard on Chase Paymentech Solutions.
Possible values:
• N: No, the card is not eligible for Level III interchange fees.
Specifications
• Data Length: 1
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
This field indicates whether the card is supported for PINless debits.
This field is returned only for Visa and Mastercard on Chase Paymentech Solutions.
Possible values:
Specifications
• Data Length: 1
Mapping Information
This information enables you to determine when a gift card or prepaid card is presented for use when establishing a new recurring, installment, or deferred billing relationship.
Possible values:
Specifications
• Data Length: 1
Mapping Information
This field indicates whether the card is regulated according to the Durbin Amendment.
This field is returned only for Visa, Mastercard, Discover, Diners Club, and JCB on Chase Paymentech Solutions.
When a card is regulated according to the Durbin Amendment, it means that the issuer has assets that exceed 10B USD and is subject to price caps and interchange rules.
Possible values:
Specifications
• Data Length: 1
Mapping Information
This information enables you to alter the way an order is processed. For example, you might not want to reauthorize a transaction for a signature debit card, or you might want to
perform reversals promptly for a signature debit card.
Possible values:
Specifications
• Data Length: 1
Mapping Information
Mapped response code for American Express SafeKey, RuPay PaySecure, or Visa Secure.
Important: a value of 0 for a Visa transaction indicates that Visa downgraded the transaction. When Visa approves an authorization and downgrades it, you are liable for
the transaction. To confirm the downgrade, look at the e-commerce indicator for the transaction in the Business Center. You can proceed with the transaction if you want to
accept liability. If you do not want to accept liability, reverse the authorization, attempt to authenticate the customer again, and request another authorization.
Important: Visa downgraded the transaction. When you receive an authorization approval and the CAVV response code
is 0, you are liable for the transaction. To confirm the downgrade, look at the e-commerce indicator for the transaction in the
Business Center. You can proceed with the transaction if you want to accept liability. If you do not want to accept liability,
reverse the authorization, attempt to authenticate the customer again, and request another authorization.
Specifications
• Data Length: 3
Mapping Information
CAVV response code sent directly from the processor for American Express SafeKey, RuPay PaySecure, or Visa Secure.
Specifications
• Data Length: 3
Mapping Information
Authorization code.
Authorization Service
Authorization code you received from an authorization that you performed outside the system.
Capture Service
Specifications
• Authorization:
◦ Data Length: 6
• Capture:
◦ JCN Gateway:
Data Length: 7
Data Length: 6
Mapping Information
◦ ccAuthService_verbalAuthCode
◦ ccCaptureService_verbalAuthCode
CVN Codes
Code Description
D The transaction was determined to be suspicious by the issuing bank.
I The CVN failed the processor's data validation check.
M The CVN matched.
N The CVN did not match.
P The CVN was not processed by the processor for an unspecified reason.
S The CVN is on the card but was not included in the request.
U Card verification is not supported by the issuing bank.
X Card verification is not supported by the payment card company.
1 Card verification is not supported for this processor or card type.
2 An unrecognized result code was returned by the processor for the card verification response.
3 No result code was returned by the processor.
Specifications
• Data Length: 1
This field is returned only when the processor sends this value.
Important: Do not use this value to evaluate the CVN result. Use this value only when debugging your order management system.
Specifications
• Data Length: 11
Mapping Information
Indicates whether the authorization request was delayed because connectivity was interrupted.
Possible values:
• Y: Deferred authorization
The value for this field corresponds to the following data in the TC 33 capture file:
◦ Position: 160-163
◦ Position: 150-151
Specifications
• Data Length: 1
Mapping Information
• Positions 1-3: Fraud score. This value ranges from 001 to 998, where 001 indicates the least likely fraudulent transaction and 998 indicates the most likely fraudulent
transaction.
• Positions 4-5: Reason code that specifies the reason for the fraud score. Possible values:
◦ 19: Score forced to be 001 because the transaction being scored was a 04xx message.
◦ 24: Suspicious recent ATM activity or suspicious ATM activity following a recent abnormal activity.
• Data Length: 32
Mapping Information
Raw electronic verification response code from the processor for the customer’s email address.
Specifications
• Data Length: 1
Mapping Information
Mapped electronic verification response code for the customer’s email address.
Specifications
• Type: String
• Length: 1
Mapping Information
Raw electronic verification response code from the processor for the customer’s last name.
Specifications
• Data Length: s1
Mapping Information
Specifications
• Data Length: 1
Mapping Information
Raw electronic verification response code from the processor for the customer’s phone number.
Specifications
• Data Length: 1
Mapping Information
Mapped electronic verification response code for the customer’s phone number.
Specifications
• Data Length: 1
Mapping Information
Raw electronic verification response code from the processor for the customer’s postal code.
Specifications
• Data Length: 1
Mapping Information
Mapped electronic verification response code for the customer’s postal code.
Specifications
• Data Length: 1
Mapping Information
Raw electronic verification response code from the processor for the customer’s street address.
Specifications
• Data Length: 1
Mapping Information
Mapped electronic verification response code for the customer’s street address.
Specifications
• Data Length: 1
Mapping Information
Flag that specifies whether this transaction is the first in a series of recurring payments.
This field is supported only on Atos, FDC Nashville Global, and OmniPay Direct.
Possible values:
• N (default): No, this is not the first payment in a series of recurring payments.
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 32
Mapping Information
This field is not returned for unmarked authorizations. Some processors that support the final authorization indicator do not send this field.
• 0: Preauthorization.
• 1: Final authorization.
• 0: Preauthorization.
• 1: Final authorization.
• 2: Undefined authorization.
Specifications
Mapping Information
Possible values:
• 0: Preauthorization.
• 1: Final authorization.
The default for Barclays and Elavon is 1 (final authorization). To change the default for this field, contact customer support.
When the value for this field is 0, it corresponds to the following data in the TC 33 capture file:
• Position: 164
When the value for this field is 1, it does not correspond to any data in the TC 33 capture file.
Specifications
• Data Length: 1
Mapping Information
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for a Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 140-143
Specifications
• Data Length: 4
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 128-139
Specifications
• Data Length: 12
Mapping Information
Amount funded.
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 48-59
Specifications
• Data Length: 12
Mapping Information
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 60-63
Specifications
• Data Length: 4
This field is returned only for Mastercard installment payments on Visa Platform Connect in all countries except Croatia and Georgia.
Brazil
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26-37
Greece
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 23-34
Other Countries
The value for this field corresponds to the following data in the TC 33 capture file:
Specifications
• Data Length: 12
Mapping Information
This field is returned only for Crediario installment payments in Brazil on Visa Platform Connect.
This field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario installment payments in
Brazil.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 158-164
Specifications
• Data Length: 7
Mapping Information
This field is returned only for two kinds of installment payments on Visa Platform Connect:
• Crediario with Visa in Brazil: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for
Crediario installment payments.
Brazil
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 151-157
Other Countries
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 58-62
Specifications
• Data Length: 7
Mapping Information
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 76-79
Specifications
• Data Length: 4
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 64-75
Specifications
• Data Length: 12
Mapping Information
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 92-95
Specifications
• Data Length: 4
This field is returned only for two kinds of installment payments on Visa Platform Connect:
• Crediario with Visa in Brazil: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for
Crediario installment payments.
Brazil
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 80-91
Other Countries
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 46-57
• Data Length: 12
Mapping Information
This field is returned only for Mastercard installment payments on Visa Platform Connect in all countries except Brazil, Croatia, Georgia, and Greece.
The issuer provides this value when the first installment payment is successful.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 23-34
Specifications
Mapping Information
This field is returned only for Mastercard installment payments on Visa Platform Connect in Greece.
Format: YYMMDD
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 102-107
Specifications
• Data Length: 6
Mapping Information
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 124-127
Specifications
• Data Length: 4
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 112-123
Specifications
• Data Length: 12
Mapping Information
This field is returned only for installment payments with Mastercard on Visa Platform Connect in all countries except Brazil, Croatia, Georgia, and Greece.
The issuer provides this value when the first installment payment is successful.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 77-78
Specifications
• Data Length: 2
Mapping Information
This field is returned only for installment payments with Mastercard on Visa Platform Connect in all countries except Brazil, Croatia, Georgia, and Greece.
The issuer provides this value when the first installment payment is successful.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 75-76
Specifications
• Data Length: 2
Mapping Information
This field is returned only for two kinds of installment payments on Visa Platform Connect:
• Crediario with Visa in Brazil: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for
Crediario installment payments.
Brazil
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 144-150
Other Countries
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 41-45
Specifications
• Data Length: 7
Mapping Information
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 108-111
Specifications
• Data Length: 4
This field is returned only for two kinds of installment payments in Brazil on Visa Platform Connect:
• Crediario with Visa: this field is included in the authorization response for the Crediario eligibility request when the issuer approves the customer's request for Crediario
installment payments.
• Mastercard.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 96-107
Specifications
• Type: Decimal
• Data Length: 12
Mapping Information
This field is returned only for installment payments with Mastercard on Visa Platform Connect in all countries except Croatia, Georgia, and Greece.
Brazil
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 8-19
Other Countries
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 5-16
Specifications
Mapping Information
This field is returned only for installment payments with Mastercard on Visa Platform Connect in all countries except Brazil, Croatia, Georgia, and Greece.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 20-22
Specifications
• Data Length: 2
Mapping Information
Flag that specifies whether to request that the processor use least-cost routing for the transaction.
When the request includes this field, this value overrides the information in your account.
Possible values:
• Y: Request that the processor use least-cost routing for the transaction
• N (default): Do not request that the processor use least-cost routing for the transaction
Specifications
• Data Length: 1
Mapping Information
Possible values:
• 03: Do not try again. Obtain another type of payment from the customer.
• 04: Problem with a token or a partial shipment indicator. Do not try again.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 96-99
• Data Length: 2
Mapping Information
For some processors, this field is used only for Mastercard. For other processors, this field is used for Visa and Mastercard. And for other processors, this field is not implemented.
Possible values:
• 03: Do not try again. Obtain another type of payment from the customer.
• 04: Problem with a token or a partial shipment indicator. Do not try again.
Specifications
• Data Length: 2
Merchant ID that was used to create the subscription or token for which the service was requested.
Specifications
• Data Length: 30
Mapping Information
Flag that specifies whether to enable the transaction for partial authorization.
When a request includes this field, this value overrides the information in your account. Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 164
Specifications
• Data Length: 1
Possible values:
◦ Incorrect Mastercard POS entry mode. The Mastercard POS entry mode should be 81 for an authorization or authorization reversal.
◦ Incorrect Mastercard POS entry mode. The Mastercard POS entry mode should be 01 for a tokenized request.
• U: Expired token.
• W: Primary account number (PAN) listed in electronic warning bulletin. This field is returned only for Visa Platform Connect.
• Data Length: 1
Mapping Information
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 133-134
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 2
You can use this value to identify a specific transaction when you are discussing the transaction with your processor. Not all processors provide this value.
For Cielo, this value is the non-sequential unit (NSU) and is returned for all transactions. Cielo or the issuing bank generates the value.
For Credit Mutuel-CIC, this value is the proof of sale or non-sequential unit (NSU) number. The Cielo acquirer, Rede acquirer, or issuing bank generates the value.
For Visa Platform Connect, the following values are returned for each card type:
• American Express: American Express generates this value. It is included in all replies from the American Express Global Network (AEGN).
• Mastercard: This value is the qualification information for the Mastercard Interchange Compliance (MIC) program. It is used for all Mastercard responses coming from
Banknet through Visa to certified acquirers. Format:
◦ Bits 8-13: Banknet reference number generated by Mastercard for each transaction
• Visa and Other Card Types: The payment card company generates this value. It is unique for each original authorization and identifies a transaction throughout its life cycle.
For GPN, the following values are returned for each card type:
• ◦ American Express: The payment card company generates this value. This value is saved and sent to the processor in all subsequent capture requests.
◦ Discover: The payment card company generates this value. This value is saved and sent to the processor in all subsequent requests for full authorization reversals and
captures.
▪ Bits 1-9: Banknet reference number generated by Mastercard for each transaction
◦ Visa: The payment card company generates this value. This value is saved and sent to the processor in all subsequent requests for full authorization reversals and
captures.
Specifications
Credit Mutuel-CIC:
• Data Length: 20
Elavon:
• Data Length: 22
• Data Length: 15
Mapping Information
This field is returned only for Redecard in Brazil for Cybersource Latin American Processing. This field is returned only when the personal ID result is returned by the processor.
If you included personal_id in the request, this value indicates whether personal_id matched a value in a record on file.
Possible values:
• Y: Match
• N: No match
• K: Not supported
• U: Unknown
• Z: No response returned
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Specifications
• Data Length: 1
Cybersource generates this value, which consists of a series of codes that identify terminal capability, security data, and specific conditions present at the time the transaction
occurred. To comply with the CAPN requirements, this value must be included in all subsequent follow-on requests, such as captures and follow-on credits.
When you perform authorizations, captures, and credits through Cybersource, Cybersource passes this value from the authorization service to the subsequent services for you.
However, when you perform authorizations through Cybersource and perform subsequent services through other financial institutions, you must ensure that requests for captures
and credits include this value.
Specifications
• Data Length: 12
Mapping Information
This field is returned only for Cielo, Cybersource Latin American Processing, and Moneris.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Moneris
This value identifies the transaction on a host system. It contains the following information:
• Batch number
You must store this value. If you give the customer a receipt, display this value on the receipt.
• Terminal ID = 66012345
Specifications
◦ Data Length: 50
• Moneris:
◦ Data Length: 18
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
This field is returned only for Visa Platform Connect and Ingenico ePayments.
Ingenico ePayments
Unique number that Cybersource generates to identify the transaction. You can use this value to identify transactions in the Ingenico ePayments Collections Report, which
provides settlement information. Contact customer support for information about the report.
Specifications
• Data Length: 20
Mapping Information
Give this number to American Express when you call them for a verbal authorization.
Specifications
• Data Length: 6
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Request ID of the authorization for which you are requesting this service.
Specifications
• Data Length: 26
Mapping Information
◦ ccAuthReversalService_authRequestID
◦ ccCaptureService_authRequestID
◦ ccCheckStatusService_authRequestID
◦ ccIncrementalAuthService_authRequestID
Request token for the authorization for which you are requesting this service.
This value is an encoded string that contains no confidential information, such as an account number or card verification number.
Specifications
Mapping Information
◦ ccAuthReversalService_authRequestToken
◦ ccCaptureService_authRequestToken
Specifications
• Data Length: 15
Mapping Information
Authorization code.
This field is returned only when the value is sent by the processor.
Specifications
• Data Length: 6
Mapping Information
This field is returned only when the processor sends this value.
Important: Do not use this field to evaluate the result of the request.
JCN Gateway
Processor-defined detail error code. The associated response category code is in the additional_processor_response field.
Specifications
• JCN Gateway:
◦ Data Length: 3
◦ Data Length: 10
Specifications
• Data Length: 32
Mapping Information
Possible values:
◦ Incorrect Mastercard POS entry mode. The Mastercard POS entry mode should be 81 for an authorization or authorization reversal.
◦ Incorrect Mastercard POS entry mode. The Mastercard POS entry mode should be 01 for a tokenized request.
• U: Expired token.
• W: Primary account number (PAN) listed in electronic warning bulletin. This field is returned only for Visa Platform Connect
• Data Length: 1
Mapping Information
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 133-134
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 2
This value identifies the transaction on a host system. It contains the following information:
• Batch number.
You must store this value. If you give the customer a receipt, display this value on the receipt.
• Terminal ID = 66012345
Specifications
• Data Length: 18
Mapping Information
Possible values:
Specifications
• Type: Integer
• Length: 1
Mapping Information
Set the value for this field to 34, which indicates suspected fraud.
This field is ignored for processors that do not support this value.
Specifications
• Data Length: 3
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
• Type: String
• Length: 255
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Credit Mutuel-CIC
This value might also include a text message from Credit Mutuel-CIC.
Specifications
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
Atos:
• Data Length: 6
Mapping Information
Transaction identifier (TID) that is used to identify and track a transaction throughout its life cycle.
This field is returned only for American Express Direct.
American Express generates this value. To comply with the CAPN requirements, this value must be included in all subsequent follow-on requests, such as captures and follow-on
credits.
When you perform authorizations, captures, and credits through Cybersource, Cybersource passes this value from the authorization service to the subsequent services for you.
However, when you perform authorizations through Cybersource and perform subsequent services through other financial institutions, you must ensure that requests for captures
and credits include this value.
Specifications
• Data Length: 15
Mapping Information
This value indicates Mastercard’s evaluation of the transaction’s safety and security.
• U0: Unclassified.
• U0: Unclassified.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 136-137
Specifications
• Data Length: 2
Mapping Information
Type of authentication for which the transaction qualifies as determined by the Mastercard authentication service, which confirms the identity of the cardholder.
Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 132
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
Authorization type.
Possible values:
To request an automatic capture if your account is not configured for automatic captures, set this field to AUTOCAPTURE and include it in a bundled authorization and capture request.
To override an automatic capture and request a standard capture if your account is configured for automatic captures, set this field to STANDARDCAPTURE and include it in a standard
authorization or bundled authorization and capture request.
Forced Capture
A forced capture occurs when you process an authorization outside the Cybersourcesystem but then capture the order through Cybersource. To indicate that you are performing a
forced capture, set this field to verbal and include it in a bundled authorization and capture request along with other fields required for a forced capture.
Verbal Authorization
When you request an authorization through Cybersource, the issuing bank might ask you to call the payment processor to answer questions about the transaction. When this
happens, the processor gives you a verbal authorization code for the transaction. To indicate that you are capturing a verbal authorization, set this field to verbal and include it in a
capture request along with other fields required for a verbal authorization.
• Data Length: 15
• Data Length: 11
Mapping Information
◦ ccAuthService_authType
◦ ccCaptureService_authType
This field is supported only for Mastercard installment payments in Poland on Visa Platform Connect.
After receiving the authorization request, the issuer sends you the type of data you requested by means of a communication method or network that does not include Visa
Platform Connect. Use the data to verify the customer's identity.
Possible values:
Specifications
• Data Length: 2
Mapping Information
This flag specifies whether the transaction is exempt from strong customer authentication (SCA) requirements in Europe because payer authentication is not available.
Possible values:
For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 145-146
Specifications
• Data Length: 1
The name of the individual or the company contacted for company authorized purchases.
Specifications
• Data Length: 36
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Possible values:
Specifications
• Data Length: 1
Mapping Information
First line of the billing street address as it appears in the payment card issuer records.
Atos
The value for this field must not include colons (:) or non-ASCII characters.
FDMS Nashville
When the street name is numeric, it must be sent in numeric format. For example, if the address is One First Street, it must be sent as 1 1st Street.
Important:
When you populate billing street address 1 and billing street address 2, Visa Platform Connect concatenates the two values. If the concatenated value exceeds 40 characters,
Visa Platform Connect truncates the value at 40 characters before sending it to Visa and the issuing bank. Truncating this value affects AVS results and therefore might also
affect risk decisions and charge backs.
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitation of the payment card networks prevents Visa Platform Connect from transmitting non-ASCII characters to the payment card networks.
Therefore, Visa Platform Connect replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card networks.
Specifications
• Atos:
◦ Data Length: 29
◦ Data Length: 20
• Moneris:
◦ Data Length: 50
◦ Data Length: 40
• Worldpay VAP:
◦ Data Length: 35
Atos
The value for this field must not include colons (:) or non-ASCII characters.
FDMS Nashville
The billing address 1 and billing address 2 fields together cannot exceed 20 characters.
Important:
When you populate billing street address 1 and billing street address 2, Visa Platform Connect concatenates the two values. If the concatenated value exceeds 40 characters,
Visa Platform Connect truncates the value at 40 characters before sending it to Visa and the issuing bank. Truncating this value affects AVS results and therefore might also
affect risk decisions and charge backs.
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitation of the payment card networks prevents Visa Platform Connect from transmitting non-ASCII characters to the payment card networks.
Therefore, Visa Platform Connect replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card networks.
• Atos:
◦ Data Length: 29
◦ Data Length: 20
• Moneris
◦ Data Length: 50
◦ Data Length: 40
• Worldpay VAP
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 20
Mapping Information
• Transactions on Cielo.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Specifications
Atos
The value for this field must not include colons (:) or non-ASCII characters.
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
Specifications
Atos
• Data Length: 32
Other Processors
Mapping Information
This field is supported only for these kinds of payments on Visa Platform Connect:
• BNDES transactions
Set the value for this field to the Cadastro Nacional da Pessoa Jurídica (CNPJ). The request must include this field or personal_id. When a request includes both fields, the value for
the personal_id field is sent to the processor and the bill_company_tax_id field is ignored.
For BNDES transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26-39
• Field: Buyer ID
For installment payments with Mastercard in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26-39
• Field: Buyer ID
Specifications
• Data Length: 9
Mapping Information
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
Specifications
• Data Length: 2
Mapping Information
Customer’s neighborhood, community, or region (a barrio in Brazil) within the city or municipality.
This field is supported only on Cielo.
Specifications
• Data Length: 50
Mapping Information
Cielo
Getnet
This field is supported for aggregator authorizations. All characters must be numbers.
Rede
Software Express
• Authorizations with Mastercard in Argentina, Chile, and Paraguay. The value for this field corresponds to the following data in the TC 33 capture file:
◦ Position: 110-124
◦ Position: 40-59
• Installment payments with Mastercard in Croatia. The value for this field corresponds to the following data in the TC 33 capture file:
◦ Position: 79-98
Specifications
• Data Length: 15
Mapping Information
• Authorization service: Flag that specifies whether this payment is for a bill or for an existing contractual loan. This value is case sensitive. Possible values:
• Capture service: Flag that specifies whether this is a credit for a bill that the customer paid with a Visa card. Possible values:
Specifications
• Data Length: 1
Mapping Information
Possible values:
This field is supported only for bill payments in Brazil with Mastercard on Visa Platform Connect.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 48-50
Specifications
• Data Length: 3
Point-of-sale data.
This field is supported only for the American Express card type on American Express Direct and FDMS South.
This field enables you to comply with American Express CAPN requirements.
Forced Capture
Obtain the value for this field from the authorization response.
Verbal Authorization
You cannot obtain a value for this field so Cybersource uses the default value. The default value is generated based on various factors of the transaction such as:
Specifications
• Data Length: 12
This value identifies the transaction on a host system. It contains the following information:
• Batch number.
You must store this value. If you give the customer a receipt, display this value on the receipt.
• Terminal ID = 66012345
Specifications
• Data Length: 18
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
You can use this value to identify transactions in the Ingenico ePayments Collections Report, which provides settlement information. Contact customer support for information
about the report.
Specifications
• Data Length: 20
Mapping Information
This value creates a follow-on credit by linking the credit to the capture. When you include this field, you do not need to include several other credit request fields.
Specifications
• Length: 26
Mapping Information
This value is an encoded string that contains no confidential information, such as an account number or card verification number.
Specifications
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
• Type: String
• Length: 255
Mapping Information
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
Specifications
• Data Length: 2
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Atos:
◦ Data Length: 6
◦ Length: 8
◦ Data Length: 60
Transaction ID (TID).
This field is supported only for the American Express card type on American Express Direct and FDMS South.
This field enables you to comply with American Express CAPN requirements.
Forced Capture
Obtain the value for this field from the authorization response.
Verbal Authorization
You cannot obtain a value for this field so Cybersource uses the default value of 000000000000000 (15 zeros).
Specifications
• Data Length: 15
Mapping Information
When the billing country is the U.S., the 9-digit postal code must follow this format: [5 digits][dash][4 digits].
Example: 12345-6789
When the billing country is Canada, the 6-digit postal code must follow this format: [alpha][numeric][alpha][space][numeric][alpha][numeric]
Before the postal code is sent to the processor, all non-alphanumeric characters are removed, and if the remaining value is longer than nine characters, the value is truncated
starting from the right side.
Atos
The value for this field must not include colons (:) or non-ASCII characters.
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
• Comercio Latino
◦ Data Length: 9
◦ Data Length: 9
Mapping Information
Type of transaction.
This field is a pass-through, which means that the value is not verified or modified in any way before it is sent to the processor.
You can provide a business application ID in this field or in your account. When a request includes this field, the value in the field overrides the information in your account. Call
customer support to update your account information.
◦ Commission payments
◦ Insurance payments
◦ Lottery payouts
◦ Shared economy
Possible values:
◦ Commission payments
◦ Insurance payments
◦ Loan disbursements
◦ Lottery payouts
◦ Shared economy
Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 108-109
Specifications
• Data Length: 2
Mapping Information
Capture number when requesting multiple partial captures for one authorization.
This value is used along with capture_total_count to track which capture is being processed.
Example: These are the values for the second of five captures:
capture_sequence=2
capture_total_count=5
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 158-159
Specifications
• Data Length: 2
Total number of captures when requesting multiple partial captures for one authorization.
This value is used along with capture_sequence to track which capture is being processed.
Example: These are the values for the second of five captures:
capture_sequence=2
capture_total_count=5
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 160-161
Specifications
• Data Length: 2
Reference number that facilitates card acceptor/corporation communication and record keeping.
Specifications
• Data Length: 25
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The encrypted data can be track data or keyed data and is in tag-length-value (TLV) format. A data set consists of encrypted data and the encryption attributes that are associated
with the encrypted data. This field can contain multiple data sets.
This field contains the PIN data, which is optional because some networks no longer require the PIN. Your agreement with the debit networks determines whether the customer
must provide a PIN.
Specifications
Mapping Information
Card password.
The card password consists of 2 digits and is considered Personally Identifiable Information (PII).
Specifications
• Data Length: 2
Mapping Information
The data used will be either 6 digits representing the cardholder's date of birth or a 10-digit business number. This data is considered Personally Identifiable Information (PII).
Specifications
• Data Length: Up to 10
Mapping Information
Possible values:
Specifications
• Data Length: 7
Mapping Information
Example GIFT
Example PAYROLL
Example GENERAL_PREPAID
Specifications
• Data Length: 50
Mapping Information
Possible values:
• Y: Card is present
Specifications
• Data Length: 1
Mapping Information
This field is supported only for BNDES transactions on Visa Platform Connect.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 115-120
Specifications
• Data Length: 15
Mapping Information
You can use this value on the receipt that you give to the customer.
Card-Present Transactions
This field is returned in the response message when the client software that is installed on the POS terminal uses the Token Management Service (TMS) to retrieve tokenized
payment details.
You must contact customer support to have your account enabled to receive these fields in the credit response message.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 85
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
• Data Length: 4
Mapping Information
All cards from the issuers below are supported along with Visa and Mastercard.
• BC
• Hana
• Hyundai
• KB Kookmin
• Lotte
• NH Nonghyup
• Samsung
• Shinhan
Possible Values
Each processor and acquirer supports some of the following card types. No processor or acquirer supports all card types.
001: Visa
For all processors except Ingenico ePayments and SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type
value 001 for Visa Electron.
002: Mastercard and Eurocard
For Eurocard, which is the European regional brand of Mastercard, you must include the card type field in a request for an authorization or stand-alone credit.
003: American Express
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
007: JCB
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
014: EnRoute
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
021: JAL
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
024: Maestro (UK Domestic)
031: Delta
Delta. Use this value only for Ingenico ePayments. For other processors, use 001 for all Visa card types. For this card type, you must include the card type field in a
request for an authorization or stand-alone credit.
033: Visa Electron
Use this value only for Ingenico ePayments and SIX. For other processors, use 001 for all Visa card types. For this card type, you must include the card type field in a
request for an authorization or stand-alone credit.
034: Dankort
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
036: Cartes Bancaires
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
037: Carta Si
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
039: Encoded account number
This value is supported only on Chase Paymentech Solutions. For this value, you must include the card type field in a request for an authorization or stand-alone
credit.
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
042: Maestro (International)
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
050: Hipercard
For this card type on 3.0, , or , you must include the card type field in a request for an authorization or stand-alone credit. This card type is not supported on 1.5.
051: Aura
054: Elo
For this card type on or , you must include the card type field in a request for an authorization or stand-alone credit.
058: Carnet
061: RuPay
Cybersource Integrations
This field is included in the response message when the client software that is installed on the POS terminal uses the Token Management Service (TMS) to retrieve tokenized
payment details. You must contact customer support to have your account enabled to receive these fields in the credit response message.
Specifications
• Data Length: 3
Important: Provide the card type even when it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the
wrong card type.
The value for this field corresponds to the following data in the TC 33 capture file:
• Record: CP01-TCR1
• Position: 70-71
• Field: Card ID
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
All cards from the issuers below are supported along with Visa and Mastercard. Always use code 065 for all card types.
• BC
• Hana
• Hyundai
• KB Kookmin
• Lotte
• Samsung
• Shinhan
Possible Values
Each payment method, processor, and acquirer support different card types. See the table of supported processors and card types for the payment method you are implementing.
001: Visa
For all processors except Ingenico ePayments and SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type
value 001 for Visa Electron.
002: Mastercard and Eurocard
For Eurocard, which is the European regional brand of Mastercard, you must include the card type field in a request for an authorization or stand-alone credit.
003: American Express
004: Discover
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
007: JCB
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
014: EnRoute
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
021: JAL
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
024: Maestro (UK Domestic)
031: Delta
Use this value only for Ingenico ePayments and SIX. For other processors, use 001 for all Visa card types. For this card type, you must include the card type field in a
request for an authorization or stand-alone credit.
034: Dankort
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
036: Cartes Bancaires
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
037: Carta Si
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
039: Encoded account number
This value is supported only on Chase Paymentech Solutions. For this value, you must include the card type field in a request for an authorization or stand-alone
credit.
040: UATP
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
042: Maestro (International)
For this card type, you must include the card type field in a request for an authorization or stand-alone credit.
050: Hipercard
For this card type on Cielo 3.0, Getnet, or , you must include the card type field in a request for an authorization or stand-alone credit. This card type is not supported
on 1.5.
051: Aura
054: Elo
For this card type on Getnet or Rede, you must include the card type field in a request for an authorization or stand-alone credit.
058: Carnet
061: RuPay
For this card type on Getnet or Rede, you must include the card type field in a request for an authorization or stand-alone credit.
Specifications
• Data Length: 3
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
Flag that specifies how to use the card for the requested transaction.
This field is supported only for Mastercard transactions in Brazil on Visa Platform Connect.
Possible values:
• C: Credit transaction.
• D: Debit transaction.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 51
Specifications
• Data Length: 1
Mapping Information
Possible values:
• 0: No verification
• 1: Signature
• 2: PIN
Specifications
• Data Length: 1
Mapping Information
Flag that indicates whether the card number corresponds to a virtual card number.
Possible values:
Specifications
• Type: String
• Length: 5
Mapping Information
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 15-23
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
This field is supported only on FDC Nashville Global and Visa Platform Connect.
When a cashback amount is included in a request, the cashback amount must be included in the value for the grand_total_amount field.
Specifications
• Data Length:
◦ Authorization: 9
◦ Authorization Reversal: 9
Mapping Information
Possible values:
• 2: Self-service terminal
• 9: Terminal or cash register that uses a dialup connection to connect to the transaction processing network
Specifications
• Data Length: 1
Mapping Information
Affiliate organization.
You can use this information for selective analytics and reporting.
Contact your processor to have your account enabled for this feature.
Specifications
• Data Length: 25
Mapping Information
Marketing campaign.
You can use this information for selective analytics and reporting.
Contact your processor to have your account enabled for this feature.
Specifications
• Data Length: 25
Mapping Information
You can use this information for selective analytics and reporting.
Contact your processor to have your account enabled for this feature.
Specifications
• Data Length: 25
Mapping Information
Algorithm for generating a cardholder authentication verification value (CAVV) or universal cardholder authentication field (UCAF) data.
• Atos
• Credit Mutuel-CIC
When you request the payer authentication and authorization services separately, get the value for this field from the pa_validate_cavv_algorithm response field.
Possible values:
Specifications
• Data Length: 1
This value is a transaction identifier generated by the issuing bank during Visa Secure, JCB J/Secure, or ProtectBuy payer authentication.
For Visa Secure on FDC Nashville Global, this field is set to the value for the transaction identifier (XID) when the XID is present in the authorization request and the CAVV is not
present.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_validate_cavv response field.
• American Express: for a 20-byte cryptogram, set this field to the cryptogram for authorizations with payment network tokens. For a 40-byte cryptogram, set this field to
block A of the cryptogram for authorizations with payment network tokens.
• Discover: the value for this field can be a 20 or 40-character hex binary. All cryptograms use of these formats.
• Visa: the value for this field must be 28-character base 64 or 40-character hex binary. All cryptograms use one of these formats.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 77-78
Specifications
• Data Length: 40
Mapping Information
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
The transaction was not cancelled. It was sent to the payment card company and the issuer who can reject it with a soft decline by requesting additional cardholder authentication.
Possible values:
• 04: Transaction timed out at the access control server (ACS), which is a server on the issuer side of the 3D Secure protocol. This value includes all ACS timeouts not covered
by the value 05.
• 05: Transaction timed out at the ACS because the first challenge request was not received by the ACS.
• 07: Unknown.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_enroll_challenge_cancel_code or
pa_validate_challenge_cancel_code response field.
Specifications
• Data Length: 2
Mapping Information
Authorization code.
Specifications
• Data Length: 6
Mapping Information
Authorization status.
Possible values:
Specifications
• Data Length: 20
Mapping Information
Possible values:
Specifications
• Type: Integer
• Length: 1
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
• Type: String
• Length: 255
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
This value is not sent to the processor. Instead, the value is forwarded to the Cybersource reporting software.
Specifications
Mapping Information
Specifications
• Data Length: 12
Elavon Americas
• Data Length: 12
FDC Compass
• Data Length: 12
• Data Length: 12
GPN
OmniPay Direct
• Data Length: 12
• Data Length: 12
• Data Length: 12
Worldpay VAP
• Data Length: 12
Mapping Information
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
First line in the street address of the company purchasing the product.
Specifications
• Data Length: 40
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 40
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 30
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Two-digit ISO standard code for the country in the address of the company purchasing the product.
For more information on ISO standard country codes, see ISO Standard Country Codes.
Specifications
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
Specifications
• Data Length: 40
Moneris processor:
• Data Length: 50
• Data Length: 60
Mapping Information
For US and Canadian transactions, use the standard two digit state / province codes.
For more information, see State, Province, and Territory Codes for the United States and Canada.
Specifications
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
For U.S. transactions, the postal code must consist of the 5 digit or 9 digit format:
For Canadian transactions, the postal code must use the 6-digit potal code format:
Specifications
• Data Length: 10
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This field is returned only when the issuer returns this value and the credit is authorized.
Specifications
• Data Length: 6
Mapping Information
This field is returned only for Visa Platform Connect and only when the credit is authorized.
You can use this value to identify a specific transaction when you are discussing the transaction with your acquirer.
Specifications
• Type: String
• Length: 15
Mapping Information
This field is returned only when the credit is authorized and the processor sends this value.
Important: Do not use this field to evaluate the result of the request.
Specifications
• Data Length: 10
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Specifications
• Data Length: 32
Mapping Information
Merchant ID that was used to create the subscription or token for which the service was requested.
Specifications
• Data Length: 30
Mapping Information
This value identifies the transaction on a host system. It contains the following information:
• Batch number.
You must store this value. If you give the customer a receipt, display this value on the receipt.
• Terminal ID = 66012345
Specifications
• Data Length: 18
Mapping Information
Possible values:
Specifications
• Type: Integer
• Length: 1
Mapping Information
You can use this value to identify transactions in the Ingenico ePayments Collections Report, which provides settlement information. Contact customer support for information
about the report.
Specifications
• Data Length: 20
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
• Type: String
• Length: 255
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
Atos:
• Data Length: 6
◦ Data Length: 8
◦ Data Length: 60
Flag that specifies whether the payment is for the purchase of cryptocurrency.
This field is supported only for Visa transactions on Visa Platform Connect.
Possible values:
The value for this field does not map to the TC 33 capture file.
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
Mapping Information
For an authorization reversal or capture, you must use the same currency that was used for the authorization.
Specifications
• Data Length: 5
Mapping Information
◦ orderInformation.amountDetails.currency
◦ creditAmountDetails.currency
◦ refundAmountDetails.currency
◦ reversalAmountDetails.currency
For authorization reversal or capture services, you must use the same currency that was used for the authorization.
For the PIN debit reversal service, you must use the same currency that was used for the PIN debit purchase or PIN debit credit that you are reversing.
Specifications
• Data Length: 5
Mapping Information
◦ orderInformation.amountDetails.currency
◦ reversalInformation.amountDetails.currency
This value is forwarded to your processor, which then forwards the value to your acquirer during settlement.
When you provide this field in separate authorization and capture requests for the same order, the value from the capture request is forwarded to your processor.
Specifications
• Data Length: 32
Mapping Information
This includes changes to the billing or shipping address, new payment accounts or new users added. This field can contain one of these values:
Specifications
• Data Length: 8
Mapping Information
Specifications
• Data Length: 8
Mapping Information
Credit Mutuel-CIC
For recurring payments in Mexico, the value for this field is the customer’s contract number.
Before you request the authorization, you must inform the issuer about the customer contract numbers that will be used for recurring transactions.
Ingenico ePayments
Prosa
For recurring payments in Mexico, the value for this field is the customer’s contract number.
Worldpay VAP
For a follow-on credit, Cybersource checks the following locations, in the order given, for a customer account ID value and uses the first value it finds:
2. customer_account_id value that was used for the capture that is being credited.
If a customer account ID value cannot be found in any of these locations, then no value is used.
• Credit Mutuel-CIC:
◦ Data Length: 20
• Ingenico ePayments:
◦ Data Length: 15
• Prosa:
◦ Data Length: 20
When a subscription or customer profile is being created, the maximum length for this field for most processors is 30. Otherwise, the maximum length is 100.
Specifications
• Data Length: 8
Mapping Information
Possible values:
• 0 (default): CVN service not requested. This default value is used when you do not include the customer_cc_cv_number field in the request.
• 1 (default): CVN service requested and supported. This default value is used when you include the customer_cc_cv_number field in the request.
Specifications
• Data Length: 1
Mapping Information
Refer to the CVN information in Credit Card Services Using the SCMP API.
Specifications
• Data Length: 4
Mapping Information
◦ paymentInformation.card.securityCode
◦ paymentInformation.tokenizedCard.securityCode
Format: MM
For Maestro (UK Domestic and International) cards, this value must be valid (01 through 12) but is not required to be a valid expiration date. In other words, an expiration date
that is in the past does not cause Cybersource to reject a request. However, an invalid expiration date might cause the issuer to reject a request.
For encoded account numbers (card_type=039), set the value for this field to 12 if the card does not provide an expiration date.
Specifications
• Data Length: 2
Mapping Information
◦ paymentInformation.card.expirationMonth
Format: YYYY
Barclays
For Maestro (UK Domestic and International) cards on Barclays and Streamline, this value must be valid (1900 through 3000) but is not required to be a valid expiration date. In
other words, an expiration date that is in the past does not cause Cybersource to reject a request. However, an invalid expiration date might cause the issuer to reject a request.
Streamline
For Maestro (UK Domestic and International) cards on Barclays and Streamline, this value must be valid (1900 through 3000) but is not required to be a valid expiration date. In
other words, an expiration date that is in the past does not cause Cybersource to reject a request. However, an invalid expiration date might cause the issuer to reject a request.
For encoded account numbers (card_type=039), set the value for this field to 2021 if the card does not provide an expiration date.
You can provide two digits or four digits. When you provide two digits, they must be the last two digits of the year.
FDMS South
You can provide two digits or four digits. When you provide two digits, they must be the last two digits of the year.
• FDC Nashville Global: You can provide two digits or four digits. When you provide two digits, they must be the last two digits of the year.
• FDMS South: You can provide two digits or four digits. When you provide two digits, they must be the last two digits of the year.
Mapping Information
◦ paymentInformation.card.expirationYear
◦ paymentInformation.tokenizedCard.expirationYear
Number of times a Maestro (UK Domestic) card has been issued to the account holder.
The card might or might not have an issue number. The number can consist of one or two digits, and the first digit might be a zero. When you include this value in a request,
include exactly what is printed on the card. A value of 2 is different than a value of 02.
Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.
The issue number is not required for Maestro (UK Domestic) transactions.
Specifications
• Type: String
• Length: 5
Mapping Information
When processing encoded account numbers, use this field for the encoded account number.
Specifications
◦ Data Length: 19
Mapping Information
Month of the start of the Maestro (UK Domestic) card validity period.
Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.
The start date is not required for Maestro (UK Domestic) transactions.
Specifications
• Data Length: 2
• Data Format: MM
Mapping Information
Year of the start of the Maestro (UK Domestic) card validity period.
Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.
The start date is not required for Maestro (UK Domestic) transactions.
Specifications
• Data Length: 4
Mapping Information
Format: name@host.domain
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
Specifications
Mapping Information
Important:
For an authorization request, Cybersource Latin American Processing concatenates customer_firstname and customer_lastname . If the concatenated value exceeds 30
characters, Cybersource Latin American Processing declines the authorization request.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
Specifications
• Worldpay VAP
◦ Data Length: 25
Mapping Information
Specifications
• Data Length: 60
Mapping Information
Customer’s IP address.
Specifications
• Data Length: 45
Mapping Information
Important:
For an authorization request, Cybersource Latin American Processing concatenates customer_firstname and customer_lastname . If the concatenated value exceeds 30
characters, Cybersource Latin American Processing declines the authorization request.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Specifications
• Worldpay VAP:
◦ Data Length: 25
Mapping Information
Specifications
• Data Length: 3
Mapping Information
Specifications
• Data Type:String
• Data Length: 40
Mapping Information
Include the country code when the order is from outside the U.S.
Credit card networks cannot process transactions that contain non-ASCII characters. Visa Platform Connect accepts and stores non-ASCII characters correctly and displays them
correctly in reports. However, the limitations of the payment card networks prevent Cybersource Latin American Processing from transmitting non-ASCII characters to the
payment card networks. Therefore, Cybersource Latin American Processing replaces non-ASCII characters with meaningless ASCII characters for transmission to the payment card
networks.
For installment payments with Mastercard in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 40-50
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
◦ Type: String
• Other Processors:
◦ Type: String
◦ Length: 15
Mapping Information
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 60
Mapping Information
Flag that specifies whether this is a payment towards an existing contractual loan.
Possible values:
• Y: Loan payment.
Specifications
• Data Length: 5
Mapping Information
Flag for a mass transit transaction that indicates whether the purpose of the authorization is to recover debt.
Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 150-151
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
Possible values:
• REVIEW: The order was flagged for review. This value is returned only when you use Token Management Service.
Specifications
• Data Length: 6
Mapping Information
List of AVS codes that cause the request to be declined for AVS reasons.
Important: To receive declines for the AVS code N, include the value N in the list.
Specifications
Mapping Information
This flag specifies whether the transaction is exempt from strong customer authentication (SCA) requirements in Europe because the authentication was delegated to a different
provider, such as an acquirer or payment technology provider (PTP).
Possible values:
• 1: Exempt from SCA requirements because the authentication was delegated to a different provider
For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 145-146
Specifications
• Data Length: 1
When you request the payer authentication and authorization services separately, get the value for this field from the pa_enroll_directory_server_transaction_id or
pa_validate_directory_server_transaction_id response field.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 114-149
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 36
Mapping Information
This field may be required for all Level III processing, depending on your merchant category code. Check with your processor.
Specifications
• Data Length: 13
GPN
• Data Length: 12
OmniPay Direct
• Data Length: 12
• Data Length: 8
• Length: 13
• Data Length: 12
Worldpay VAP
• Data Length: 8
Mapping Information
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
• Elavon Americas:
• FDC Compass:
• OmniPay Direct:
Possible values:
• Y: Discount applied
• N: No Discount applied
Specifications
• Type: String
• Length: 1
Elavon Americas
• Type: String
• Length: 1
FDC Compass
• Type: String
• Length: 1
OmniPay Direct
• Type: String
• Length: 1
• Type: String
• Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Flag to indicate how you handle discount at the line item level.
Possible values:
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Additional details for all processors and all txns (Level II/III and non-Level II/III).
OmniPay Direct
Specifications
GPN
• Data Length: 5
OmniPay Direct
• Data Length: 5
• Data Length: 5
• Data Length: 6
• Data Length: 5
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Dynamic payment descriptor extension (DPDE) that specifies the month for which you are billing the customer.
This field is supported only on JCN Gateway and is not supported for all Japanese acquirers.
Depending on your business model, you might bill for a service that has already been provided, such as a telephone service, or you might bill for a service that is going to be
provided, such as a subscription to investment information. This value lets the customer know which month the payment is for.
Specifications
• Data Length: 4
Mapping Information
◦ ccCaptureService_dpdeBillingMonth
◦ ccCreditService_dpdeBillingMonth
For a lodging deposit, the value for this field specifies the number of days covered by the advance payment.
Specifications
• Data Length: 2
Mapping Information
Total charges for any import or export duties included in the order.
FDMS South
GPN
Specifications
Elavon Americas
• Data Length: 12
FDC Compass
• Data Length: 11
FDMS South
• Data Length: 15
GPN
• Data Length: 12
• Data Length: 12
• Data Length: 8
• Data Length: 13
• Data Length: 12
Worldpay VAP
• Data Length: 8
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Flag that indicates whether the duty amount should be interpreted as negative or positive.
Possible values:
• negative: duty amount is considered negative and represents a refund on the invoice
• positive: duty amount is considered positive and represents a cost on the invoice
Specifications
• Data Length: 8
Mapping Information
The following list provides the Level III processor field name for each processor that supports Level III data:
Type of transaction.
Some payment card companies use this information when determining discount rates.
• For secure transactions for Credit Mutuel-CIC: Authentication was successful for a co-badged Mastercard and Cartes
Bancaires card.
spa_failure Authentication for a co-badged Mastercard and Cartes Bancaires card was attempted but did not succeed.
• For secure transactions for Credit Mutuel-CIC: Authentication failed for a co-badged Mastercard and Cartes Bancaires card.
vbv For Visa Secure: Authentication was successful. For secure transactions for Credit Mutuel-CIC: Authentication was successful for
a co-badged Visa and Cartes Bancaires card.
vbv_attempted For Visa Secure: Authentication was attempted but did not succeed. For secure transactions for Credit Mutuel-CIC:
Authentication for a co-badged Visa and Cartes Bancaires card was attempted but did not succeed.
vbv_failure For Visa Secure: Authentication failed. For secure transactions for Credit Mutuel-CIC: Authentication failed for a co-badged Visa
and Cartes Bancaires card.
• internet: E-commerce order placed through a website. On Ingenico ePayments, this value is supported only for Cartes Bancaires.
• moto: Mail order or telephone order. Not supported on Cielo or UATP. On Ingenico ePayments, this value is supported only for Cartes Bancaires.
• recurring: Recurring payment that is a U.S. transaction or non-U.S. mail order / telephone order (MOTO) transaction.
For the merchant decryption method, one of the following values is required: aesk, dipb, internet, spa, vbv.
Ingenico ePayments
When you omit this field on Ingenico ePayments, the processor uses the default transaction type that they have on file for you.
Card-Present Transactions
Payer Authentication
When you request the payer authentication and authorization services separately, get the value for this field from the pa_validate_e_commerce_indicator response field.
Payouts
For Chase Paymentech Solutions, the value for an account funding transaction (AFT) and original credit transaction (OCT) is internet.
Payouts
For FDC Compass and Visa Platform Connect, the value for an original credit transaction (OCT) is internet.
For a PIN debit transaction, you must set this field to retail.
Samsung Pay
For the merchant decryption method, one of the following values is required: aesk, internet, spa.
• Data Length:
◦ Card-not-present transaction: 20
◦ Card-present transaction: 20
Mapping Information
◦ ccAuthService_commerceIndicator
◦ ccCreditService_commerceIndicator
◦ octService_commerceIndicator
◦ pinDebitCreditService_commerceIndicator
◦ pinDebitPurchaseService_commerceIndicator
When you request the payer authentication and authorization services separately, get the value for this field from the pa_validate_eci_raw response field.
Specifications
• Data Length: 2
Mapping Information
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_enroll_effective_authentication_type or
pa_validate_effective_authentication_type response field.
Possible values:
• CH: Challenge. Strong customer authentication is required. The cardholder must prove that they are present and enter the payment details by providing two of the following
elements:
◦ Something the cardholder has. Examples: plastic card, mobile device, token generator.
• FD: Frictionless with delegation. The issuer does not require cardholder authentication, but the payment card company might require it.
Specifications
• Data Length: 2
Flag that specifies whether the authorization request is a Crediario eligibility inquiry.
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Specifications
• Type: String
• Length: 9
Mapping Information
Cryptogram validation results returned by the entity or service specified in emv_reply_chip_ validation_type.
Possible values:
• A: Application cryptogram is valid, but the application transaction counter (ATC) is outside the allowed range. (A large increase in ATC values can indicate data copying or
other fraud.)
• E: Application cryptogram is valid, but the ATC indicates possible replay fraud.
• G: Application cryptogram is valid but is not a valid authorization request cryptogram (ARQC).
• T: Application cryptogram is valid, but terminal verification results (TVR) or card verification results (CVR) are invalid.
This field is returned only for Mastercard near-field communication (NFC) authorizations that use payment network tokens on Visa Platform Connect.
Specifications
• Data Length: 1
Entity or service that provided the validation results returned in the emv_reply_chip_ validation_results field.
Possible values:
• 02: Mastercard pre-validation service. The Mastercard authorization platform validated the cryptogram before the issuer received the authorization request.
• 03: Mastercard stand-in service. The Mastercard authorization platform validated the cryptogram because the issuer was not available.
• 50: Issuer.
• 90: Chip fall-back transaction downgrade process. The chip could not be read.
This field is returned only for Mastercard near-field communication (NFC) authorizations that use payment network tokens on Visa Platform Connect.
Specifications
• Data Length: 2
Mapping Information
EMV data that is transmitted from the chip card to the issuer and from the issuer to the chip card.
The EMV data is in the tag-length-value format and includes chip card tags, terminal tags, and transaction detail tags.
For more information about the individual tags, see the Application Specification section in the EMV specifications.
Information about EMV in this topic applies to payment card processing and PIN debit processing. All other information applies only to payment card processing. PIN debit
processing is available with the FDC Nashville Global and Visa Platform Connect processors.
Specifications
Mapping Information
Number assigned to a specific card when two or more cards are associated with the same primary account number.
This value enables issuers to distinguish among multiple cards that are linked to the same account. This value can also act as a tracking tool when the issuer reissues cards. When
this value is available, it is provided by the chip reader. When the chip reader does not provide this value, do not include this field in your request.
Information about EMV in this topic applies to payment card processing and PIN debit processing. All other information in this topic applies only to payment card processing. PIN
debit processing is available only on Visa Platform Connect and FDC Nashville Global.
Specifications
• Data Length: 2
Mapping Information
EMV data that is transmitted from the chip card to the issuer and from the issuer to the chip card.
The EMV data is in the tag-length-value format and includes chip card tags, terminal tags, and transaction detail tags.
Important:
The following tags contain sensitive information and must not be included in this field:
For information about the individual tags, see the “Application Specification” section in the EMV Specifications.
For captures, this field is required for contact EMV transactions. Otherwise, it is optional.
Important:
For contact EMV captures, contact EMV stand-alone credits, and contactless EMV stand-alone credits, you must include the following tags in this field. For all other types of
EMV transactions, the following tags are optional:
Information in this topic about EMV applies to payment card processing and PIN debit processing. All other information in this topic applies only to payment card processing.
PIN debit processing is available on Visa Platform Connect and FDC Nashville Global.
The value for Tag 84 corresponds to the following data in the TC 33 capture file:
• Position: 118-149
Specifications
JCN Gateway
Mapping Information
An EMV fallback transaction occurs when an EMV transaction fails for one of these reasons:
• Technical failure: the EMV terminal or EMV card cannot read and process chip data.
• Empty candidate list failure: the EMV terminal does not have any applications in common with the EMV card. EMV terminals are coded to determine whether the terminal
and EMV card have any applications in common. EMV terminals provide this information to you.
Possible values:
• 1: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the EMV terminal either used information from a successful chip read
or it was not a chip transaction.
• 2: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the EMV terminal was an EMV fallback transaction because the
attempted chip read was unsuccessful.
Specifications
• Data Length: 1
Indicates that a fallback method was used to enter payment card information into the POS terminal.
When a technical problem prevents a successful exchange of information between a chip card and a chip-capable terminal:
1. Swipe the card or key the payment card information into the POS terminal.
2. Use the pos_entry_mode field to indicate whether the information was swiped or keyed.
Possible values:
This field is supported on American Express Direct, Chase Paymentech Solutions, FDC Nashville Global, GPN, JCN Gateway, OmniPay Direct, and SIX.
Specifications
• Data Length: 5
Mapping Information
When you receive the issuer_pin_request field in an authorization response message, you must respond with the customer's PIN in a duplicate authorization request.
Possible value:
This field is supported only for Mastercard transactions on Visa Platform Connect.
Specifications
• Data Length: 1
Mapping Information
Digital payment transactions: encrypted payment data value. If you are using the Cybersource decryption option, populate this field with the encrypted payment data value
returned by the Full Wallet request.
Specifications
Mapping Information
Values:
Specifications
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Specifications
• Data Length: 4
Mapping Information
Specifications
• Data Length: 25
Mapping Information
The value for this field includes a decimal point and a maximum of four decimal places.
Specifications
• Data Length: 16
Mapping Information
This value is returned by the DCC provider. This value must be in GMT.
Specifications
• Data Length: 14
Mapping Information
Number of months over which the cardholder can pay for the purchase.
You can use this field when offering extended credit to a cardholder at a retail location. The cardholder provides this value. The issuer pays you for the purchase in one payment,
and then the cardholder pays the issuer in the number of monthly payments specified by this value.
This field is supported only for acquirers in South Africa using Visa Platform Connect.
Specifications
• Data Length: 2
Mapping Information
Interchange reimbursement fee program indicator (FPI), which is used when assessing the fee applied to a cross-border or domestic Asia Pacific financial transaction.
Acquirers and issues retain and return the FPI value in chargeback and representments.
Specifications
• Data Length: 3
Mapping Information
Specifications
• Length: 15
Mapping Information
Specifications
• Data Length: 5
Mapping Information
The total freight or shipping and handling charges for the order.
For Level III transacations with Visa, the field value is set to 0 when this field is not included in the request.
Specifications
Elavon Americas
• Data Length: 12
FDC Compass
• Data Length: 13
GPN
• Data Length: 12
OmniPay Direct
• Data Length: 12
• Data Length: 8
• Data Length: 13
• Data Length: 12
Worldpay VAP
• Data Length: 8
Mapping Information
Flag that indicates if the freight (shipping) amount should be interpreted as negative or positive.
Possible values:
• negative: freight amount is considered negative and represents a refund on the invoice
• positive: freight amount is considered positive and represents a cost on the invoice
Specifications
• Data Length: 8
Mapping Information
The following list provides the Level III processor field name for each processor that supports Level III data:
This value cannot be negative. You can include a decimal point (.), but you cannot include any other special characters. The amount is truncated to the correct number of decimal
places.
Important: Some processors have specific requirements and limitations, such as maximum amounts and maximum field lengths.
Set this field to the converted amount that was returned by the DCC provider. You must include either this field or offer0 and the offer-level field amount in a request.
Amount must be less than or equal to 50,000 USD. Amount limits differ depending on limitations imposed by your acquirer in addition to local laws and regulations. Contact your
acquirer for more information.
If the transaction includes a cash-back amount, that amount must be included in this total amount. If the transaction includes a surcharge amount, that amount must be included in
this total amount.
If your processor supports zero amount authorizations, you can set this field to 0 for the authorization to verify whether the card is lost or stolen.
Comercio Latino
• Data Length: 19
Mapping Information
◦ orderInformation.amountDetails.totalAmount
◦ reversalInformation.amountDetails.totalAmount
When your customer uses a debit card or prepaid card, and you receive a partial authorization, the payment networks recommend that you do not submit a capture amount that is
higher than the authorized amount. When the capture amount exceeds the partial amount that was approved, the issuer has chargeback rights for the excess amount.
Specifications
• Data Length: 12
Mapping Information
Flag that indicates whether the tax amount is included in the Line Item Total.
Possible values:
Specifications
• Data Length: 1
Elavon Americas
• Data Length: 1
FDC Compass
• Data Length: 1
• Data Length: 1
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Replace the # character with a sequential number from 0 to 4. Send this field with a corresponding health_care_#_amount_type field.
Example:
health_care_0_amount_type=vision
health_care_0_amount=60.00
Specifications
• Data Length: 13
Mapping Information
• prescription
• clinic
• dental
• healthcare-transit
• prescription
• vision
Replace the # character with a sequential number from 0 to 4. Send this field with a corresponding health_care_#_amount field.
Example:
health_care_0_amount_type=vision
health_care_0_amount=60.00
• Data Length: 35
Mapping Information
Indicates the bit depth of the color palette for displaying images, in bits per pixel.
Example 24
Specifications
Mapping Information
The value is returned from the navigator.javaEnabled property. This field can contain one of these values:
• true
• false
Specifications
Mapping Information
This value is available from the fingerprint details of the cardholder's browser. This field can contain one of these values:
• true
• false
Specifications
Mapping Information
Example en-US
Specifications
• Data Length: 8
Mapping Information
Example 864
Specifications
• Data Length: 6
Mapping Information
Example 1536
Specifications
• Data Length: 6
Mapping Information
Time difference between UTC time and the cardholder browser local time, in minutes.
Example 300
Specifications
• Data Length: 5
Mapping Information
Example:
Specifications
• Data Length: 40
Mapping Information
Specifications
Mapping Information
Possible values:
For details about these values, see the information about handling replies in the getting started guide.
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Important: Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Flag for a sale request that specifies whether to allow the capture service to run even when the authorization receives an AVS decline.
Possible values:
• yes: Ignore the results of AVS checking and run the capture service.
• no (default): If the authorization receives an AVS decline, do not run the capture service.
When the value of this field is yes, the list in the decline_avs_flags field is ignored.
Specifications
• Data Length: 3
Mapping Information
Flag for a sale request that specifies whether to allow the capture service to run even when the authorization receives a CVN decline.
Possible values:
• yes: Ignore the results of CVN checking and run the capture service.
• no (default): If the authorization receives a CVN decline, do not run the capture service.
Specifications
• Data Length: 3
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 3
Mapping Information
Authorization code.
This field is returned only when the processor returns this value.
Specifications
• Data Length: 7
Mapping Information
You can use this value to identify a specific transaction when you are discussing the transaction with your processor.
Specifications
• Data Length: 15
Mapping Information
Possible values:
Specifications
• Type: Integer
• Length: 1
Mapping Information
This field is returned only when the processor sends this value.
Important: Do not use this field to evaluate the result of the request.
Specifications
• Data Length: 10
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
• Type: String
• Length: 255
Mapping Information
Specifications
• Data Length: 20
Mapping Information
You can use this value to reconcile Cybersource reports with processor reports.
Specifications
• Data Length: 60
Mapping Information
For certain industries, you must set this field to an industry data value to be sent to the processor. When this field is not set to an industry value or is not included in the request,
industry data does not go to the processor.
Specifications
• Data Length: 10
◦ ccAuthService_industryDatatype
◦ ccCaptureService_industryDatatype
◦ ccCreditService_industryDatatype
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 140-143
Specifications
• Data Length: 4
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 128-139
Specifications
• Data Length: 12
Mapping Information
Amount funded.
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
Specifications
• Data Length: 12
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 60-63
Specifications
• Data Length: 4
Mapping Information
Argentina
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26-37
Brazil
When you do not include this field in a request for a Crediario installment payment, a value of 0 is sent to the processor.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26-37
Chile
• Position: 24-35
Georgia (Sakartvelo)
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 63-74
Specifications
• Length:12
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 158-164
Specifications
• Data Length: 7
Mapping Information
In Brazil, obtain the value for this field from the authorization response for a Crediario eligibility request.
For Crediario installment payments in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 151-157
In Chile, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 36-39
Specifications
• Data Length: 7
Mapping Information
Down payment.
Specifications
• Data Length:12
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 76-79
Specifications
• Data Length: 4
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 64-75
Specifications
• Data Length: 12
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 92-95
Specifications
• Data Length: 4
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 80-91
Specifications
• Data Length: 12
Mapping Information
This field is supported only for Mastercard installment payments in Georgia (Sakartvelo) on Visa Platform Connect.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 23-34
Specifications
• Data Length: 12
Mapping Information
When you do not include this field, a string of six zeros (000000) is sent to the processor.
In Argentina, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 38-43
For Crediario installment payments in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 42-47
Specifications
• Data Length: 6
Mapping Information
When you do not include this field in a request for a Credario installment payment, a space character is sent to the processor.
Possible values:
• B: Biweekly.
• M: Monthly.
• W: Weekly.
For Credario installment payments, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 41
Specifications
• Data Length: 1
Grace period requested by the customer before the first installment payment is due.
Prosa
When the value for the installment plan type field is 07, the installment grace period duration must be greater than 00.
This field is supported only for Mastercard installment payments in Brazil and Greece.
When you include this field in a request, you must also include the grace period duration type field.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 100-101
• Data Length: 2
Mapping Information
This field is supported only for Mastercard installment payments in Brazil and Greece on Visa Platform Connect.
Possible values:
• D: Days.
• W: Weeks.
• M: Months.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 99
Specifications
• Data Length: 1
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain the value for this field from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 124-127
Specifications
• Data Length: 4
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
Obtain this value from the authorization response for a Crediario eligibility request.
The value for this field corresponds to the following data in the TC 33 capture file.
• Position: 112-123
Specifications
• Data Length: 12
Mapping Information
This field is supported only for installment payments with Mastercard on Visa Platform Connect in Brazil.
This value is similar to a tracking number and is the same for all installment payments for one purchase.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 51-70
Specifications
• Data Length: 20
Mapping Information
This field is supported only for installment payments on Visa Platform Connect.
Brazil
This field is included in the authorization response for a Crediario eligibility request when the issuer approves the customer's request for Crediario installment payments in Brazil.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 144-150
Georgia (Sakartvelo)
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 41-45
• Data Length: 7
Mapping Information
This field is supported only for installment payments on Visa Platform Connect.
Possible values:
• 0 (default): Regular installment. This value is not allowed for airline transactions.
• 2: Installment payment without down payment. This value is supported only for airline transactions.
• 3: Installment payment; down payment and boarding fee will follow. This value is supported only for airline transactions.
• 5: Boarding fee only. This value is supported only for airline transactions.
Brazil
In Brazil, this field is supported only for installment payments with Visa.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 9
Rest of World
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 35-37
Specifications
• Data Length: 1
Mapping Information
Possible values:
• 0: No deferred period.
• 1: Deferred period 1.
• 2: Deferred period 2.
• 3: Deferred period 3.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 40
Specifications
• Data Length: 50
This field is supported only on American Express Direct, Cielo, Cybersource Latin American Processing, Prosa, and Visa Platform Connect.
Possible values:
When you do not include this field in the request, the value in your account is used. To change the value in your account, contact customer service.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Prosa
Possible values:
• 07: Skip payment: buy now and pay the full amount later in one payment.
American Express-defined code that specifies the type of installment plan. Contact American Express for:
• Information about the kinds of installment plans that American Express provides.
For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 5-6
Possible values:
For installment payments in Argentina, the value for this field corresponds to the following data in the TC 33 capture file:
For installment payments in Chile, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 23
For installment payments with Visa in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 5-6
For all other kinds of installment payments, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 39-40
Specifications
• Data Length: 1
Mapping Information
This field is used along with installment_total_count to track which payment is being processed.
Example: These are the values for the second of five payments:
installment_sequence=2
installment_total_count=5
When you do not include this field in a request for a Crediario installment payment, a value of 0 is sent to the processor.
For Crediario installment payments, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 38-40
Specifications
Mapping Information
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
This field is included in the authorization response for a Crediario eligibility request when the issuer approves the customer's request for Crediario installment payments in Brazil.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 108-111
Specifications
• Data Length: 4
Mapping Information
This field is included in the authorization response for a Crediario eligibility request when the issuer approves the customer's request for Crediario installment payments in Brazil.
This field is supported only for Crediario installment payments in Brazil on Visa Platform Connect.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 96-107
Specifications
• Type: Decimal
• Length: 12
Mapping Information
Specifications
• Data Length: 12
Mapping Information
This field is used along with installment_sequence to track which payment is being processed.
Example: These are the values for the second of five payments:
installment_sequence=2
installment_total_count=5
This value is the total number of installments that you approved. The default is 1.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
Prosa
When the value for the installment plan type field is 07, the installment total count is set to 00.
• Position: 24-25
For Mastercard installments and for Crediario installment payments with Visa, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 23-25
• Position: 20-22
Visa Platform Connect in All Countries Except Argentina, Brazil, and Chile
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 20-22
For installment payments with American Express or with Visa, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 7-8
Specifications
• Data Length: 2
Mapping Information
You must specify the number of offer lines that will include an invoice number. By default, the first offer line includes an invoice number field. By default, the first offer line
includes an invoice number field. The invoice number field can be included for up to 10 offer lines.
Specifications
• Data Length: 23
• Data Length: 23
FDC Compass
• Data Length: 23
• Data Length: 23
FDMS South
• Data Length: 23
GPN
• Data Length: 23
• Data Length: 23
• Data Length: 15
GPN
• Data Length: 23
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data.
• GPN: Amount
This field is supported only for Visa and Mastercard on Visa Platform Connect.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 9-168
Specifications
Important: For an authorization, the maximum length for this value is 255 characters. In the capture file, the value is truncated at 161 characters.
Mapping Information
If you give the customer a receipt, display this value on the receipt.
Specifications
Mapping Information
When you request an authorization for a card-present transaction but do not include a PIN in the request, the issuer can require the PIN. To complete the authorization:
2. Send a duplicate authorization request that includes the PIN and the emv_request_repeat field.
This field is supported only for Mastercard transactions on Visa Platform Connect.
Specifications
• Data Length: 1
Mapping Information
Additional authorization code that must be printed on the receipt when returned by the processor.
This value is generated by the processor and is returned only for a successful transaction.
• SIX
• HSBC
Specifications
• Data Length: 6
Mapping Information
Reason that the issuer declined your request for a strong customer authentication exemption.
This value is a series of a maximum of 20 four-digit codes and no delimiters. Possible codes:
• 8401: You are not participating in the Visa Trusted Listing program.
• 8403: Your business is not included on the cardholder's list of trusted merchants.
• 8473: Your business is not included on the cardholder's list of trusted merchants.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 61-140
• Data Length: 80
Mapping Information
This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on Visa Platform Connect.
Specifications
• Data Length: 25
Mapping Information
This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on Visa Platform Connect.
Specifications
• Data Length: 25
Mapping Information
This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on Visa Platform Connect.
Specifications
• Data Length: 25
Mapping Information
This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on Visa Platform Connect.
When you do not include this field in a request that uses installment payments for one of the Japanese payment options, the first billing month is set to the calendar month that
follows the transaction date.
Specifications
• Data Length: 2
Mapping Information
This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on Visa Platform Connect.
Specifications
• Data Length: 2
Mapping Information
Unique Japan Credit Card Association (JCCA) terminal identifier that is provided by Cybersource.
The difference between this field and the terminal_id field is that you can define the terminal_id field, but the jpo_jcca_terminal_id field is defined by the JCCA and is used only
in Japan.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 130-142
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 13
Japanese Industrial Standard Type 2 (JIS2) track data from the front of the card.
This field is supported only on JCN Gateway and Visa Platform Connect.
Specifications
• Data Length: 69
Mapping Information
This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on Visa Platform Connect.
Possible values:
• 2: Bonus payment.
• 4: Installment payment.
• 5: Revolving payment.
Specifications
• Data Length: 1
Mapping Information
Value that links the current authorization request to the original authorization request.
This value is used for partial authorizations and split shipments. Set this value to the request ID that was returned in the response message from the original authorization request.
Specifications
• Data Length: 26
Mapping Information
Flag that specifies whether a loan is for a recoverable item or a non-recoverable item.
This field is supported only for BNDES transactions on Visa Platform Connect.
Possible values:
• N: Non-recoverable item.
• R: Recoverable item.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26
Specifications
• Data Length: 1
Mapping Information
Type of loan or installment payment plan based on an agreement between you and the issuer.
This field is supported only for these kinds of payments on Visa Platform Connect:
• BINDES transactions
Example: AGRO-CUSTEIO
Example: AGRO-INVEST
Example: BNDES-Type1
Example: CBN
Example: FINAME
For BNDES transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 27-46
For installment payments with Mastercard in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
Specifications
• Data Length: 20
Mapping Information
Flag that indicates whether local sales tax is included in the order total.
Possible values:
Specifications
Elavon Americas
• Data Length: 1
OmniPay Direct
• Data Length: 1
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 13
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
Elavon Americas
• Data Length: 10
• Data Length: 13
• Data Length: 13
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This flag specifies whether the transaction is exempt from strong customer authentication (SCA) requirements in Europe because the payment amount is low.
Possible values:
For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 145-146
For transactions with other card types, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 126
• Data Length: 1
Mapping Information
This field is supported for American Express Direct, JCN Gateway, and Visa Platform Connect.
JCN Gateway
This value must be right justified. In Japan, this value is called a goods code.
This value must be right justified. In Japan, this value is called a goods code.
Specifications
• Data Length: 7
Mapping Information
This field is supported only on Visa Platform Connect and OmniPay Direct.
The value for this field is a four-digit number that the payment card industry uses to classify merchants into market segments. A payment card company assigned one or more of
these values to your business when you started accepting the payment card company’s cards. Including this field in a request for a domestic transaction might reduce interchange
fees.
This field is supported only for domestic transactions with Visa or Mastercard in Spain. Domestic means that you and the customer are in the same country.
When you include this field in a Visa request, you must also include the merchant_category_code field.
When you include this field in a Mastercard request, including the merchant_category_code field is optional.
OmniPay Direct
• The value for this field overrides the value in your account.
• Domestic transactions with Mastercard in Spain. Domestic means that you and the customer are in the same country.
Specifications
• Length: 4
Mapping Information
Four-digit number that the payment card industry uses to classify merchants into market segments.
A payment card company assigned one or more of these values to your business when you started accepting the payment card company’s cards.
When you do not include this field in a request, the value in your account is used.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 150-153
Specifications
• Data Length: 4
Mapping Information
This topic describes the sequence of fields from merchant_defined_data1 through merchant_defined_data100.
Warning: Merchant-defined data fields are not intended to and must not be used to capture personally identifying information. Accordingly, merchants are prohibited from
capturing, obtaining, and/or transmitting any personally identifying information in or via the merchant-defined data fields. Personally identifying information includes, but
is not limited to, address, payment card number, social security number, driver's license number, state-issued identification number, passport number, and card verification
numbers (CVV, CVC2, CVV2, CID, CVN). In the event Cybersource discovers that a merchant is capturing and/or transmitting personally identifying information via the
merchant-defined data fields, whether or not intentionally, Cybersource will immediately suspend the merchant's account, which will result in a rejection of any and all
transaction requests submitted by the merchant after the point of suspension.
Payer Authentication
Only fields 1 through 5 are supported in Payer Authentication. The value appears in the Case Management Details window in the Business Center. The first four fields are the same
fields that are used by the Secure Data services.
For installment payments with Mastercard in Brazil, use merchant_defined_data1 and merchantDefinedData_mddField_2merchant_defined_data2 for data that you want to
provide to the issuer to identify the transaction.
• The value for merchant_defined_data1 corresponds to the following data in the TC 33 capture file:
◦ Position: 25-44
• The value for merchant_defined_data2 corresponds to the following data in the TC 33 capture file:
◦ Position: 45-64
Specifications
◦ Data Length: 20
Mapping Information
When you do not include this value in your PIN debit request, Cybersource uses the merchant city from your account.
Payouts
Specifications
• Data Length: 13
Mapping Information
This value must be the city in which your store or outlet is located.
When you include more than one consecutive space, extra spaces are removed.
Payouts
For Chase Paymentech Solutions, you must use one of the following formats:
• PCCCCCCCCCCCC
• NNN-NNN-NNNN
• NNN-NNN-NAAA
• NNN-NNN-AAAA
• NNN-AAAAAAA
where:
• N: Numeric
• P: Alpha
• Data Length: 13
Mapping Information
When you do not include this value in your request, Cybersource uses the merchant country from your account.
If your business is located in the U.S. or Canada and you include this field in a request, you must also include merchant_ descriptor_state.
Specifications
• Data Length: 2
Mapping Information
Important: Mastercard requires a postal code for any country that uses postal codes. You can provide the postal code in your Cybersource account or you can include this
field in your request.
If your business is domiciled in the U.S., you can use a 5-digit or 9-digit postal code. A 9-digit postal code must follow this format: [5 digits][dash][4 digits] Example: 12345-6789
If your business is domiciled in Canada, you can use a 6-digit or 9-digit postal code. A 6-digit postal code must follow this format: [alpha][numeric][alpha][space] [numeric][alpha]
[numeric] Example: A1B 2C3
When you do not include this value in your PIN debit request, Cybersource uses the merchant postal code from your account.
Specifications
• Data Length: 14
This name is displayed on the cardholder’s statement. When you include more than one consecutive space, extra spaces are removed.
For a credit card bill payment, set the value for this field to the name of the originator providing the credit card bill payment service.
For a funds disbursement, set the value for this field to the name of the originator sending the funds disbursement.
For a prepaid load, set the value for this field to the name of the partner providing the reload service.
PIN Debits
When you do not include this value in a PIN debit request, Cybersource uses the merchant name in your account.
• Data Length: 23
Mapping Information
Use the standard state, province, and territory codes for the United States and Canada.
This field is supported only for businesses located in the U.S. or Canada.
When you do not include this value in your PIN debit request, Cybersource uses the merchant state from your account.
Specifications
• Data Length: 2
Mapping Information
When you include this value in your request, Cybersource recommends you also include the merchant descriptor country, merchant descriptor state, and merchant descriptor
postal code in your request.
Specifications
• Data Length:
Mapping Information
This field is supported only for Mastercard digital secure remote payment (DSRP) transactions on FDC Compass and Visa Platform Connect.
Specifications
◦ Colon(:)
◦ Period (.)
Mapping Information
Your merchant ID. Use the same merchant ID for evaluation, testing, and production.
Specifications
• Data Length: 30
Mapping Information
◦ For payment processing: The merchant ID value is passed in the HTTP header v-c-merchant-id.
Specifications
Mapping Information
You should provide a unique value for each transaction so that you can perform meaningful searches for the transaction. Refer to the Getting Started with Cybersource Advanced
guide.
Card-Not-Present Transactions
FDC Nashville Global: Certain circumstances can cause the processor to truncate this value to 15 or 17 characters for Level II and Level III processing, which can cause a
discrepancy between the value you submit and the value included in some processor reports.
Card-Present Transactions
FDC Nashville Global: The value for this field must be numeric and must be fewer than 9 digits. When you do not send a valid value, Cybersource creates one for you. However, the
value is not returned to you, so you cannot use the merchant reference number to track the order.
Requests for PIN debit reversals need to use the same merchant reference number that was used in the transaction that is being reversed.
Specifications
◦ Data Length: 40
◦ Data Length: 32
• Elavon Americas:
◦ Data Length: 39
◦ Data Length: 24
◦ Data Length: 50
Mapping Information
If you included multi-byte characters in this field in the request, the returned value might include corrupted characters.
When a card-present request does not include a merchant reference number, this value is provided by the client software that is installed on the POS terminal.
Sometimes the processor truncates this value to 15 or 17 characters for Level II and Level III processing. This can cause a discrepancy between the value you submit and the value
included in some processor reports.
SIX
When a card-present request does not include a merchant reference number, this value is provided by the client software that is installed on the POS terminal.
Specifications
• Data Length: 50
Mapping Information
For a PIN debit reversal, your request must include a request ID or a merchant transaction identifier. The suggested format for this value is:
• Positions 14-15: Two random characters. One way to generate two random characters is to use a counter from 01-99.
Specifications
• Data Length:
Specifications
Elavon Americas
• Data Length: 20
GPN
• Data Length: 20
OmniPay Direct
• Data Length: 21
• Data Length: 20
• Data Length: 20
• Data Length: 20
Worldpay VAP
• Data Length: 20
• Data Length: 13
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
• OmniPay Direct: Merchant VAT Registration / Single Business Reference Number / Merchant Tax ID / Corporation VAT Number
This field is supported only for Mastercard transactions on Visa Platform Connect.
Possible values:
• 5: Customer-initiated top up
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 94
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
Mapping Information
Possible values:
• 0: Dongle
• 1: Phone or tablet
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 141
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
Specifications
Important: For an authorization, the maximum length for this value is 255 characters. In the capture file, the value is truncated at 161 characters.
Mapping Information
Amount of national tax or value added tax for countries in which more than one tax is applied.
Provide this value if national_tax differs from tax_amount. If you do not provide this value, Cybersource assumes that national_tax is equal to tax_amount.
Specifications
• Data Length: 11
FDMS South
• Data Length: 15
• Data Length: 12
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Amount of national tax or value added tax for countries in which more than one tax is applied to an order.
Provide this value if national_tax differs from tax_amount. If you do not provide this value, Cybersource assumes that national_tax is equal to tax_amount.
Specifications
Elavon Americas
• Data Length: 12
GPN
• Data Length: 12
OmniPay Direct
• Data Length: 12
• Data Length: 13
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Flag that indicates whether a national tax is included in the order total.
Possible values:
If you do not include any national_tax values in your request, Cybersource does not include national_tax_indicator in the data it sends to the processor.
Specifications
Elavon Americas
• Data Length: 1
OmniPay Direct
• Data Length: 1
• Data Length: 1
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Priority order of the networks through which the transaction will be routed.
Important: This field is supported only for businesses located in the U.S.
Set this value to a series of one-character network codes in your preferred order:
Network Code
Accel E
AFFN U
Alaska Option 3
CU24 C
Interlink G
Maestro 8
NETS P
NYCE F
Pulse H
Shazam 7
Star M
Visa V
For example, if the Star network is your first preference and Pulse is your second preference, set this field to a value of MH.
Specifications
• Data Length: 30
Mapping Information
◦ pinDebitCreditService_networkOrder
◦ pinDebitPurchaseService_networkOrder
For token-based transactions with 3D Secure, you must submit both types of cryptograms: network token and 3D Secure.
The value for this field must be 28-character Base64 or 40-character hex binary. All cryptograms use one of these formats.
Specifications
• Data Length: 40
Mapping Information
Transaction amount.
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Network transaction identifier (TID). This value can be used to identify a specific transaction when you are discussing the transaction with your processor.
Specifications
• Data Length: 15
Mapping Information
Possible values:
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Possible values:
• 13: Amount exceeded the maximum limit allowed for this type of OCT.
• 61: Issuer declined the transaction because exceeds the cumulative total amount limit.
• 62: Restricted card. OCT cannot be sent to an embargoed country (Cuba, Iran, North Korea, Syria, or Sudan).
• 64: Transaction does not fulfill anti-money laundering requirements because the required sender and recipient information was not sent.
• 65: Issuer declined the transaction because it exceeds the cumulative total count limit.
Specifications
• Data Length: 10
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Message that explains the response flag (oct_rflag). Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Reference number that you use to reconcile your Cybersource reports with your processor reports. See Getting Started with Cybersource Advanced for the SCMP API for
information about transaction tracking and reconciliation.
Specifications
• Data Length: 60
Mapping Information
You must include either offer0 and the offer-level field amount, or the request-level field grand_total_amount in a request.
Specifications
• Data Length: 50
Mapping Information
• REST API Field: No corresponding field. The REST API uses an array of line items.
• Simple Order API Field: No corresponding field. The Simple Order API uses item-level fields.
For RBS WorldPay Atlanta transactions only: The discount amount cannot exceed 999999.99.
Specifications
• Data Length: 13
Elavon Americas
• Data Length: 12
FDC Compass
• Data Length: 13
• Data Length: 11
GPN
• Data Length: 12
OmniPay Direct
• Data Length: 12
• Data Length: 8
• Data Length: 13
• Data Length: 12
Worldpay VAP
• Data Length: 8
Mapping Information
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
Flag that indicates whether the invoice level discount amount should be interpreted as negative or positive.
Possible values:
A positive value for the discount amount is considered to reduce the amount of the invoice.
Specifications
• Data Length: 8
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Possible values:
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This value links the previous request to the current follow-on request.
This value is an encoded string that contains no confidential information, such as an account number or card verification number.
Specifications
Mapping Information
This value cannot be negative. You can include a decimal point (.) in this field to denote the currency exponent, but you cannot include any other special characters. If needed, the
amount is truncated to the correct number of decimal places.
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Tax amount for the tax type identified by in the item_#_otherTax_#_rateitem_#_otheTax_#_typeother_tax#_type field.
For more information on tax fields, see: Example: Three Tax Line Items for One Item
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
A maximum of 2 decimal places is allowed. Valid range is 0.00 to 99.99. The value can also be zero.
For example:
• 60%: offer0:taxRate=60.00
• 25.5%: offer0:taxRate=25.50
• 33.33%: offer0:taxRate=33.33
Specifications
• Data Length: 4
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This field is a pass-though field. This means Cybersource does not verify the value or modify it in any way befoe sending it to the precessor. For possible values, see: Tax Fields
For more information on tax fields, see: Example: Three Tax Line Items for One Item
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This field is a pass-though field. This means Cybersource does not verify the value or modify it in any way befoe sending it to the precessor.
Specifications
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This field is supported only for combo card transactions in Brazil on Visa Platform Connect.
Include this field when the value for the or override_payment_method field is line of credit (LI) or prepaid card (PP).
Line of Credit
Possible values:
Prepaid Card
Possible values:
TC 33 Capture File
• Position: 44-47
Specifications
Mapping Information
◦ ccAuthService_overridePaymentDetails
◦ ccCreditService_overridePaymentDetails
Flag that specifies the type of account associated with the card.
Possible values:
Combo cards in Brazil contain credit and debit functionality in a single card. Visa systems use a credit bank identification number (BIN) for this type of card. Using the BIN to
determine whether a card is debit or credit can cause transactions with these cards to be processed incorrectly. It is strongly recommended that you include this field for combo
card transactions.
On these processors, this field is supported only for authorizations. Possible values:
For combo card transactions with Mastercard in Brazil, the card_usage field is also supported.
The value for this field corresponds to the following data in the TC 33 capture file:
• Positions: 42-43
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 2
Mapping Information
◦ paymentInformation.card.useAs
◦ ccAuthService_overridePaymentMethod
◦ ccCreditService_overridePaymentMethod
◦ pinDebitCreditService_overridePaymentMethod
Number of purchases with this cardholder account during the previous six months.
Specifications
• Data Length: 4
Mapping Information
Issuers should be aware of the acquirer's country code when the acquirer country differs from the merchant country, and the acquirer is in the EEA (European Economic Area).
Specifications
• Data Length: 2
Mapping Information
You can send this override field to set the challenge window size to display to the cardholder. The Access Control Server (ACS) replies with content that is formatted appropriately
for this window size to allow for the best user experience.
The sizes are width x height in pixels of the window displayed in the cardholder browser. Possible values:
• 01: 250x400
• 02: 390x400
• 03: 500x600
• 04: 600x400
Specifications
• Data Length: 2
Mapping Information
Specifications
• Data Length: 3
Mapping Information
Specifications
Mapping Information
Format: YYYYMMDDHHMM
Specifications
• Data Length: 12
Mapping Information
Format: YYYYMMDDHHMM
Specifications
• Data Length: 12
Mapping Information
Possible values:
Specifications
• Data Length: 2
Mapping Information
Date and time that the 3D Secure server authenticated the cardholder.
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
Format: YYYYMMDDHHMMSS
Specifications
• Data Length: 14
Mapping Information
Possible values:
• 06: Cardholder verification as part of EMV token ID&V (identity and verification)
Specifications
• Data Length: 2
Mapping Information
Authentication type or challenge that you presented to the cardholder at checkout after requesting Cartes Bancaires Fast'R through the Cybersource payer authentication services.
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
A challenge means that strong customer authentication is required. The challenge status does the following:
• Informs the issuer about the alternative authentication methods that the cardholder used.
• Enables you to override default values for one transaction at a time and increase the authorization acceptance rate at the risk of accepting a liability shift for the transaction.
Possible values:
• 01: No preference.
• 03: You requested the challenge. You can default to this value for every transaction when you see an increase in fraud rates.
• 04: Challenge mandated. Strong customer authentication is required when one of the following is true:
◦ Transaction amount exceeds 30 EUR and there have been at least five transactions on the payment card during the preceding week.
◦ Cumulative amount for the payment card during the preceding week exceeds 100 EUR.
• 05: No challenge requested because transactional risk analysis has already been performed.
• 06: No challenge requested because the purpose of this transaction is to share data, not to move money.
• 07: No challenge requested because strong consumer authentication has already been performed.
• 08: No challenge requested because the cardholder is on a white list of exempt cardholders.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_enroll_challenge_code response field.
Specifications
• Data Length: 2
Mapping Information
An alias that uniquely identifies the customer's account and credit card on file.
Specifications
Mapping Information
Indicates that the card being used is the one designated as the primary payment card for purchase.
• true
• false
Specifications
Mapping Information
• SDK
• Browser
Important: If you use the SDK integration, this field is dynamically set to SDK. If you use the JavaScript code, this field is dynamically set to Browser. For merchant-initiated
or 3RI transactions, you must set the field to 3RI. If you use this field in addition to JavaScript code, you must set the field to Browser.
Specifications
• Data Length: 10
Mapping Information
Indicates whether the merchant experienced suspicious activity (including previous fraud) on the account.
Specifications
• Data Length: 2
Mapping Information
The purchase amount total for prepaid gift cards in major units.
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 2
Mapping Information
Specifications
• Data Length: 3
Mapping Information
Important: If the customer’s browser provides a value, you must include it in your request.
Specifications
Mapping Information
Specifications
Mapping Information
Important: If the customer’s browser provides a value, you must include it in your request.
Specifications
Mapping Information
An integer value greater than 1 indicating the maximum number of permitted authorizations for installment payments.
Important: This value is required if the merchant and cardholder have agreed to installment payments.
Specifications
• Data Length: 4
Mapping Information
• true
• false
Specifications
Mapping Information
Specifications
• Data Length: 40
Mapping Information
Specifications
• Data Length: 4
Mapping Information
Calculated by merchants according to Payment Service Directive 2 (PSD2) and Regulatory Technical Standards (RTS). European Economic Area (EEA) card fraud divided by all EEA
card volumes.
Possible Values:
Specifications
• Data Length: 2
Mapping Information
Your company’s name as you want it to appear to the customer in the issuing bank’s authentication form.
Specifications
• Data Length: 25
For Paymentech processor using Cybersource Payouts, the maximum data length is 22.
Mapping Information
Indicates whether the consumer is a new or existing customer with the merchant.
• true
• false
Specifications
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Specifications
Mapping Information
Possible values:
• 03-79: Reserved for EMVCo future use (values invalid until defined by EMVCo)
Specifications
• Data Length: 2
Mapping Information
Specifications
Mapping Information
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_network_score response field.
Specifications
• Data Length: 2
Mapping Information
This field overrides other payment types that might be specified in the request. Use one of the following values for this field:
• NA: Not applicable. Do not override other payment types that are specified in the request.
Specifications
• Data Type:String
• Data Length: 10
Mapping Information
Specifications
• Data Length: 8
Mapping Information
Format: YYYYMMDD
Specifications
• Data Length: 8
Mapping Information
Indicates whether cardholder is placing an order with a future availability or release date.
Specifications
• Data Length: 2
Mapping Information
This field contains data that the ACS can use to verify the authentication process.
Specifications
Mapping Information
Possible values:
• 05-79: Reserved for EMVCo future use (values invalid until defined by EMVCo)
Specifications
• Data Length: 2
Mapping Information
This field contains the ACS transaction ID for a prior authenticated transaction.
For example, the first recurring transaction that was authenticated with the cardholder.
Specifications
• Data Length: 36
Mapping Information
Format: YYYYMMDDHHMM
Specifications
• Data Length: 12
Mapping Information
• GAS: Fuel
• RES: Restaurant
• SVC: Services
• TRA: Travel
Specifications
• Request: Required
• Data Length: 3
Mapping Information
Format: YYYYMMDD.
Specifications
• Request: Required
• Data Length: 8
Mapping Information
Integer value indicating the minimum number of days between recurring authorizations.
A frequency of monthly is indicated by the value 28. Multiple of 28 days will be used to indicate months.
• 31
• 031
• 0031
Specifications
• Request: Required
• Data Length: 4
Mapping Information
Specifications
• Data Length: 17
Mapping Information
• 02: Reordered
Specifications
• Data Length: 2
Mapping Information
Possible Values:
• 07: Top-up
EMV 3D Secure version 2.1.0 supports values 01-05. Version 2.2.0 supports values 01- 11.
Specifications
• Data Length: 2
Mapping Information
JSON Web Token (JWT) returned by the 3D Secure provider when the authentication is complete.
Specifications
• Request: Required
Mapping Information
This return URL is added to the step-up JWT and returned in the response of the Payer Authentication enrollment call. Your return URL page serves as a listening URL. Cardinal
sends a POST response to your return URL when the bank session completes that contains the completed bank session’s transaction ID. Your return page should capture the
transaction ID and send it in the Payer Authentication validation call.
Specifications
• Field Type:Request
• Data Type:String
• Data Length:2048
Mapping Information
This field indicates the maximum amount of time for all 3D Secure 2.x messages to be communicated between all components (in minutes).
Possible Values:
• Default is set to 15
Specifications
• Data Length: 2
Mapping Information
Date when the shipping address for this transaction was first used.
Specifications
• Data Length: 8
Mapping Information
If you need to show proof of enrollment checking, you may need to decrypt and parse the string for the information required by the payment card company.
Important: The value is in Base64. You must remove all carriage returns and line feeds before adding the PARes to the request.
Specifications
Mapping Information
Example: 1.0.2
Example: 2.0.0
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 113
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 20
Number of transaction (successful or abandoned) for this cardholder account within the last 24 hours.
Specifications
• Data Length: 3
Mapping Information
Number of transactions (successful and abandoned) for this cardholder account within the last year.
Specifications
• Data Length: 3
Mapping Information
Transaction mode identifier. Identifies the channel from which the transaction originates.
Possible values:
• R: Retail
• S: eCommerce
• P: Mobile Device
• T: Tablet
Specifications
• Data Length: 1
Mapping Information
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
Possible values:
• 02: Unknown device. Example: Device fingerprint not recognised because the device is an old mobile phone.
• 04: Exceeds authentication frequency limit. Strong customer authentication is required every six transactions or when the cumulative amount for the payment card during
the preceding week exceeds 100 EUR.
• 08: No card record. The card was not found in the 3D Secure server database.
• 21: 3D Secure request for information, such as BIN lookup, is not supported.
• 23: Decoupled authentication is required by the ACS but you did not request it.
• 25: There was not enough time for decoupled authentication to authenticate the cardholder.
• 26: Authentication was attempted but the cardholder was not authenticated.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_enroll_pares_status_reason or
pa_validate_pares_status_reason response field.
Specifications
• Data Length: 2
• Asia, Middle East, and Africa Gateway for Mastercard Identity Check and Visa Secure transactions.
• Credit Mutuel-CIC for Cartes Bancaires Fast'R and Mastercard Identity Check transactions.
◦ Mastercard Identity Check transactions when a third-party provider authenticates the transaction.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_validate_pares_status response field.
Possible values:
Specifications
• Data Length: 1
Mapping Information
Partial primary account number (PAN) and International Bank Account Number (IBAN).
This field is returned only for Mastercard transactions on Visa Platform Connect.
The issuer provides the value for this field, which consists of four digits of the PAN and seven digits of the IBAN.
Specifications
• Data Length: 11
Mapping Information
Value that links the previous transaction to the current follow-on request.
This value is assigned by the client software that is installed on the POS terminal, which makes it available to the terminal’s software and to Cybersource. Therefore, you can use
this value to reconcile transactions between Cybersource and the terminal’s software.
This value is not sent to the processor. Instead, the value is forwarded to the Cybersource reporting software.
Specifications
• Data Length: 32
Mapping Information
This value is provided by the client software that is installed on the POS terminal.
This value is not sent to the processor. Instead, the value is forwarded to the Cybersource reporting software.
Specifications
• Data Length: 32
Mapping Information
Visa-generated reference number that identifies a transaction for which you provided one of the following:
This reference number provides a link to the cardholder account and to all transactions for that account.
For transactions with American Express, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 79-107
For Token Management Service transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 79-110
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
• Data Length: 32
Mapping Information
Mastercard-defined code that indicates how the account information was obtained.
Possible values:
• 00 (default): Card
• 01: Removable secure element that is personalized for use with a mobile phone and controlled by the wireless service provider; examples: subscriber identity module (SIM),
universal integrated circuit card (UICC)
• 03: Watch
• 05: Wristband
• 07: Mobile phone with a non-removable, secure element that is controlled by the wireless service provider
• 08: Removable secure element that is personalized for use with a mobile phone and not controlled by the wireless service provider; example: memory card
• 09: Mobile phone with a non-removable, secure element that is not controlled by the wireless service provider
• 10: Removable secure element that is personalized for use with a tablet or e-book and is controlled by the wireless service provider; examples: subscriber identity module
(SIM), universal integrated circuit card (UICC)
• 11: Tablet or e-book with a non-removable, secure element that is controlled by the wireless service provider
• 12: Removable secure element that is personalized for use with a tablet or e-book and is not controlled by the wireless service provider
Specifications
• Data Length: 2
Mapping Information
Possible values:
• N: Nonregulated
• R: Regulated
Specifications
• Data Length: 1
Mapping Information
Apple Pay, Google Pay, and Samsung Pay Transactions: This field is supported only for FDC Compass and Visa Platform Connect.
Specifications
• Data Length: 2
Mapping Information
Apple Pay, Google Pay, and Samsung Pay Transactions: This field is supported only for FDC Compass and Visa Platform Connect.
Specifications
• Data Length: 2
Mapping Information
Possible values:
• 001: Secure Element (SE). Smart card or memory with restricted access and encryption to prevent data tampering. For storing payment credentials, an SE is tested against a
set of requirements defined by the payment networks.
• 002: Host card emulation (HCE). Emulation of a smart card by using software to create a virtual and exact representation of the card. Sensitive data is stored in a database
that is hosted in the cloud. For storing payment credentials, a database must meet very stringent security requirements that exceed PCI DSS.
Specifications
• Data Length: 3
Mapping Information
This field is returned only for Mastercard transactions on Visa Platform Connect.
For the possible values available for this field, refer to Mastercard Product IDs in the credit card services guide (see Related information below).
Specifications
• Data Length: 3
Mapping Information
Value that identifies your business and indicates that the cardholder’s account number is tokenized.
This value is assigned by the token service provider and is unique within the token service provider’s database.
This field is supported only for Chase Paymentech Solutions, FDC Nashville Global, and Visa Platform Connect.
Specifications
• Data Length: 11
Mapping Information
Value that identifies your business and indicates that the cardholder’s account number is tokenized.
This value is assigned by the token service provider and is unique within the token service provider’s database.
This field is returned only for FDC Nashville Global and Visa Platform Connect.
Specifications
• Data Length: 11
Mapping Information
This value does not specify the token service provider; it specifies the entity that provided you with information about the token.
Possible values:
• 1: In-app transactions (for Apple Pay, Google Pay, and Samsung Pay transactions).
• 2: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this
value if the original transaction was a contactless EMV transaction.
For Google Pay transactions, this field is used only for merchant-initiated transactions with Elavon Americas.
Specifications
• Data Length: 1
Mapping Information
This unique ID distinguishes digital payment solution transactions and authorizations with payment network tokens on the Cybersource platform for reporting purposes.
Possible values:
• 014: Mastercard credential-on-file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
• 015: Visa credential-on-file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
Specifications
• Apple Pay, Google Pay, Samsung Pay, Visa payment network tokens, and Mastercard payment network tokens:
◦ Data Length: 3
◦ Data Length: 12
Mapping Information
This field is supported only on Cielo 3.0, Credit Mutuel-CIC, Cybersource Latin American Processing and Visa Platform Connect.
Cielo 3.0
Set this field to the Cadastro Nacional da Pessoa Jurídica (CNPJ) or Cadastro de Pessoas Fisicas (CPF).
Credit Mutuel-CIC
This field is supported only for Redecard in Brazil. Set this field to the Cadastro de Pessoas Fisicas (CPF), which is required for AVS for Redecard in Brazil.
Cybersource Latin American Processing is the name of a specific processing connection. Cybersource Latin American Processing does not refer to the general topic of processing
in Latin America. The information in this field description, or in this section of the field description, is for the specific processing connection called Cybersource Latin American
Processing. It is not for any other Latin American processors.
• BNDES transactions
Set this field to the Cadastro de Pessoas Fisicas (CPF). The request must include this field or bill_company_tax_id.
• Position: 7-21
For installment payments with Mastercard in Brazil, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 26-39
• Field: Buyer ID
Specifications
• Cielo 3.0:
◦ Data Length: 18
• Commerico Latino:
◦ Data Length: 18
◦ Data Length: 26
Mapping Information
Possible values:
Specifications
• Data Length: 7
Mapping Information
Encrypted PIN.
This value is provided by the client software that is installed on the POS terminal.
This field is supported only for Cybersource integrations and only for processors that support chip and online PIN transactions.
Specifications
• Data Length: 16
Mapping Information
Combination of the POS terminal's unique identifier and a transaction counter that is used when decrypting the encrypted PIN.
The entity that injected the PIN encryption keys into the terminal decrypts the encrypted PIN and creates this value.
For all terminals that are using derived unique key per transaction (DUKPT) encryption, this is generated as a single number within the terminal.
This field is supported only for Cybersource integrations and only for processors that support chip and online PIN transactions.
Specifications
• Data Length: 20
Mapping Information
This value is provided by the client software that is installed on the POS terminal.
Possible values:
This field is supported only for Cybersource integrations and only for processors that support chip and online PIN transactions.
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Possible values:
Network Code
Accel E
AFFN U
Alaska Option 3
CU24 C
Interlink G
Maestro 8
NETS P
NYCE F
Pulse H
Shazam 7
Star M
Visa V
Specifications
Mapping Information
Important: Do not use this field to evaluate the results of the transaction request.
Specifications
• Data Length: 2
Mapping Information
Flag that indicates whether the request for the PIN debit credit service was successful.
Possible values:
Refer to the Getting Started with Cybersource Advanced guide (see Related Information below) for information about order tracking and reconciliation.
Specifications
• Data Length: 1
Mapping Information
One-word description of the result of the request for the PIN debit credit service.
Specifications
• Data Length: 50
Mapping Information
Important: Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Format: YYYY-MM-DDThhmmssZ
The T separates the date and the time. The Z indicates UTC.
Specifications
• Data Length: 20
Mapping Information
Refer to the Getting Started with Cybersource Advanced guide for information about order tracking and reconciliation.
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Possible values:
• cash: Cash benefits, which can be used to purchase any item at a participating retailer, as well as to obtain cash-back or make a cash withdrawal from a participating ATM.
• food: Food stamp benefits, which can be used only to purchase food items authorized by the USDA SNAP program.
Specifications
• Data Length: 4
Mapping Information
◦ pinDebitPurchaseService_ebtCategory
◦ pinDebitCreditService_ebtCategory
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 3
Mapping Information
◦ pinDebitCreditService_paymentType
◦ pinDebitPurchaseService_paymentType
Specifications
• Data Length: 5
Mapping Information
Specifications
• Data Length: 12
Mapping Information
Possible values:
• Positive
• Negative
Specifications
• Data Length: 8
Mapping Information
Type of account.
Possible values:
Specifications
• Data Length: 2
Mapping Information
Type of amount.
Possible values:
• 02: Current available balance, which is typically the ledger balance less outstanding authorizations. Some depository institutions also include pending deposits and the credit
or overdraft line associated with the account.
Specifications
• Data Length: 2
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Possible values:
Network Code
Accel E
AFFN U
Alaska Option 3
CU24 C
Interlink G
Maestro 8
NETS P
NYCE F
Pulse H
Shazam 7
Star M
Visa V
Specifications
Mapping Information
Flag that indicates whether the transaction is enabled for partial authorization.
When the request includes this field, this value overrides the information in your account.
Possible values:
Specifications
• Data Length: 5
Mapping Information
Important: Do not use this field to evaluate the results of the transaction request.
Specifications
• Data Length: 2
Mapping Information
Flag that indicates whether the request for the PIN debit credit service was successful.
Possible values:
Refer to the Getting Started guides (see Related Information below) for information about these values.
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Currency for the amount you requested for the PIN debit purchase.
Specifications
• Data Length: 5
Mapping Information
One-word description of the result of the request for the PIN debit purchase service.
Specifications
• Data Length: 50
Mapping Information
Important: Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Format: YYYY-MM-DDThhmmssZ
The T separates the date and the time. The Z indicates UTC.
Specifications
• Data Length: 20
Mapping Information
Refer to the Getting Started guide (see Related Informaiton below) for information about order tracking and reconciliation.
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Request ID of the PIN debit purchase or PIN debit credit that you want to reverse.
Specifications
• Data Length: 26
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Important: Do not use this field to evaluate the results of the transaction request.
Specifications
• Data Length: 2
Mapping Information
Flag that indicates whether the request for the PIN debit reversal service was successful.
Possible values:
Refer to the Getting Started guides (see Related Information below) for information about these values.
Specifications
• Data Length: 1
Mapping Information
One-word description of the result of the request for the PIN debit reversal service.
Specifications
• Data Length: 50
Mapping Information
Important: Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
Mapping Information
Format: YYYY-MM-DDThhmmssZ
The T separates the date and the time. The Z indicates UTC.
Specifications
• Data Length: 20
Mapping Information
Refer to the Getting Started guide (see Related Informaiton below) for information about order tracking and reconciliation.
Specifications
• Data Length: 60
Mapping Information
Specifications
• Data Length: 6
Mapping Information
Value created by the client software that uniquely identifies the POS device.
This value is not sent to the processor. Instead, the value is forwarded to the Cybersource reporting software.
Specifications
• Data Length: 32
Mapping Information
Possible values:
• msd: Read from a contactless interface using magnetic stripe data (MSD).
The contact, contactless, and msd values are supported only for EMV transactions.
Specifications
• Data Length: 11
Operating environment.
This field is supported only on American Express Direct and Visa Platform Connect.
• 2: On merchant premises, unattended, or customer terminal. Examples: oil, kiosks, self-checkout, home computer, mobile telephone, personal digital assistant (PDA).
Customer terminal is supported only for Mastercard transactions on Visa Platform Connect.
• 4: Off merchant premises, unattended, or customer terminal. Examples: vending machines, ,mobile telephone, personal digital assistant. Customer terminal is supported
only for Mastercard transactions on Visa Platform Connect.
• 2: On merchant premises, unattended. Examples: oil, kiosks, self-checkout, mobile telephone, personal digital assistant (PDA).
• 3: Off merchant premises, attended. Examples: portable POS devices at trade shows, at service calls, or in taxis.
• 4: Off merchant premises, unattended. Examples: vending machines, home computer, mobile telephone, PDA.
• S: Electronic delivery of product. Examples: music, software, or eTickets that are downloaded over the Internet.
• T: Physical delivery of product. Examples: music or software that is delivered by mail or by a courier.
• Data Length: 1
Mapping Information
You can extract the service code from the track data and provide it in this API field.
Specifications
• Data Length: 3
Mapping Information
This field is supported only for post-dated transactions with Mastercard in Brazil on Visa Platform Connect.
The guaranteed amount is specified in an agreement between you and the issuer.
A post-dated transaction enables a customer to make a purchase using a debit Mastercard and to have the debit post to the customer's account at a later date.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 5-12
Specifications
• Type: Decimal
• Length: 8
Mapping Information
This field is supported only for post-dated transactions with Mastercard in Brazil on Visa Platform Connect.
The guarantee is specified in an agreement between you and the issuer. The customer tells you whether they would like the transaction to be post-dated. The issuer provides the
guarantee.
A post-dated transaction enables a customer to make a purchase using a debit Mastercard and to have the debit post to the customer's account at a later date.
Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 55
Specifications
• Data Length: 1
This field is supported only for post-dated transactions with Mastercard in Brazil on Visa Platform Connect.
A post-dated transaction enables a customer to make a purchase using a debit Mastercard and to have the debit post to the customer's account at a later date.
Format: YYYYMMDD
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 13-18
Specifications
• Data Length: 8
Mapping Information
Specifications
• Data Length: 3
Mapping Information
Type of product.
This value is used to determine the category that the product is in, such as electronic, physical, service, or shipping.
Possible values:
• default: Default value for the product code. The value default is used when a request message does not include a value for the product code.
• handling_only: Fee that you charge your customer to cover your administrative selling costs.
• shipping_and_handling: Handling portion is the fee that you charge your customer to cover your administrative selling costs. Shipping is the charge for shipping the product
to your customer.
• shipping_only: Charge for transporting tangible personal property from your location to your customer. You must maintain documentation that clearly establishes the
location where the title to the property passed from you to your customer.
• merchant_product_sku
• product_name
• quantity
Specifications
Mapping Information
Name of product.
Specifications
Mapping Information
Customer ID reference number that identifies the customer for a Level II transaction.
Specifications
FDMS South
• Data Length: 17
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Worldpay VAP
Specifications
Elavon Americas
• Data Length: 6
GPN
• Data Length: 6
OmniPay Direct
• Data Length: 6
• Data Length: 6
• Data Length: 6
Worldpay VAP
• Data Length: 10
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
Elavon Americas
• Data Length: 13
• Data Length: 13
FDMS South
• Data Length: 13
GPN
OmniPay Direct
• Data Length: 13
• Data Length: 13
• Data Length: 13
• Data Length: 13
Mapping Information
◦ buyerInformation.vatRegistrationNumber
◦ senderInformation.vatRegistrationNumber
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Flag that indicates the capture or credit request includes Level III data.
Specifications
• Data Length: 1
• Data Length: 1
FDC Compass
• Data Length: 1
• Data Length: 1
GPN
• Data Length: 1
OmniPay Direct
• Data Length: 1
• Data Length: 1
• Data Length: 1
Worldpay VAP
• Data Length: 1
Mapping Information
◦ ccCaptureService_purchasingLevel
◦ ccCreditService_purchasingLevel
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
• GPN: N/A
The default is 1.
Specifications
• Data Length: 10
Mapping Information
Receipt number.
This field is returned only for American Express Direct and Visa Platform Connect.
• American Express Direct: System trace audit number (STAN). This value identifies the transaction and is useful when investigating a chargeback dispute.
• Visa Platform Connect: System trace number that must be printed on the customer’s receipt.
Specifications
• Data Length: 6
Mapping Information
Set the value for this field to the first six digits and last four digits of the recipient’s account number.
This field is a pass-through, which means that the value is not verified or modified in any way before it is sent to the processor. If the field is not required for the transaction, it is
not forwarded to the processor.
Specifications
• Data Length: 10
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Conversion rate between the sender’s currency and recipient’s currency used by the issuer to deposit the funds into the recipient’s account.
Specifications
• Data Length: 8
Mapping Information
Currency used by the issuer to deposit the funds into the recipient’s account. See the ISO Standard Currency Codes reference guide.
Specifications
• Data Length: 3
Mapping Information
Specifications
• Data Length: 25
Mapping Information
Specifications
• Data Length: 2
Mapping Information
Related information
ISO Standard Country Codes
This field is a pass-through, which means that it is verified that the value is eight numeric characters but otherwise the value is not verified or modified in any way before it is sent
to the processor. If the field is not required for the transaction, it is not forwarded to the processor.
Specifications
• Data Length: 8
• Format: YYYYMMDD
Mapping Information
Specifications
• Data Length: 35
Mapping Information
This field is a pass-through, which means that the value is not verified or modified in any way before it is sent to the processor. If the field is not required for the transaction, it is
not forwarded to the processor.
Specifications
• Data Length: 35
Mapping Information
Specifications
• Data Length: 1
Mapping Information
Specifications
• Data Length: 35
Mapping Information
Specifications
• Data Length: 30
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Example: If the postal code is NN5 7SG, the value for this field should be the first part of the postal code: NN5.
This field is a pass-through, which means that the value is not verified or modified in any way before it is sent to the processor. If the field is not required for the transaction, it is
not forwarded to the processor.
Specifications
• Data Length: 10
Mapping Information
Specifications
• Field Type:Request
• Data Length: 2
Mapping Information
Related information
State, Province, and Territory Codes for the United States and Canada
This field is a pass-through, which means that this value is not verified or modified in any way before it is sent to the processor.
Specifications
• Data Length: 3
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Possible values:
This field is a pass-though field. This means Cybersource does not verify the value or modify it in any way before sending it to the precessor.
Specifications
• Data Length: 2
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Reference number. The meaning of this value is defined by the value of the corresponding reference_data_#__code field.
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
This field is a pass-through, which means that this value is not verified or modified in any way before it is sent to the processor.
Specifications
• Data Length: 30
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Value that you create that enables you to identify a group of transactions.
Specifications
• Data Length: 25
Mapping Information
Specifications
• Data Length: 26
Mapping Information
• REST API Field: No corresponding field. The value is returned in the endpoint of the resource that was requested.
This value is an encoded string that contains no confidential information, such as an account number or card verification number.
When you request the authorization and capture services together, the request token is for the capture response only.
Specifications
Mapping Information
Flag that indicates whether a full authorization reversal was successfully submitted.
Possible values:
• N: Authorization reversal was not successfully submitted. You must send a credit request for a refund.
Specifications
• Data Length: 1
Mapping Information
This flag specifies whether the transaction is exempt from strong customer authentication (SCA) requirements in Europe because it is a low-risk transaction.
Low-risk transactions are described by the Payments Service Directive 2/Regulatory Technical Standards (PSD2/RTS) regulations.
Possible values:
For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 145-146
For transactions with other card types, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 127
Specifications
• Data Length: 1
Mapping Information
Possible values:
• NYCE
• PULSE
• STAR
• Visa
• Mastercard
Specifications
• Data Length: 10
Mapping Information
Indicates whether the transaction was routed on a credit network, a debit network, or the STAR signature debit network.
Possible values:
• C: Credit network
Specifications
• Data Length: 1
Mapping Information
Possible values:
Specifications
• Data Length: 1
Mapping Information
This field is supported only for aggregator transactions. Get the value for this field from the payment card company.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 106-116
Specifications
• Data Length: 11
Mapping Information
This field is supported only on JCN Gateway and Visa Platform Connect.
In Argentina, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 8-15
In Japan, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 143-147
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
Mapping Information
Transaction identifier.
The difference between this field and the receipt_number field is that Cybersource generates the receipt number for the field, and you must print the receipt number on the
receipt. However, for the processorInformation.salesSlipNumber field, you can generate the sales slip number, and you can choose to print the sales slip number on the receipt.
This field is supported only on JCN Gateway and Visa Platform Connect.
Specifications
• Data Length: 5
Mapping Information
This flag specifies whether the transaction is exempt from strong customer authentication (SCA) requirements in Europe because the payment is a secure corporate payment.
Indicates that dedicated payment processes and procedures were used.
Possible values:
• 1: Exempt from SCA requirements because the payment is a secure corporate payment.
For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 145-146
For transactions with other card types, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 129
• Dats Length: 1
Mapping Information
◦ ccAuthService_secureCorporatePaymentIndicator
◦ payerAuthEnrollService_secureCorporatePaymentIndicator
The account number of the entity funding the transaction. The value for this field can be a payment card account number or bank account number.
Specifications
• Data Length: 20
Mapping Information
Specifications
• Data Length: 50
Mapping Information
City of sender.
Specifications
• Data Length: 25
Mapping Information
Country of sender.
Specifications
• Data Length: 2
Mapping Information
Related information
ISO Standard Country Codes
Format: YYYMMDD
Specifications
• Data Length: 8
Mapping Information
First name of sender when the sender is an individual. When the sender is a business or government entity, use the sender_name field instead.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 5-39
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 35
Mapping Information
Last name of sender when the sender is an individual. When the sender is a business or government entity, use the sender_name field instead.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 75-109
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 35
Mapping Information
Middle initial of sender when the sender is an individual. When the sender is a business or government entity, use the sender_name field instead.
Format: YYYMMDD
Specifications
• Data Length: 1
Mapping Information
Middle name of sender when the sender is an individual. When the sender is a business or government entity, use the sender_name field instead.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 40-74
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 35
Mapping Information
First name of whole name of the sender. Name of sender when the sender is a business or government entity.
FDC Compass
When the sender is an individual, use the sender_firstname and fields instead.
Funds Disbursement: This value is the first name of the originator sending the funds disbursement.
Specifications
• Data Length: 30
FDC Compass
• Data Length: 24
• Data Length: 30
Mapping Information
Specifications
• Data Length: 20
Mapping Information
Specifications
• Data Length: 10
Mapping Information
Specifications
• Data Length: 19
Mapping Information
Source of funds.
Possible values:
• 05: Debit or deposit account that is not linked to a Visa card. Includes checking accounts, savings accounts, proprietary debit or ATM card accounts, and digital wallet
accounts.
• 06: Credit account that is not linked to a Visa card. Includes credit cards and proprietary lines of credit.
Funds Disbursement: For FDC Compass, the best value for funds disbursement is 04 to identify that the originator used a deposit account to fund the disbursement. For Visa
Platform Connect, the best value for funds disbursement is 05.
Credit Card Bill Payment: This value must be 02, 03, 04, or 05.
Specifications
• Data Length: 2
Mapping Information
State of sender.
Specifications
• Data Length: 2
Mapping Information
Related information
State, Province, and Territory Codes for the United States and Canada
Specifications
• Data Length: 40
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Additional address information for the company that ships the product.
Specifications
• Data Length: 40
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 30
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 40
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 40
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The combined length of this field and the orderInformation.billTo.last.nameship_from_lastnameship_from_lastName field must not exceed 40 characters.
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The combined length of this field and the orderInformation.billTo.first.nameship_from_firstnameship_from_firstName field must not exceed 40 characters.
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Postal code for the address from which the goods are shipped, which is used to establish nexus.
The default is the postal code associated with your account. The postal code must consist of 5 to 9 digits.
U.S.
Example: 12345-6789
Canada
Specifications
• Data Length: 10
Mapping Information
Specifications
• Worldpay VAP:
◦ Data Length: 35
Mapping Information
Specifications
• Worldpay VAP:
◦ Data Length: 35
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 40
Mapping Information
Tax Calculation
Optional field for U.S., Canadian, international tax, and value added taxes.
Specifications
• Data Length: 2
Mapping Information
Specifications
• Data Length: 80
Mapping Information
Possible values:
• 05 : Digital goods
• 07 : Other
Specifications
• Data Length: 2
Mapping Information
Shipping destination.
Specifications
• Data Length: 25
Mapping Information
Specifications
• Data Length: 50
Mapping Information
Specifications
• Worldpay VAP:
◦ Data Length: 25
Mapping Information
Specifications
• Worldpay VAP:
◦ Data Length: 25
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Tax Calculation
Optional field for U.S. and Canadian taxes. Not applicable to international and value added taxes. Billing address objects will be used to determine the cardholder’s location when
shipTo objects are not present.
Specifications
• Data Length: 2
Mapping Information
Canada
Format: [alpha][numeric][alpha][space][numeric][alpha][numeric]
U.S.
Example: 12345-6789
American Express Direct: Before sending the postal code to the processor, all non-alphanumeric characters are removed. If the remaining value is longer than nine characters,
the value is truncated starting from the right side.
Specifications
• Data Length: 10
Possible values:
Specifications
• Data Length: 10
Mapping Information
Flag to indicate whether the tax_amount should be interpreted as a positive or negative value.
Possible values:
• negative
• positive
Specifications
• Data Length: 8
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
When connectivity is unavailable, the client software that is installed on the POS terminal can store a transaction in its memory and send it for authorization when connectivity is
restored.
This value is provided by the client software that is installed on the POS terminal.
This value is not sent to the processor. Instead, the value is forwarded to the Cybersource reporting software.
Possible values:
Specifications
• Data Length: 1
Mapping Information
Sub-merchant’s city.
FDC Compass
Getnet
Allowable characters are letters, numbers, and spaces. Special characters are not allowed.
The value for this field does not map to the TC 33 capture file.
Specifications
• Data Length:
◦ Cielo: 13
◦ FDC Compass: 21
◦ Rede: 13
◦ Software Express: 21
Mapping Information
Sub-merchant’s country.
FDC Compass
The value for this field does not map to the TC 33 capture file.
Specifications
• Data Length: 3
Mapping Information
With American Express, the value of this field corresponds to the following data in the TC 33 capture file:
• Position: 25-64
Specifications
• Data Length:
◦ FDC Compass: 40
FDC Compass
With American Express, the value of this field corresponds to the following data in the TC 33 capture file:
• Position: 65-84
With Mastercard and Visa, the value of this field corresponds to the following data in the TC 33 capture file:
• Position: 117-131
• Field: Sub-Merchant ID
Specifications
◦ Cielo: 15
◦ FDC Compass: 20
◦ Getnet: 15
◦ Rede: 15
◦ Software Express: 20
Mapping Information
This field is supported only for aggregator authorizations on FDC Nashville Global with American Express.
Specifications
• Data Length: 15
Mapping Information
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 109-146
FDC Compass
Specifications
• Data Length:
◦ American Express Direct: Maximum length of the sub-merchant name depends on the length of the aggregator name. The combined length for both values must not
exceed 37 characters.
◦ FDC Compass: American Express: 19. Mastercard: maximum length of the sub-merchant name depends on the length of the aggregator name. The combined length for
both values must not exceed 37 characters.
◦ Visa Platform Connect: With American Express, the maximum length of the sub-merchant name depends on the length of the aggregator name. The combined length
for both values must not exceed 36 characters. Not used with other card types.
Mapping Information
FDC Compass
Getnet
The value for this field does not map to the TC 33 capture file.
Specifications
• Data Length:
◦ Cielo: 9
◦ FDC Compass: 15
◦ Rede: 9
◦ Software Express: 15
Mapping Information
Sub-merchant’s region.
This field is supported only for aggregator authorizations on FDC Nashville Global.
Specifications
• Data Length: 3
Mapping Information
FDC Compass
Getnet
All characters must be uppercase letters. Special characters are not allowed.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 164-166
Specifications
• Data Length:
Mapping Information
FDC Compass
Getnet
Allowable characters are letters, numbers, and spaces. Special characters are not allowed.
The value for this field does not map to the TC 33 capture file.
Specifications
• Data Length:
◦ Cielo: 22
◦ FDC Compass: 38
◦ Rede: 48
◦ Software Express: 38
Mapping Information
FDC Compass
This value must consist of numbers or a combinations of numbers and uppercase letters.
Formats:
• NNN-NNN-NNNN
• NNN-AAAAAAA
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 5-24
Specifications
• Data Length:
◦ Cielo: 13
◦ FDC Compass: 13
◦ Software Express: 20
Mapping Information
When you use Recurring Billing or Token Management Service and you include this value in a request, many of the fields that are normally required for an authorization or credit
become optional.
Payouts
When you include this field in your request, the following fields are optional :
• customer_cc_expmo
• customer_cc_expyr
• customer_cc_number
Specifications
• Data Length: 26
Mapping Information
Indicates whether the customer initiated the transaction and whether the credentials are stored for future authorizations.
Future authorizations that use the stored credentials can be merchant-initiated transactions or credentials-on-file transactions.
Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 136
Specifications
• Data Length: 1
This field is supported only for the following kinds of transactions with Discover:
• Merchant-initiated transactions.
• Recurring payments on FDC Nashville Global that use payment network tokens.
Specifications
• Data Length: 60
Mapping Information
This field is supported only for the five kinds of merchant-initiated transactions in the following list.
Possible values:
• 1: Resubmission.
• 2: Delayed charge.
• 4: No show.
• 5: Incremental authorization.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 160-163
• Data Length: 1
Mapping Information
• Merchant-initiated transactions.
Possible values:
The value for this field does not correspond to any data in the TC 33 capture file.
Specifications
• Data Length: 1
Indicates whether you obtained the payment information from credentials on file (COF) instead of from the customer.
Possible values:
When you use the Token Management Service, this field is set to Y for you.
Specifications
• Type: String
• Length: 1
Mapping Information
Network transaction identifier that was returned for a previous authorization in the series.
This field is supported only for:
• Merchant-initiated transactions.
The value for this field was returned in the auth_payment_network_transaction_id field in the response message for either the original authorization in the series or the
previous authorization in the series.
Specifications
• Data Length: 15
Mapping Information
Elavon Americas
FDMS South
GPN
This field might be required for Level III processing depending on your merchant category code. Check with your processor for more information.
Specifications
Elavon Americas
• Data Length: 4
FDMS South
• Data Length: 4
GPN
• Data Length: 4
OmniPay Direct
• Data Length: 4
• Data Length: 4
• Data Length: 4
• Data Length: 4
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Due to the limited functionality of the supplier_order_reference field, you should use the offer-level product_nameitem-level item_#_productName field instead. Only include
on of these fields in a request. Including both fields may result in an error.
Specifications
• Data Length: 25
OmniPay Direct
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
• OmniPay Direct: Purchase Identifier / Merchant Related Data / Merchant Reference Number
Surcharge amount that you are charging the customer for the transaction.
The surcharge amount is included in the total transaction amount but is passed in a separate field to the issuer and acquirer for tracking. The issuer can provide information about
the surcharge amount to the customer.
If you include a surcharge amount in the request, you must also do the following:
Specifications
• Data Length: 15
Mapping Information
Possible values:
If you include this field in the request, you must also include the surcharge_amount field.
Specifications
• Data Length: 1
Mapping Information
This value cannot be negative. The tax amount and the offer amount must be in the same currency.
offer0=amount:10.00^quantity:1^tax_amount:0.80
offer1=amount:20.00^quantity:1^tax_amount:1.60
2. The total authorized amount is 32.40, not 30.00 with 2.40 of tax included.
Airline Processing
Tax portion of the order amount. This value cannot exceed 99999999999999 (fourteen 9s). Format: English characters only. Optional request field for a line item.
Tax Calculation
Optional field for U.S., Canadian, international tax, and value-added taxes.
When you want to include tax_amount and also request the tax service, see the tax calculation service guide.
• Data Length: 15
Mapping Information
Flag that indicates whether tax is included in the total purchase amount.
Possible values:
• Y: Tax is included
Specifications
OmniPay Direct
• Data Length: 1
Mapping Information
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
Possible values:
• Y: Order is taxable
This field is required for Level II Mastercard and Visa transactions. If tax_amount = 0, set this field to falseN. If tax_amount > 0, set this field to trueY.
If you do not include any tax_amount values in your request, the tax_indicator field value is not included in the request.
Worldpay VAP
Specifications
FDMS Nashville
• Data Length: 1
FDMS South
• Data Length: 1
• Data Length: 1
• Data Length: 1
Worldpay VAP
• Data Length: 1
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Possible values:
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The valid range is between 0.00 (0%) to 99.99 (99.99%). Values with more than 2 digits beyond the decimal point will be truncated.
• 60%: 60.00
• 25.5%: 25.50
• 33.33%: 33.33
For Visa: the valid range is 0.01 (1%) to 0.99 (99%). Only whole percentage values accepted; values with additional decimal places will be truncated.
• 60%: 0.6000
• 25.5%: 0.2550
• 33.33%: 0.3333
• 60%: 0.60
• 25%: 0.25
Elavon Americas
• 60%: 0.6000
• 25.5%: 0.2550
• 33.33%: 0.3333
• 60%: 0.60
• 25%: 0.25
• 33%: 0.33
FDC Compass
• 60%: 0.6000
• 25.5%: 0.2550
• 33.33%: 0.3333
• 60%: 0.60
• 25%: 0.25
The valid range is between 0.00 (0%) to 99.99 (99.99%). Values with more than 2 digits beyond the decimal point will be truncated.
• 60%: 60.00
• 25.5%: 25.50
• 33.33%: 33.33
The valid range is between 0.00 (0%) to 99.99 (99.99%). Values with more than 2 digits beyond the decimal point will be truncated.
• 60%: 60.00
• 25.5%: 25.50
• 33.33%: 33.33
The valid range is between 0.00 (0%) to 99.99 (99.99%). Values with more than 2 digits beyond the decimal point will be truncated.
• 60%: 60.00
• 25.5%: 25.50
• 33.33%: 33.33
Specifications
• Data Length: 4
Elavon Americas
FDC Compass
• Data Length: 4
• Data Length: 6
• Data Length: 4
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
• Elavon Americas:
This field is a pass-though field, which means Cybersource does not verify the value or modify it in any way before sending it to the processor.
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Specifications
• Data Length: 4
Elavon Americas
• Data Length: 4
FDC Compass
• Data Length: 4
• Data Length: 4
• Data Length: 4
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Possible values:
• 5: Terminal can read contactless chip cards; cannot use contact to read chip cards.
Specifications
• Data Length: 1
Mapping Information
Possible values:
This field is supported only for Cybersource integrations. This field is not supported for FDC Nashville Global or SIX processors.
Specifications
• Data Length: 1
Mapping Information
Flag that indicates whether the terminal is compliant with standards mandated by the Reserve Bank of India for card-present domestic transactions in India.
Format:
• First character indicates whether the terminal supports terminal line encryption (TLE). Possible values:
◦ 1: Not certified
◦ 2: Certified
• Second character indicates whether the terminal supports Unique Key Per Transaction (UKPT) and Derived Unique Key Per Transaction (DUKPT). Possible values:
◦ 1: Not certified
◦ 2: Certified
Example: 21 indicates that the terminal supports TLE but does not support UKPT/DUKPT.
You and the terminal vendors are responsible for terminal certification. If you have questions, contact your acquirer.
This field is supported only for Mastercard transactions on Visa Platform Connect.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 92-93
Specifications
• Data Length: 2
Mapping Information
Possible values:
• PIN
• Signature
Specifications
• Data Length: 15
Mapping Information
This field is supported only for Mastercard transactions on FDC Nashville Global. Use the terminal_id field to identify the main terminal at your retail location. When your retail
location has multiple terminals, use the pointOfSaleInformation.laneNumber field to identify the terminal used for the transaction.
This field is a pass-through, which means that the value is not checked or modified in any way before it is sent to the processor.
Specifications
• Data Length: 8
Mapping Information
You defined the value for this field in the request message. This value must be printed on the receipt.
This field is supported only for Mastercard transactions on FDC Nashville Global.
Specifications
• Data Length: 8
Mapping Information
You can define this value yourself, but consult the processor for requirements.
To have your account configured to support this field, contact customer support. This value must be a value that FDC Nashville Global issued to you.
A list of all possible values is stored in your account. When terminal ID validation is enabled for your account, the value you send for this field is validated against the list each time
you include the field in a request. To enable or disable terminal ID validation, contact customer support.
When you do not include this field in a request, the default value in your account is used.
Specifications
• Data Length: 8
Mapping Information
Specifications
• Data Length: 8
Mapping Information
Possible values:
• Swiped: Terminal can accept card data from a magnetic stripe reader.
Specifications
• Data Length: 15
Possible values:
• 1: Neither
• 2: Print only
• 3:Display only
Specifications
• Data Length: 1
Mapping Information
Possible values:
• 4: Four characters
• 5: Five characters
• 6: Six characters
• 7: Seven characters
• 8: Eight characters
• 9: Nine characters
Specifications
• Data Length: 2
Mapping Information
This value is provided by the client software that is installed on the POS terminal.
This value is not sent to the processor. Instead, the value is forwarded to the Cybersource reporting software.
Specifications
• Data Length: 32
Mapping Information
Type of terminal.
Possible values:
Specifications
• Data Length: 2
Mapping Information
Value that identifies the application vendor and application version for a third party gateway.
You are provided with this value during testing and validation.
Specifications
• Data Length: 12
Mapping Information
Number of seconds the system waits before returning a timeout error. The default is 110 seconds.
Specifications
• Data Length: 3
Mapping Information
Indicates whether Cybersource should use a payment network token that is associated with a TMS token for an authorization.
Possible values:
• ignore: Use a tokenized card number for an authorization, even if the TMS token has an associated payment network token.
• prefer: Use an associated payment network token for an authorization if the TMS token has one; otherwise, use the tokenized card number.
Specifications
• Data Length: 6
Mapping Information
This field is returned only for merchant-initiated transactions with Elavon Americas.
This field is included in the response message when it decrypts the payment blob for the tokenized transaction.
Format: MM
Specifications
• Data Length: 2
Mapping Information
This field is returned only for merchant-initiated transactions with Elavon Americas.
This field is included in the response message when it decrypts the payment blob for the tokenized transaction.
Format: YYYY
Specifications
• Data Length: 4
Mapping Information
This field is returned only for merchant-initiated transactions with Elavon Americas.
This field is included in the response message when it decrypts the payment blob for the tokenized transaction.
Specifications
• Data Length: 6
Mapping Information
This field is returned only for merchant-initiated transactions with Elavon Americas.
This field is included in the response message when it decrypts the payment blob for the tokenized transaction.
Specifications
• Data Length: 4
Mapping Information
For Chase Paymentech Solutions, FDC Compass and RBS WorldPay Atlanta transactions, do not use all zeros or spaces in Mastercard transactions.
Specifications
Elavon Americas
OmniPay Direct
• Data Length: 12
• Data Length: 12
• Data Length: 12
Worldpay VAP
• Data Length: 8
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
• Elavon Americas:
This field is supported only for Cartes Bancaires Fast'R transactions on Credit Mutuel-CIC.
Specifications
• Data Length: 2
Mapping Information
◦ ccAuthService_totaloffersCount
◦ payerAuthEnrollService_totalOffersCount
Specifications
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Contains the tax type code that corresponds to the entry in the tax_amount field
Additional details for all processors and all txns (Level II/III and non-Level II/III).
Possible values:
Specifications
• Data Length: 3
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
For card-present transactions, this field applies to the card’s track 1 and 2 data. For PIN debit transactions, this field applies to track 2 data from the debit card; the sentinels are
required.
Card-present Transactions
• Track 1 data
Example:
In the following example, the card number is 4111111111111111, the expiration year is 16, and the expiration month is 12. The end sentinel (?) follows the final character of data
recorded on the track.
Example:
;4111111111111111=16121019761186800000?
Specifications
Mapping Information
Include both the date and time in this field or leave it blank.
Format: YYYYMMDDhhmmss
• MM = month
• YYYY = year
• DD = day
• hh = hour
• mm = minutes
• ss = seconds
Card-Present Transactions
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 16-21
Specifications
• Data Length: 14
Mapping Information
◦ ccIncrementalAuthService_transactionLocalDateTime
◦ transactionLocalDateTime
Format: YYYYMMDDhhmmss
• MM = month
• YYYY = year
• DD = day
• hh = hour
• mm = minutes
• ss = seconds
Specifications
• Data Length: 14
Mapping Information
A temporary ID that represents the customer's payment data (which is securely stored in Visa Data Centers).
Specifications
• Data Length: 64
Mapping Information
Possible values:
• 00: Use this value for debt recovery, more than one transportion mode, or an unknown transportation mode
• 04: Train
• 07: Toll
• 08: Parking
• 09: Taxi
• 13: Paratransit
• 16: Locomotive
• 18: Trailer
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 153-154
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
Mapping Information
This flag specifies whether the transaction is exempt from strong customer authentication (SCA) requirements in Europe because the customer trusts you.
Possible values:
• 1: Exempt from SCA requirements because the customer trusts the merchant.
For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 145-146
For transactions with other card types, the value for this field corresponds to the following data in the TC 33 capture file:
• Position: 8
• Data Length: 1
Mapping Information
Code that indicates whether the issuer honored or denied the customer's request for trusted merchant exemption.
Possible values:
Possible values:
• 00: Goods
• 01: Services
Specifications
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 126-157
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 32
Mapping Information
Universal cardholder authentication field (UCAF) collection indicator to which the transaction was downgraded.
Apple Pay and Samsung Pay: set the value of this field to 2.
The value for this field corresponds to the following data in the TC 33 capture file.
• Position: 5
The TC 33 Capture file contains information about the payments and credits that a merchant submits to Cybersource. Visa Platform Connect creates the TC 33 Capture file at the
end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
Specifications
• Data Length: 1
Mapping Information
This field is returned only for downgraded Mastercard Identity Check transactions on Visa Platform Connect.
When you set the e-commerce indicator to a value that indicates that Mastercard Identity Check data is included in the request, Mastercard provides this value when the
transaction is downgraded.
Possible values:
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 80
Specifications
• Data Length: 1
For American Express Direct, see the EDI codes for units of measurement at: http://ecomgx17.ecomtoday.com/edi/EDI_4010/el737.htm
For all other processors, see a list of available unit of measure codes at: Units of Measurement Codes
FDC Compass
Specifications
• Data Length: 12
Elavon Americas
FDC Compass
• Data Length: 12
GPN
• Data Length: 12
OmniPay Direct
• Data Length: 12
• Data Length: 12
• Data Length: 12
• Data Length: 12
Worldpay VAP
• Data Length: 12
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
It is recommended that you do not populate the field with all zeros or nines.
Specifications
• Data Length: 17
• Data Length: 25
Elavon Americas
• Data Length: 17
FDC Compass
• Data Length: 25
• Data Length: 25
FDMS Nashville
• Data Length: 25
FDMS South
• Data Length: 25
OmniPay Direct
• Data Length: 25
• Data Length: 25
• Data Length: 17
Worldpay VAP
• Data Length: 17
Mapping Information
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
Specifications
Elavon Americas
• Data Length: 15
• Data Length: 15
• Data Length: 15
• Data Length: 15
• Data Length: 15
Worldpay VAP
• Data Length: 15
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
If you do not provide this value, the rate is calculated as (national_tax x 100 / amount).
Specifications
FDMS South
• Data Length: 5
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The total amount of the Value Added Tax (VAT) or other tax included in the order.
Specifications
• Data Length: 13
Elavon Americas
• Data Length: 12
FDC Compass
GPN
• Data Length: 12
OmniPay Direct
• Data Length: 12
• Data Length: 8
• Length: 13
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
Flag that indicates if the VAT tax amount should be interpreted as positive or negative.
Possible values:
Specifications
• Data Length: 8
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
The Value Added Tax (VAT) or other tax rate used to calculate the tax applied to the order.
For RBS WorldPay Atlanta and TSYS Acquiring Solutions: The valid range is between .01 and 99.99 percent. The rate is entered as a decimal. For example:
• 60%: 0.6000
• 33.33%: 0.3333
• 25.5%: 0.2550
For Visa Platform Connect, the valid range is between 0.01 and 99.99 percent. The rate is entered as a percentage. For example:
• 60%: 60.00
• 33.33%: 33.33
• 25.5%: 25.50
For all other processors: The valid range is between 1 and 99 percent. The rate is entered as a decimal. For example:
• 60%: 0.60
• 33%: 0.33
• 25%: 0.25
Specifications
• Data Length: 4
Elavon Americas
• Data Length: 4
FDC Compass
• Data Length: 4
• Data Length: 5
GPN
• Data Length: 4
• Data Length: 4
• Data Length: 4
• Data Length: 6
• Data Length: 4
Mapping Information
Processor-specific field names for each processor supporting this field for Level II or Level III processing:
Visa Click to Pay provides a unique order ID for every transaction in the Visa Click to Pay callID field.
Specifications
• Data Length: 48
Mapping Information
This field is supported only on Asia, Middle East, and Africa Gateway.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_enroll_veres_enrolled response field.
Possible values:
• Y: Authentication available.
Specifications
• Data Length: 1
Mapping Information
The processor provides this value when a credit authorization reversal does not succeed.
Specifications
• Data Length: 3
Mapping Information
Possible values:
Specifications
• Type: Integer
• Length: 1
Mapping Information
Specifications
• Data Length: 26
Mapping Information
Value of the request token returned from a previous request for a service that you want to void.
This value is an encoded string that contains no confidential information, such as an account number or card verification number.
Specifications
Mapping Information
Specifications
• Type: String
• Length: 50
Mapping Information
Do not display this message to the customer, and do not use this field to write an error handler.
Specifications
• Type: String
• Length: 256
Mapping Information
Specifications
• Data Length: 15
Mapping Information
Specifications
• Data Length: 5
Mapping Information
PIN Debit
Time when the PIN debit credit, PIN debit purchase or PIN debit reversal was requested.
Returned by PIN debit credit, PIN debit purchase or PIN debit reversal.
Specifications
• Data Length: 20
Mapping Information
Type of wallet.
This field is supported only for Visa Click to Pay on FDC Compass, FDC Nashville Global, FDI Australia, TSYS Acquiring Solutions, and Visa Platform Connect.
On the following processors, the value that Cybersource sends to the processor is the value that the processor expects for this field:
• FDC Compass
• FDI Australia
This field is a passthrough; therefore, the value is not verified or modified in any way before it is sent to the processor.
The value for this field corresponds to the following data in the TC 33 capture file:
• Position: 72-76
• Data Length: 5
Mapping Information
Specifications
• Data Length: 9
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Type of weight
Possible values:
• B: Billed weight
Specifications
• Data Length: 1
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Code that specifies the unit of measurement for the weight amount.
The values are defined by the ANSI Accredited Standards Committee (ASC).
Specifications
• Data Length: 2
Mapping Information
The following list provides the Level II/Level III processor field name for each processor that supports Level II or Level III data:
Transaction identifier.
For Visa Secure on FDC Nashville Global, the CAVV field is set to the XID value when the XID is present in the authorization request and the CAVV is not present.
When you request the payer authentication and authorization services separately, get the value for this field from the pa_validate_xid response field.
• American Express: For a 20-byte cryptogram, set this field to the cryptogram for authorizations with payment network tokens. For a 40-byte cryptogram, set this field to
block A of the cryptogram for authorizations with payment network tokens. All cryptograms use one of these formats.
• Visa: The value for this field must be 28-character base64 or 40-character hex binary. All cryptograms use one of these formats.
Specifications
• Data Length: 40
Mapping Information