Академический Документы
Профессиональный Документы
Культура Документы
Authorize.Net LLC (Authorize.Net) has made efforts to ensure the accuracy and completeness of the information in this document. However, Authorize.Net disclaims all representations, warranties and conditions, whether express or implied, arising by statute, operation of law, usage of trade, course of dealing or otherwise, with respect to the information contained herein. Authorize.Net assumes no liability to any party for any loss or damage, whether direct, indirect, incidental, consequential, special or exemplary, with respect to (a) the information; and/or (b) the evaluation, application or use of any product or service described herein. Authorize.Net disclaims any and all representation that its products or services do not infringe upon any existing or future intellectual property rights. Authorize.Net owns and retains all right, title and interest in and to the Authorize.Net intellectual property, including without limitation, its patents, marks, copyrights and technology associated with the Authorize.Net services. No title or ownership of any of the foregoing is granted or otherwise transferred hereunder. Authorize.Net reserves the right to make changes to any information herein without further notice. Authorize.Net Trademarks: Authorize.Net Authorize.Net Your Gateway to IP Transactions Authorize.Net Verified Merchant Seal Authorize.Net Where the World Transacts Automated Recurring Billing eCheck.Net Fraud Detection Suite FraudScreen.Net
Table of Contents
Revision History ................................................................................ 3 Section 1 ........................................................................................... 4 Developer Introduction ..................................................................... 4
Minimum Requirements .................................................................................................... 4 Developer Support ............................................................................................................ 5
Revision History
PUBLISH DATE November 2007 UPDATES Initial release of the Customer Information Manager (CIM) API
Minimum Requirements
Before you begin this integration for an Authorize.Net Payment Gateway account, please check with the merchant to make sure that the following minimum requirements have already been met.
The merchant must have a U.S. based merchant bank account that allows Internet transactions. The merchant must have an active Authorize.Net Card Not Present Payment Gateway account. The merchant must be signed up for the CIM service. The merchant must store account authentication data securely (for example, API login ID, transaction key).
Note: Merchants should avoid storing any type of sensitive cardholder information. However, in the event that a merchant or third party must store sensitive customer business or payment information, compliance with industry standard storage requirements is required. Please see the Developer Security Best Practices White Paper at http://www.authorize.net/files/developerbestpractices.pdf for guidelines.
Developer Support
There are several resources available to help you successfully integrate a merchant Web site or other application to the Authorize.Net Payment Gateway. The Integration Center at http://developer.authorize.net provides test accounts, sample code, FAQs, and troubleshooting tools. If you cant find what you need in the Integration Center, our Integration Team is available to answer your questions via e-mail at integration@authorize.net. Be sure to read our Developer Security Best Practices White Paper at http://www.authorize.net/files/developerbestpractices.pdf for information on how to maximize the security and reliability of your merchant integration solutions.
If you have any suggestions about how we can improve or correct this guide, please e-mail documentation@authorize.net.
Note: The Developer Test URL requires the use of a developer test payment gateway account. You can request a test account from our Integration Center at http://developer.authorize.net/testaccount. Developer test accounts cannot be used to test against the Production URL.
CIM Functions
The CIM API includes the following functions:
CreateCustomerProfile Create a new customer profile along with any customer payment profiles and customer shipping addresses for the customer profile. CreateCustomerPaymentProfile Create a new customer payment profile for an existing customer profile. CreateCustomerShippingAddress Create a new customer shipping address for an existing customer profile.
CreateCustomerProfileTransaction Create a new payment transaction from an existing customer profile DeleteCustomerProfile Delete an existing customer profile along with all associated customer payment profiles and customer shipping addresses. DeleteCustomerPaymentProfile Delete a customer payment profile from an existing customer profile. DeleteCustomerShippingAddress Delete a customer shipping address from an existing customer profile. GetCustomerProfile Retrieve an existing customer profile along with all the associated customer payment profiles and customer shipping addresses. GetCustomerPaymentProfile Retrieve a customer payment profile for an existing customer profile. GetCustomerShippingAddress Retrieve a customer shipping address for an existing customer profile. UpdateCustomerProfile Update an existing customer profile. UpdateCustomerPaymentProfile Update a customer payment profile for an existing customer profile. UpdateCustomerShippingAddress Update a shipping address for an existing customer profile. ValidateCustomerPaymentProfile Verify an existing customer payment profile by generating a test transaction.
The following sections provide information about the input parameters required for executing the functions listed above. Indentations in the Parameter column indicate grouping hierarchy. All parameters are case sensitive and must be submitted in the order listed here. Parameters are required unless otherwise indicated. Optional parameters should not be submitted unless they contain valid values. Note: Parameters required for individual API calls are in addition to the authentication parameters required for all API calls.
Authentication
All Web services calls must be authenticated to ensure they originate from authorized sources. This implementation of the merchant Web services API supports authentication using the API Login ID and Transaction Key.
PARAMETER merchantAuthentication VALUE Contains merchant unique information for purposes of authentication The valid API Login ID for the developer test or merchant account The valid Transaction Key for the developer test or merchant account TYPE/FORMAT MerchantAuthentication Type 20 Submit the API Login ID used to submit transactions. Submit the Transaction Key obtained from the Merchant Interface. NOTES
name
transactionKey
16
The authentication information with the merchants Login ID and Transaction Key is sent in SOAP body, as shown below:
<soap:Body> <FunctionName xmlns="https://api.authorize.net/soap/v1/"> <merchantAuthentication> <name>API Login ID here</name> <transactionKey>Transaction Key here</transactionKey> </merchantAuthentication> Additional required parameters here </FunctionName> </soap:Body>
Note: The sample code included in this document uses dummy field values. When using or testing sample code, be sure to enter valid field values. Additional sample code is available for download from the Authorize.Net Integration Center at http://developer.authorize.net/samplecode.
merchantCustomerId
Up to 20 characters
FIELD
VALUE
TYPE/FORMAT
NOTES this parameter and its children may be submitted to create multiple payment profiles for the customer profile.
payment Type profiles for the customer profile Optional customerType Optional CustomerTypeEnum individual business billTo address firstName The customers first name Optional lastName The customers last name Optional company The name of the company associated with the customer, if applicable Optional address The customers address Optional city The city of the customers address Optional state The state of the customers address Optional zip The ZIP code of Up to 20 characters (no symbols) the customers address Optional country The country of the customers address Optional Up to 60 characters (no symbols) A valid two-character state code Up to 40 characters (no symbols) Up to 60 characters (no symbols) Up to 50 characters (no symbols) Up to 50 characters (no symbols) CustomerAddressType NameAndAddressType Up to 50 characters (no symbols)
FIELD phoneNumber
VALUE The phone number associated with the customer profile Optional faxNumber
NOTES
The fax number Up to 25 digits (no associated with letters) the customer profile Ex. (123)123-1234 Optional
payment
Contains payment profile information for the customer profile Contains credit card payment information for the payment profile The customers credit card number The expiration date for the customers credit card
PaymentSimpleType
creditCard
CreditCardSimpleType
This parameter and its children only are required when the payment profile is credit card.
cardNumber
13 to 16 digits
expirationDate
YYYY-MM
For .Net users, the class System.Runtime.Remo ting.Metadata.W3cXsd 2001.SoapYearMonth can be used to manage gYearMonth types. This parameter and its children only are required when the payment profile is bank account.
bankAccount
Contains bank account payment information for the payment profile The type of bank account for the payment profile Optional
BankAccountType
accountType
nameOnAccount
echeckType
10
FIELD
The name of Up to 50 characters the bank associated with the bank account number Optional
routingNumber
The routing number of the customers bank The customers bank account number Contains drivers license information for the customer profile Conditional
9 digits
accountNumber
5 to 17 digits
driversLicense
DriversLicenseType
This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants
state
This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter is only required for Wells Fargo SecureSource eCheck.Net merchants
number
5 to 20 characters
dateOfBirth
YYYY-MM-DD
taxId
9 digits
shipToList
CustomerAddressType
11
FIELD
VALUE profile address Contains address information for the customer profile The customers first name Optional lastName The customers last name Optional company The name of the company associated with the customer, if applicable Optional address The customers shipping address Optional city The city of the customers shipping address Optional state The state of the customers shipping address Optional zip
TYPE/FORMAT
NOTES
NameAndAddressType
firstName
The ZIP code of Up to 20 characters (no the customers symbols) shipping address Optional
country
phoneNumber
12
FIELD
TYPE/FORMAT
NOTES
Ex. (123)123-1234
The fax number Up to 25 digits (no associated with letters) the customer profile Ex. (123)123-1234 Optional
For information about output for this function, see the section of this document titled Output Parameters for CreateCustomerProfileResponse.
Example CreateCustomerProfile <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Body> <CreateCustomerProfile xmlns="https://api.authorize.net/soap/v1/"> <merchantAuthentication> <name>API Login ID here</name> <transactionKey>Transaction Key here</transactionKey> </merchantAuthentication> <profile> <merchantCustomerId>Merchant Customer ID here</merchantCustomerId> <description>Profile description here</description> <email>customer profile email address here</email> <paymentProfiles> <CustomerPaymentProfileType> <customerType>individual</customerType> <payment> <creditCard> <cardNumber>Credit card number here</cardNumber> <expirationDate>Credit card expiration date here</expirationDate> </creditCard> </payment> </CustomerPaymentProfileType> </paymentProfiles> </profile> </CreateCustomerProfile> </soap:Body> </soap:Envelope>
Note: The sample code included in this document uses dummy field values. When using or testing sample code, be sure to enter valid field values. Additional sample code is available for download from the Authorize.Net Integration Center at http://developer.authorize.net/samplecode.
13
paymentProfile
customerType
billTo address firstName The customers first name Optional lastName The customers last name Optional company
The name of the Up to 50 characters (no company associated symbols) with the customer, if applicable Optional
address
city
state
zip
14
FIELD
VALUE
TYPE/FORMAT
NOTES
Optional country The country of the customers address Optional phoneNumber The phone number associated with the customers address Optional faxNumber The fax number associated with the customers address Optional payment Contains payment information for the customer profile PaymentSimpleType Can contain CreditCardSimpleType or BankAccountType. This parameter and its children only are required when the payment profile is credit card. Up to 25 digits (no letters) Ex. (123)123-1234 Up to 25 digits (no letters) Ex. (123)123-1234 Up to 60 characters (no symbols)
creditCard
Contains credit card CreditCardSimpleType payment information for the customer profile The customers credit card number The expiration date for the customers credit card 13 to 16 digits YYYY-MM
cardNumber expirationDate
For .Net users, the class System.Runtime.Remoti ng.Metadata.W3cXsd20 01.SoapYearMonth can be used to manage gYearMonth types. This parameter and its children only are required when the payment profile is bank account.
bankAccount
Contains bank account payment information for the customer profile The type of bank account for the payment profile Optional
BankAccountType
accountType
nameOnAccount
The customers full name as listed on the bank account The type of electronic check transaction Optional
echeckType
Currently, the CIM API does not support ARC or BOC transaction types
15
FIELD bankName
VALUE The name of the bank associated with the bank account number Optional routingNumber The routing number of the customers bank The customers bank account number Contains the customers drivers license information Conditional state The state of the customers drivers license
TYPE/FORMAT Up to 50 characters
NOTES
9 digits
accountNumber
5 to 17 digits
driversLicense
DriversLicenseType
This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter is only required for Wells Fargo SecureSource eCheck.Net merchants Validation mode allows you to generate a test transaction at the time you create a customer payment profile. In Test Mode, only field validation is preformed. In Live Mode, a transaction is generated and submitted to the processor with the amount of $0.01. If successful, the transaction is immediately voided.
number
5 to 20 characters
dateOfBirth
YYYY-MM-DD
taxId
9 digits
validationMode
Indicates the ValidationModeEnum processing mode for the request none testMode liveMode
16
FIELD
VALUE
TYPE/FORMAT
For information about output parameters for this function, see the section of this document titled Output Parameters for CreateCustomerPaymentProfileResponse.
address
CustomerAddressType
address firstName The customers first name Optional lastName The customers last name Optional company
The name of the company Up to 50 characters (no associated with the symbols) customer, if applicable Optional
address
city
state
zip
Up to 20 characters (no
17
FIELD
VALUE customers shipping address Optional country The country of the customers shipping address Optional
TYPE/FORMAT symbols)
NOTES
phoneNumber
The phone number associated with the customers shipping address Optional
faxNumber
The fax number associated with the customers shipping address Optional
For information about output parameters for this function, see the section of this document titled Output Parameters for CreateCustomerShippingAddressResponse.
The credit card ProfileTransCaptureOnlyType transaction type that is being requested ProfileTransAuthCaptureType
ProfileTransAuthOnlyType
This amount should include all other amounts such as tax amount, shipping
18
FIELD
VALUE
TYPE/FORMAT
tax
Contains tax information for the transaction Optional amount The tax amount for the transaction Optional name The name of the tax for the transaction Optional description The tax description for the transaction Optional
ExtendedAmountType
Up to 4 digits with a decimal point (no dollar symbol) Ex. 4.95 Up to 31 characters
This amount must be included in the total amount for the transaction.
Up to 255 characters
shipping
ExtendedAmountType
amount
This amount must be included in the total amount for the transaction.
name
Up to 31 characters
description
Up to 255 characters
duty
ExtendedAmountType
amount
19
FIELD
VALUE Optional name The name of the duty for the transaction Optional description The duty description for the transaction Optional lineItems Contains line item details about the order Optional
TYPE/FORMAT
Up to 31 characters
Up to 255 characters
LineItemType
Up to 30 distinct instances of this parameter and its children may be included per transaction to describe items included in the order.
itemId
Up to 31 characters
name
Up to 31 characters
description
Up to 255 characters
quantity
unitPrice
Cost of an item Up to 4 digits with a decimal per unit point (no dollar symbol) excluding tax, freight, and duty Ex. 4.95 Optional
taxable
TRUE FALSE
20
FIELD customerProfileId
VALUE Payment gateway assigned ID associated with the customer profile Payment gateway assigned ID associated with the customer payment profile Payment gateway assigned ID associated with the customer shipping address Optional order Contains information about the order Optional invoiceNumber The merchant assigned invoice number for the transaction Optional description The transaction description Optional purchaseOrderNumber The merchant assigned purchase order number Optional taxExempt The tax exempt status Optional recurringBilling The recurring billing status Optional cardCode The customers
TYPE/FORMAT Numeric
NOTES
customerPaymentProfileId
Numeric
customerAddressId
If the customer AddressId is not passed, shipping information will not be included with the transaction. OrderExType
TRUE FALSE
TRUE FALSE
3 to 4 digits
This field is
21
FIELD
VALUE card code (the three- or fourdigit number on the back or front of a credit card) Required only when the merchant would like to use the Card Code Verification (CCV) filter Conditional approvalCode The authorization code of an original transaction required for a Capture Only Conditional
TYPE/FORMAT
NOTES required if the merchant would like to use the CCV security feature. For more information, please see the Merchant Integration Guide at http://www.auth orize.net/suppor t/Merchant/defa ult.htm.
6 characters
This parameter is only required for the Capture Only transaction type.
For information about output parameters for this function, see the section of this document titled Output Parameters for CreateCustomerProfileTransactionResponse.
For information about output parameters for this function, see the section of this document titled Output Parameters for DeleteCustomerProfileResponse.
22
FIELD customerProfileId
VALUE Payment gateway assigned ID associated with the customer profile Payment gateway assigned ID associated with the customer payment profile
TYPE/FORMAT Numeric
NOTES
customerPaymentProfileId
Numeric
For information about output parameters for this function, see the section of this document titled Output Parameters for DeleteCustomerPaymentProfileResponse.
customerAddressId
Numeric
For information about output parameters for this function, see the section of this document titled Output Parameters for DeleteCustomerShippingAddressResponse.
For information about output parameters for this function, see the section of this document titled Output Parameters for GetCustomerProfileResponse.
23
customerPaymentProfileId
Numeric
For information about output parameters for this function, see the section of this document titled Output Parameters for GetCustomerPaymentProfileResponse.
customerAddressId
Numeric
For information about output parameters for this function, see the section of this document titled Output Parameters for GetCustomerShippingAddressResponse.
24
customer profile merchantCustomerId Merchant assigned ID for the customer Optional description Description of the customer or customer profile Optional email Email address associated with the customer profile Optional customerProfileId Payment gateway Numeric assigned ID associated with the customer profile Up to 255 characters Up to 255 characters Up to 20 characters
For information about output parameters for this function, see the section of this document titled Output Parameters for UpdateCustomerProfileResponse.
paymentProfile
CustomerPaymentProfil eExType
customerType
billTo address firstName The customers first name Optional lastName The customers last
Up to 50 characters (no
25
FIELD
TYPE/FORMAT symbols)
NOTES
The name of the Up to 50 characters (no company associated symbols) with the customer, if applicable Optional
address
city
state
zip
country
phoneNumber
faxNumber
payment
PaymentSimpleType
Can contain CreditCardSimpleTyp e or BankAccountType. This parameter and its children only are required when the payment profile is credit card.
creditCard
Contains credit card CreditCardSimpleType payment information for the customer profile The customers credit card number 13 to 16 digits
cardNumber
26
FIELD expirationDate
TYPE/FORMAT YYYY-MM
NOTES For .Net users, the class System.Runtime.Rem oting.Metadata.W3cXs d2001.SoapYearMont h can be used to manage gYearMonth types. This parameter and its children only are required when the payment profile is bank account.
bankAccount
Contains bank account payment information for the customer profile The type of bank account for the payment profile Optional
BankAccountType
accountType
nameOnAccount
The customers full name as listed on the bank account The type of electronic check transaction Optional
echeckType
Currently, the CIM API does not support ARC or BOC transaction types
bankName
The name of the bank associated with the bank account number Optional
routingNumber
The routing number of the customers bank The customers bank account number Contains the customers drivers license information Conditional
9 digits
accountNumber
5 to 17 digits
driversLicense
DriversLicenseType
This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants
state
27
FIELD number
VALUE The customers drivers license number Conditional dateOfBirth The date of birth listed on the customers drivers license Conditional
TYPE/FORMAT 5 to 20 characters
NOTES This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter and its children are only required for Wells Fargo SecureSource eCheck.Net merchants This parameter is only required for Wells Fargo SecureSource eCheck.Net merchants
YYYY-MM-DD
taxId
9 digits
customerPaymentProfileId
Numeric
For information about output parameters for this function, see the section of this document titled Output Parameters for UpdateCustomerPaymentProfileResponse.
FIELD customerProfileId
VALUE Payment gateway assigned ID associated with the customer profile Contains shipping address information for the customer profile
TYPE/FORMAT Numeric
NOTES
address
CustomerAddressExType
address firstName The customers first name Optional lastName The customers last name
28
FIELD
VALUE
TYPE/FORMAT
NOTES
Optional company The name of the company associated with the customer, if applicable Optional address The customers shipping address Optional city The city of the customers shipping address Optional state The state of the customers shipping address Optional zip The ZIP code of the customers shipping address Optional country The country of the customers shipping address Optional phoneNumber The phone number associated with the customers shipping address Optional faxNumber The fax number associated with the customers shipping address Optional customerAddressId Payment gateway assigned ID associated with the customer shipping address Numeric Up to 25 digits (no letters) Ex. (123)123-1234 Up to 25 digits (no letters) Ex. (123)123-1234 Up to 60 characters (no symbols) Up to 20 characters (no symbols) A valid two-character state code Up to 40 characters (no symbols) Up to 60 characters (no symbols) Up to 50 characters (no symbols)
For information about output parameters for this function, see the section of this document titled Output Parameters for UpdateCustomerShippingAddressResponse.
29
customerPaymentProfileId
Numeric
customerAddressId
Numeric
If the customer AddressId is not passed, shipping information will not be included with the transaction. Validation mode allows you to generate a test transaction in either Test Mode or Live Mode to check the validity of customer information. In Test Mode, only field validation is preformed. In Live Mode, a transaction is generated and submitted to the processor with the amount of $0.01. If successful, the transaction is immediately voided.
For information about output parameters for this function, see the section of this document titled Output Parameters for ValidateCustomerPaymentProfileResponse.
30
Section 3 Responses
The response from the payment gateway to the API call is a set of fields that provides information about the status of the request. The following table lists output for API calls.
ELEMENT resultCode VALUE Contains additional information about the results of the request Contains the result code and text A code that represents the reason for the error A text description of the error TYPE/FORMAT MessageTypeEnum Ok Error MessagesTypeMessage String Messages provide more details about the error(s). See the Response Codes section of this document for possible values. See the Response Codes section of this document for possible values. NOTES
messages code
text
String
CIM Responses
The sample below illustrates the structure of a typical response from the payment gateway for any of the CIM API calls.
Sample Response <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Body> <CreateCustomerProfileResponse xmlns="https://api.authorize.net/soap/v1/"> <CreateCustomerProfileResult> <resultCode>Ok</resultCode> <messages> <code>I00001</code> <text>Successful</text> </messages> <customerProfileId>1259</customerProfileId> </CreateCustomerProfileResult> </CreateCustomerProfileResponse> </soap:Body> </soap:Envelope>
31
Section 3 Responses
Contains the CreateCustomerProfileResponse See the Response result of the API Type Codes section of request to this document for create a possible values. customer profile Payment gateway assigned ID associated with the customer profile Numeric This output is only present for successful requests.
customerProfileId
CreateCustomerPaymentProfileResult Contains the CreateCustomerPayme result of the API ntProfileResponseType request to create a customer payment profile customerPaymentProfileId Payment gateway assigned ID associated with the customer payment profile Contains detailed information about the result of the transaction. Numeric
validationDirectResponse
This output is only present if the ValidationMode See the Advanced input parameter is Integration Guide at http://www.authorize.ne passed with a value t/support/AIM_guide.pdf of testMode or for details about liveMode.. information included in the payment gateway transaction response. String
32
FIELD
VALUE
TYPE/FORMAT
NOTES See the Response Codes section of this document for possible values. This output is only present for successful requests.
CreateCustomerShippingAddressResult Contains the CreateCustomer result of the API ShippingAddress request to create ResponseType a customer shipping address customerAddressId Payment Numeric gateway assigned ID associated with the customer shipping address
CreateCustomerProfileTransactionResult Contains the CreateCustomerProfile See the result of the API TransactionResponse Response Codes request to Type section of this create a document for customer profile possible values. transaction directResponse Contains detailed information about the result of the transaction. String See the Advanced Integration Guide at http://www.authorize.n et/support/AIM_guide. pdf for details about information included in the payment gateway transaction response. Transactions created from a customer profile will behave the same as regular transactions - you and your customer will receive all associated email notifications. Additionally, all fraud settings, including FDS filters and AVS and CCV settings, will be enforced.
DeleteCustomerPr See the Response ofileResponseType Codes section of this document for possible values.
33
Section 3 Responses
DeleteCustomer See the Response PaymentProfileR Codes section of this esponseType document for possible values.
DeleteCustomer See the Response ShippingAddress Codes section of this document for possible ResponseType values.
Contains the GetCustomerProfile result of the ResponseType API request to get a customer profile Contains information for the customer profile Contains payment profiles for the customer profile Payment gateway assigned ID associated with the CustomerProfileMasked Type
profile
paymentProfiles
CustomerPaymentProfile MaskedType
customerPaymentProfileId
Numeric
34
FIELD
VALUE customer payment profile payment Contains payment profile information for the customer profile
TYPE/FORMAT
NOTES
PaymentMaskedType
creditCard
Contains credit CreditCardMaskedType card payment information for the customer profile The customers credit card number The expiration date for the customers credit card Contains bank account payment information for the customer profile The routing number of the customers bank The customers bank account number 13 to 16 digits All sensitive payment information in the output is masked. All sensitive payment information in the output is masked.
cardNumber
expirationDate
YYYY-MM
bankAccount
BankAccountMaskedType
routingNumber
9 digits
All sensitive payment information in the output is masked. All sensitive payment information in the output is masked.
accountNumber
5 to 17 digits
driversLicense
Contains the DriversLicenseMasked customers Type drivers license information The state of A valid two-character the customers state code drivers license The 5 to 20 characters customers drivers license number The date of YYYY-MM-DD birth listed on the customers drivers license All sensitive payment information in the output is masked. All sensitive payment information in the output is masked.
state
number
dateOfBirth
35
Section 3 Responses
FIELD taxId
VALUE
TYPE/FORMAT
The 9 digits customers Social Security Number or tax ID Contains CustomerAddressExType shipping address profile information for the customer profile Payment gateway assigned ID associated with the customer shipping address Numeric
shipToList
customerAddressId
paymentProfile
Contains payment CustomerPaymentProfile information for the MaskedType customer profile Payment gateway assigned ID associated with the customer payment profile Numeric
customerPaymentProfileId
customerType
billTo address firstName lastName The customers first name The customers last name
36
FIELD company
VALUE The name of the company associated with the customer, if applicable The customers address The city of the customers address The state of the customers address The ZIP code of the customers address
NOTES
address city
Up to 60 characters (no symbols) Up to 40 characters (no symbols) A valid two-character state code Up to 20 characters (no symbols)
state
zip
country
The country of the Up to 60 characters (no customers symbols) address The phone number associated with the customers address The fax number associated with the customers address Up to 25 digits (no letters) Ex. (123)123-1234
phoneNumber
faxNumber
payment
Contains payment PaymentMaskedType profile information for the customer profile Contains credit CreditCardMaskedType card payment information for the payment profile The customers credit card number The expiration date for the customers credit card 13 to 16 digits All sensitive payment information in the output is masked. All sensitive payment information in the output is masked.
creditCard
cardNumber
expirationDate
YYYY-MM
bankAccount
Contains bank BankAccountMaskedType account payment information for the payment profile The type of bank checking
accountType
37
Section 3 Responses
FIELD
NOTES
The customers Up to 22 characters full name as listed on the bank account The type of electronic check transaction CCD PPD TEL WEB Up to 50 characters Currently, the CIM API does not support ARC or BOC transaction types
echeckType
bankName
The name of the bank associated with the bank account number The routing number of the customers bank The customers bank account number Contains the customers drivers license information The state of the customers drivers license The customers drivers license number The date of birth listed on the customers drivers license The customers Social Security Number or tax ID
routingNumber
9 digits
All sensitive payment information in the output is masked. All sensitive payment information in the output is masked.
accountNumber
5 to 17 digits
driversLicense
DriversLicenseMasked Type
state
A valid two-character state code Between 5 and 20 characters All sensitive payment information in the output is masked. All sensitive payment information in the output is masked. All sensitive payment information in the output is masked.
number
dateOfBirth
YYYY-MM-DD
taxId
9 digits
38
GetCustomerShippingAddressResult
Contains the result of the API request to get a customer shipping address Contains shipping address information for the customer profile Payment gateway assigned ID associated with the customer shipping address
See the Response Codes section of this document for possible values.
address
customerAddressId
Numeric
UpdateCustomerProfileResult Contains the result of the API request to update a customer profile
UpdateCustomerProfile See the Response Codes section of this ResponseType document for possible values.
UpdateCustomer See the Response PaymentProfileRe Codes section of this document for sponseType possible values.
Contains the result UpdateCustomer of the API request ShippingAddress to update a ResponseType customer shipping address
39
Section 3 Responses
Contains the ValidateCustomer result of the API PaymentProfileRe request to sonseType validate a customer payment profile Contains detailed information about the result of the transaction. String See the Advanced Integration Guide at http://www.authori ze.net/support/AI M_guide.pdf for details about information included in the payment gateway transaction response.
directResponse
Response Codes
The following table lists the common response codes and texts for requests to the Customer Information Manager API.
CODE I00001 I00003 E00001 E00002 E00003 E00004 E00005 E00006 E00007 TEXT Successful The record has already been deleted. DESCRIPTION The request was processed successfully. The record has already been deleted.
An error occurred during processing. Please try An unexpected system error occurred while again. processing this request. The content-type specified is not supported. An error occurred while parsing the XML request. The name of the requested API method is invalid. The merchantAuthentication.transactionKey is invalid or not present. The merchantAuthentication.name is invalid or not present. User authentication failed due to invalid authentication values. The only supported content-types are text/xml and application/xml. This is the result of an XML parser error. The name of the root node of the XML request is the API method being called. It is not valid. Merchant authentication requires a valid value for transaction key. Merchant authentication requires a valid value for name. The name/and or transaction key is invalid.
40
E00008 E00009
The payment gateway account is in Test Mode. The requested API method cannot be executed The request cannot be processed. while the payment gateway account is in Test Mode. User authentication failed. You do not have the appropriate permissions. Access denied. You do not have the appropriate permissions. The field is invalid. A required field is not present. The field length is invalid. The field type is invalid. The customer taxId or driversLicense information is required. The user does not have permission to call the API. The user does not have permission to call the API method. One of the field values is not valid. One of the required fields was not present. One of the fields has an invalid length. The field type is not valid. The customer tax ID or drivers license information (drivers license number, drivers license state, drivers license DOB) is required for the subscription. An approval was not returned for the transaction. Payment information is required when creating a subscription or payment profile. A duplicate of the customer profile, customer payment profile, or customer address was already submitted. The profileID, paymentProfileId, or shippingAddressId for this request is not valid for this merchant. All of the fields were empty or missing. The maximum number of payment profiles for the customer profile has been reached. The maximum number of shipping addresses for the customer profile has been reached. The payment gateway account is not enabled for Customer Information Manager (CIM).
The transaction was unsuccessful. Payment information is required. A duplicate record already exists.
E00040
One or more fields must contain a value. The maximum number of payment profiles allowed for the customer profile is {0}. The maximum number of shipping addresses allowed for the customer profile is {0}. Customer Information Manager is not enabled.
41