Transcription
Title PageCard-Present TransactionsSupplement to the Credit Card Services User GuideApril 2019CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095
CyberSource Contact InformationFor technical support questions, go to the Home page in the Business Center to see thecontact information appropriate for your account.Visit the Business Center, your central location for managing your online paymenttransactions, at https://businesscenter.cybersource.com.For general information about our company, products, and services, go tohttp://www.cybersource.com.For sales questions about any CyberSource Service, email sales@cybersource.com orcall 650-432-7350 or 888-330-2300 (toll free in the United States).Copyright 2019 CyberSource Corporation. All rights reserved. CyberSource Corporation (“CyberSource”) furnishes thisdocument and the software described in this document under the applicable agreement between the reader ofthis document (“You”) and CyberSource (“Agreement”). You may use this document and/or software only inaccordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the informationcontained in this document is subject to change without notice and therefore should not be interpreted in any wayas a guarantee or warranty by CyberSource. CyberSource assumes no responsibility or liability for any errorsthat may appear in this document. The copyrighted software that accompanies this document is licensed to Youfor use only in strict accordance with the Agreement. You should read the Agreement carefully before using thesoftware. Except as permitted by the Agreement, You may not reproduce any part of this document, store thisdocument 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.Restricted Rights LegendsFor Government or defense agencies. Use, duplication, or disclosure by the Government or defense agenciesis subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS252.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 setforth in CyberSource Corporation's standard commercial agreement for this software. Unpublished rightsreserved under the copyright laws of the United States.TrademarksAuthorize.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.All other brands and product names are trademarks or registered trademarks of their respective owners.2
CONTENTSContentsRecent Revisions to This DocumentAbout This Guide6Audience and PurposeConventions66Related DocumentationCustomer SupportChapter 177Introduction to Card-Present TransactionsSupported ProcessorsPrerequisitesChapter 25888Optional Features10Relaxed Requirements for Address Data and Expiration DateAppendix A API Fields1011XML Schema Versions11Formatting Restrictions12Data Type Definitions12Clear Text Request Field13General Card-Present Request FieldsCard-Present Transactions Supplement April 2019133
ContentsAppendix B Examples26Name-Value Pair Examples 26Sale Using Swiped Track DataSale Using Keyed Data 2726XML Examples 29Sale Using Swiped Track DataSale Using Keyed Data 3129Card-Present Transactions Supplement April 20194
ReleaseChangesApril 2019This revision contains only editorial changes and no technical updates.September 2017This revision contains only editorial changes and no technical updates.August 2017All processors: added information about the CyberSource APIs to theCyberSource web site. See the CyberSource API Versions page.REVISIONSRecent Revisions to ThisDocumentAll processors that support relaxed requirements: moved the relaxedrequirements information to a web page: Relaxed Requirements for AddressData and Expiration Date page.December 2016This revision contains only editorial changes and no technical updates.August 2016GPN: added support for pos catLevel field. See "General Card-PresentRequest Fields," page 13.March 2016Chase Paymentech Solutions, FDC Nashville Global, and GPN: addedsupport for relaxed requirements for address data and expiration dates. SeeRelaxed Requirements for Address Data and Expiration Date page.Card-Present Transactions Supplement April 20195
ABOUT GUIDEAbout This GuideAudience and PurposeThis guide is written for application developers who want to use the CyberSource SimpleOrder API to integrate credit card processing with card-present data into their ordermanagement system. The Credit Card Services User Guide provides the basicinformation about credit card processing with CyberSource. This supplement providesinformation about additional requirements and options for card-present transactions.Implementing the CyberSource credit card services requires software development skills.You must write code that uses the API request and reply fields to integrate the credit cardservices into your existing order management system.NoteInformation in this guide about Europay, Mastercard, and Visa (EMV) applies tocredit card processing and PIN debit processing. All other information in thisguide applies only to credit card processing. PIN debit processing is availableonly on FDC Nashville Global.ConventionsThe following special statements are used in this document:A Note contains helpful suggestions or references to material not contained inthis document.NoteAn Important statement contains information essential to successfullycompleting a task or learning a concept.ImportantCard-Present Transactions Supplement April 20196
About This GuideThe following text conventions are used in this document:Table 1Text ConventionsConventionMeaningBold API field names API service names Graphical user interface elements that you must act upon XML elements Code examples Values for API fields; for example:Screen textSet the ccAuthService run field to true.Related Documentation Getting Started with CyberSource Essentials (PDF HTML) describes how to getstarted using the Simple Order API. The CyberSource API Versions page provides information about the CyberSource APIversions. The Credit Card Services User Guide (PDF HTML) describes how to integrateCyberSource payment processing services into your business.Refer to the Support Center for complete CyberSource technical documentation:http://www.cybersource.com/support center/support documentationCustomer SupportFor support information about any CyberSource service, visit the Support ent Transactions Supplement April 20197
CHAPTERIntroduction toCard-Present Transactions1This supplement to the Credit Card Services User Guide describes card-presentprocessing with CyberSource.NoteInformation in this guide about Europay, Mastercard, and Visa (EMV) applies tocredit card processing and PIN debit processing. All other information in thisguide applies only to credit card processing. PIN debit processing is availableonly on FDC Nashville Global.Supported ProcessorsCyberSource supports card-present credit card transactions for the processors shown inthe following table.Table 2Processors that CyberSource Supports for Card-Present TransactionsProcessorMagnetic StripeChase Paymentech SolutionsYesFDC Nashville GlobalYesFDMS NashvilleYesGPNYesRBS WorldPay AtlantaYesTSYS Acquiring SolutionsYesPrerequisitesBefore you start your implementation: Contact your acquirer to find out whether you are allowed to process card-presenttransactions. Find out from your acquirer and CyberSource Customer Support whether you musthave a separate CyberSource merchant ID for your card-present transactions.Card-Present Transactions Supplement April 20198
Chapter 1Introduction to Card-Present Transactions Contact CyberSource Customer Support to have your account configured to processcard-present transactions. Make sure that you are familiar with the CyberSource Simple Order API for processinge-commerce and mail order/telephone order (MOTO) transactions as described inCredit Card Services User Guide. The request and reply fields for card-presenttransactions are very similar to the request and reply fields for e-commerce andMOTO transactions.Table 3Card-Present Fields in Service Requests and RepliesService RequestDescriptionAuthorization requestA card-present authorization request includes additional fieldsand several existing authorization request fields have differentrequirements when the request is for a card-present transaction.Authorization replyA card-present authorization reply includes the same fields thatare included for an e-commerce or MOTO transaction.Capture requestA card-present capture request includes the same fields that areincluded for an e-commerce or MOTO transaction.Capture replyA card-present capture reply includes the same fields that areincluded for an e-commerce or MOTO transaction.Card-Present Transactions Supplement April 20199
CHAPTEROptional Features2Relaxed Requirements for Address Dataand Expiration DateTo enable relaxed requirements for address data and expiration date, contactCyberSource Customer Support to have your account configured for this feature. Fordetails about relaxed requirements, see the Relaxed Requirements for Address Data andExpiration Date page.Card-Present Transactions Supplement April 201910
APPENDIXAPI FieldsImportantAWhen you send an authorization request that includes card-present data, youmust include the basic fields required for every authorization request. Forinformation about card-not-present fields required for these requests, see theCredit Card Services User Guide.XML Schema VersionsFor general information about the XML schema versions, see Getting Started withCyberSource Essentials. The following table specifies the Simple Order API version to usefor each processor for clear-text card-present transactions.Table 4Simple Order API XML Schema Versionsfor Card-Present TransactionsProcessorVersion for ClearText TransactionsChase Paymentech Solutions1.25 or laterFDC Nashville Global1.24 or laterFDMS Nashville1.29 or laterGPN1.26 or laterRBS WorldPay Atlanta1.48 or laterTSYS Acquiring Solutions1.13 or laterCard-Present Transactions Supplement April 201911
Appendix AAPI FieldsFormatting RestrictionsUnless otherwise noted, all field names are case sensitive and all fields accept specialcharacters such as @, #, and %.The values of the item # fields must not contain carets ( ) or colons (:)because these characters are reserved for use by the CyberSource services.NoteValues for request-level and item-level fields must not contain new lines orcarriage returns. However, they can contain embedded spaces and any otherprintable characters. CyberSource removes all leading and trailing spaces.Data Type DefinitionsFor more information about these data types, see the World Wide Web Consortium (W3C)XML Schema Part 2: Datatypes Second Edition.Table 5Data Type DefinitionsData TypeDescriptionIntegerWhole number {., -3, -2, -1, 0, 1, 2, 3, .}StringSequence of letters, numbers, spaces, and special charactersCard-Present Transactions Supplement April 201912
Appendix AAPI FieldsClear Text Request FieldTable 6Clear Text Request FieldFieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthpos trackDataCard’s track 1 and 2 data. For all processorsexcept FDMS Nashville, this value consists ofone of the following:ccAuthService(Required if posentryMode swiped;otherwise, not used)String (119) Track 1 data Track 2 data Data for both tracks 1 and 2For FDMS Nashville, this value consists of oneof the following: Track 1 data Data for both tracks 1 and 2Example %B4111111111111111 SMITH/JOHN 1612101976110000868000000?;4111111111111111 16121019761186800000?General Card-Present Request FieldsTable 7General Card-Present Request FieldsFieldDescriptionUsed By:Required (R)or Optional (O)Data Type& LengthbillTo cityCredit card billing city.ccAuthService:String (50)1 Chase PaymentechSolutions: optional. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:not used.This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201913
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& LengthbillTo countryCredit card billing country. Use the twocharacter ISO Standard Country Codes.ccAuthService:String (2)billTo emailbillTo firstName1Customer’s email address, including fulldomain name.Format: name@host.domainCustomer’s first name. Value should matchvalue on card. Chase PaymentechSolutions: optional. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:not used.ccAuthService: Chase PaymentechSolutions: optional. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:not used.ccAuthService: Chase PaymentechSolutions: optional. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:not used.String (255)String (60)This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201914
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& LengthbillTo lastNameCustomer’s last name. Value should matchvalue on card.ccAuthService:String (60)billTo phoneNumber1Customer’s phone number. CyberSourcerecommends that you include the country codewhen order is from outside the U.S. Chase PaymentechSolutions: optional. RBS WorldPayAtlanta: optional. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:not used.ccAuthService: Chase PaymentechSolutions: optional. TSYS AcquiringSolutions: optional. All other processors:not used.String (15)This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201915
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& LengthbillTo postalCodePostal code for billing address. Postal codemust consist of 5 to 9 digits.ccAuthService:String (10) FDMS Nashville:required if posentryMode keyedand the address is inthe U.S. or Canada.Optional if posentryMode keyedand the address is notin the U.S. orCanada. Not used ifswiped. RBS WorldPayAtlanta: for best cardpresent keyed rates,send the postal codeif posentryMode keyed. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:optional.When the billing country is U.S., the9-digit postal code must follow this format:[5 digits][dash][4 digits]Example 12345-6789When the billing country is Canada, the 6-digitpostal code must follow this ha][numeric]Example A1B 2C3billTo state1Credit card billing state or province. Use State,Province, and Territory Codes for the UnitedStates and Canada.ccAuthService: Chase PaymentechSolutions: optional. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:not used.String (2)This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201916
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& LengthbillTo street1Credit card billing street address as it appearsin credit card issuer’s records.ccAuthService:FDMSNashville:String (20)FDMS Nashville:When the street name is numeric, it must besent in numeric format. For example, if theaddress is One First Street, it must be sent as1 1st Street.billTo street2Used for additional address information. Forexample:Attention: Accounts Payable FDMS Nashville:required if keyed; notused if swiped. TSYS AcquiringSolutions: requiredwhenccAuthServicebillPayment trueand posentryMode keyed. All other processors:optional.ccAuthService (O)1Customer’s credit card number.FDMSNashville:String (20)All otherprocessors:String (60)FDMS Nashville:billTo street1 and billTo street2 togethercannot exceed 20 characters.card accountNumberAll otherprocessors:String (60)ccAuthService: FDMS Nashville:required. All other processors:required if posentryMode keyed.FDMSNashville:String withnumbersonly (19)All otherprocessors:String withnumbersonly (20)This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201917
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthcard cardTypeType of card to authorize. Possible values:ccAuthService(Required for CarteBlanche and JCB.Optional for other cardtypes.)String (3) card cvIndicator001: Visa002: Mastercard003: American Express004: Discover005: Diners Club006: Carte Blanche007: JCBIndicates whether a CVN code was sent.Possible values: ImportantCyberSource stronglyrecommends that yousend the card type evenwhen it is optional foryour processor and cardtype. Omitting the cardtype can cause thetransaction to beprocessed with thewrong card type.ccAuthService: FDMS Nashville:required for AmericanExpress; otherwise,optional. TSYS AcquiringSolutions: optional ifpos entryMode keyed; otherwise,not used. All other processors:optional.0 (default): CVN service not requested.CyberSource uses this default when you donot include card cvNumber in the request. 1 (default): CVN service requested andsupported. CyberSource uses this defaultwhen you include card cvNumber in therequest.1 2: CVN on credit card is illegible. 9: CVN not imprinted on credit card.String withnumbersonly (1)This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201918
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthcard cvNumberCVN. See CVN information in Credit CardServices User Guide.ccAuthService:String withnumbersonly (4)card expirationMonthcard expirationYearccAuthServicebillPaymentTwo-digit month in which credit card expires.Format: MM.Possible values: 01 through 12. Leading 0 isrequired.Four-digit year in which credit card expires.Format: YYYY.Indicates payment for bill or payment towardsexisting contractual loan. For information aboutVisa Bill Payments and Visa DebtRepayments, see Credit Card Services UserGuide. Possible values: true: Bill payment or loan payment. false (default): Not a bill payment or loanpayment. FDMS Nashville:required for AmericanExpress or if swiped;otherwise, optional. TSYS AcquiringSolutions: optional ifpos entryMode keyed; otherwise,not used. All other processors:optional.ccAuthService: FDMS Nashville:required. All other processors:required if posentryMode keyed.1ccAuthService: FDMS Nashville:required. All other processors:required if posentryMode keyed.1String (2)String (4)ccAuthService (O)String (5)ccAuthServicecommerceIndicatorType of transaction. For a card-presenttransaction, you must set this field to retail.ccAuthService (R)String (13)ccAuthService runSet to true to request credit cardauthorization.ccAuthService (R)String (255)1This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201919
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthitem # productCodeType of product. This value is used to identifythe product category (electronic, handling,physical, service, or shipping). The defaultvalue is default. For a list of valid values,see the information about product codes inCredit Card Services User Guide.ccAuthService (O)String (30)When this field is not set to default or oneof the values related to shipping and/orhandling, the item # quantity, item #productName, and item # productSKUfields are required. For information about itemsand grand totals, see Getting Started withCyberSource Essentials.item # productNameRequired when item # productCode is notdefault or one of the values related toshipping and/or handling.ccAuthService(See description)String (30)item # productSKUProduct identifier code. Required when item# productCode is not default or one of thevalues related to shipping and/or handling.ccAuthService(See description)String (15)item # quantityDefault is 1. Required when item #productCode is not default or one of thevalues related to shipping and/or handling.ccAuthService(See description)Integer (10)item # taxAmountTotal tax to apply to the product. This valuecannot be negative. The tax amount and theunit price must be in the same currency.ccAuthService (O)String (15)The tax amount field is additive. The followingexample uses a two-exponent currency suchas USD:1 You include the following items in yourrequest:item 0 unitPrice 10.00item 0 quantity 1item 0 taxAmount 0.80item 1 unitPrice 20.00item 1 quantity 1item 1 taxAmount 1.602 The total amount authorized will be 32.40,not 30.00 with 2.40 of tax included.1This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201920
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthitem # unitPricePer-item price of the product. You must includeeither this field or purchaseTotalsgrandTotalAmount in your request. Thisvalue cannot be negative. For informationabout items and grand totals, see GettingStarted with CyberSource Essentials.ccAuthService(See description)For GPN:String (10)All otherprocessors:String (15)You can include a decimal point (.) in the valuefor this field, but you cannot include any otherspecial characters. CyberSource truncates theamount to the correct number of decimalplaces.merchantIDYour CyberSource merchant ID.ccAuthService (R)String (30)merchantReferenceCodeMerchant-generated order reference ortracking number. CyberSource recommendsthat you send a unique value for eachtransaction so that you can perform meaningfulsearches for the transaction. For informationabout tracking orders, see Getting Started withCyberSource Essentials.ccAuthService (R)String (50)ccAuthService:String (1)FDC Nashville Global:This value must be numeric and must be lessthan 9 digits. When you do not send a validvalue, CyberSource creates one for you.However, the value is not returned to you, soyou cannot use the merchant referencenumber to track the order.pos cardPresentIndicates whether the card is present at thetime of the transaction. Possible values: 1N: Card is not present.Y: Card is present. FDMS Nashville: notused. All other processors:required.This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201921
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthpos catLevelType of cardholder-activated terminal.Possible values:ccAuthService:Nonnegativeinteger (1) 1: Automated dispensing machine 2: Self-service terminal 3: Limited amount terminal 6: Mobile acceptance terminalChase Paymentech SolutionsOnly values 1, 2, and 3 are supported. Chase PaymentechSolutions: required ifpos terminalID isincluded in therequest; otherwise,optional. GPN: required. TSYS AcquiringSolutions: required fortransactions frommobile devices;otherwise, not used. All other processors:not used.GPNOnly value 6 is supported.TSYS Acquiring SolutionsOnly value 6 is supported.pos entryModeMethod of entering credit card information intothe POS terminal. Possible values: keyed: Manually keyed into POS terminal. swiped: Read from credit card magneticccAuthService (R)String (11)ccAuthService:Integer (1)stripe.pos terminalCapabilityPOS terminal’s capability. Possible values: 1: Terminal has a magnetic stripe readeronly. Chase PaymentechSolutions: required. 2: Terminal has a magnetic stripe readerand manual entry capability. FDC NashvilleGlobal: required. 3: Terminal has manual entry capability FDMS Nashville:required. GPN: optional. RBS WorldPayAtlanta: optional. TSYS AcquiringSolutions: optional.only.1This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201922
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& Lengthpos terminalIDIdentifier for the terminal at your retail location.You can define this value yourself, but consultthe processor for requirements.ccAuthService:String (8)FDC Nashville GlobalTo have your account configured to supportthis field, contact CyberSource CustomerSupport. This value must be a value that FDCNashville Global issued to you.posterminalIDAlternateIdentifier for an alternate terminal at your retaillocation. You define the value for this field.This field is supported only for Mastercardtransactions on FDC Nashville Global. Use thepos terminalID field to identify the mainterminal at your retail location. If your retaillocation has multiple terminals, use this posterminalIDAlternate field to identify theterminal used for the transaction. Chase PaymentechSolutions: optional. Ifyou include this fieldin your request, youmust also includepos catLevel. FDC NashvilleGlobal: optional. If notprovided,CyberSource usesthe value in yourCyberSourceaccount. FDMS Nashville:CyberSource usesthe value in yourCyberSourceaccount. GPN: not used. RBS WorldPayAtlanta: not used. TSYS AcquiringSolutions: not used.ccAuthService: FDC NashvilleGlobal: optional forMastercardtransactions;otherwise, not used. All other processors:not used.String (8)This field is a pass-through, which means thatCyberSource does not check the value ormodify the value in any way before sending itto the processor.purchaseTotalscurrency1Currency used for order. For possible values,see ISO Standard Currency Codes.ccAuthService (R)String (5)This field is optional if your CyberSource account is configured for relaxed requirements for address data and expiration date. See"Relaxed Requirements for Address Data and Expiration Date," page 10. Important It is your responsibility to determine whethera field is required for the transaction you are requesting.Card-Present Transactions Supplement April 201923
Appendix ATable 7API FieldsGeneral Card-Present Request Fields (Continued)FieldDescriptionUsed By:Required (R)or Optional (O)Data Type& LengthpurchaseTotalsgrandTotalAmountGrand total for the order. You must includeeither this field or item # unitPrice in yourrequest. For information about items and grandtotals, see Getting Started with CyberSourceEssentials.ccAuthService(See description)S
management system. The Credit Card Services User Guide provides the basic information about credit card processing with CyberSource. This supplement provides information about additional requirements and options for card-present transactions. Implementing the CyberSource credit card services requires software development skills.
