Task: Credit Validation

CreditValidation_2_0 performs credit card validation and address verification.

Note: The Merchant ID must be supplied in the <CCAddrData> field when in AG mode, after January 22, 2007.

Section 1: Short Answer

Transaction Name: 

CreditValidation_2_0

Can any other transaction(s) perform this same task?

CreditCardVerification_2_0 should be used for all credit card authorizations.

Can this task be performed in a sessionless environment?

Yes, this task can be used in a sessionless environment.

Are the request and response identical on both the Apollo and Galileo systems?

CreditValidation_2_0 is available on Apollo. Address verification is available on a contractual basis and access to this feature is controlled by the AAT. If address verification is not available for the client application, only the credit card number verification will take place when these transactions are invoked.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

Because this transaction is used to request an actual approval code from a credit card vendor, it requires that the request is sent with a Merchant ID in AG mode.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

There are no special limitations.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

The request validates either the address and credit card number (JVV), or the credit card number (JV).

Address Verification

For address verification (JVV), the street address must be 20 bytes and Zip code must be 9 bytes (Spaces or ‘.’ (dots) are included). If the data is less than 20 bytes, remaining bytes must be filled either with spaces or dots(.).

Transaction amount validation is not supported by the CRS. However, it is still a required field in the transaction.

Following is an example of the request in AG mode, where the Merchant ID is Mandatory:

<CreditValidation_2_0>
 <CCAddrVerifyMods>
  <Cmd>JVV</Cmd>
  <CCAddrData><![CDATA[VI/-nnnnnnnnnnnnnnnn/-6901 S HAVANA......./-80112..../-AA]]>
  </CCAddrData>
 </CCAddrVerifyMods>
</CreditValidation_2_0>

Number Verification

For credit card number verification (JV), the <CCData> field has the 2-digit vender code followed by the credit card number. For example, <CCData>DC1234567890123456/V1.00USD</CCData>

Prerequisite tasks:

The following is needed for Credit Validation:

• Credit Card Type

• Credit Card Number

• [Optional]    Transaction Amount*

• [Optional]    Address**

• [Optional]    ZIP Code

For task to be executed properly it is mandatory to give merchant ID in AG duty code.

Expected response:

Address Response

If the Credit Validation is successful for the address, the response will look like this:

<CreditValidation_2_0>

    <CCAddrVerify>

    </CCAddrVerify>

</CreditValidation_2_0>

Number Response

If the Credit Validation is successful, the response is not what you might expect. Though it seems odd, the response will look like the following XML example:

<CreditValidation_2_0>

        <CCNumVerify/>

</CreditValidation_2_0>

Addresses can be validated only for American Express, Discover, Master Card, and Visa.

CreditValidation_2_0 does not obtain credit card authorization or approval codes. These functions must be obtained externally as part of the fulfillment process.

Error and warning responses:

The following error messages may be received in the <CCAddrVerify> tag:

1 Address and zip code are both incorrect

2 Address is correct, zip code is incorrect

3 Zip code is correct, address is incorrect

4 Data not available

5 Address verification entry format incorrect

6 Credit card number incorrect

7 Address incorrect

8 Zip code incorrect

9 System error cannot process

The following error message may be received in the <CCNumVerify>

1 Credit card number incorrect

Follow-on requests:

No follow-on requests exist.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

CreditValidation_2_0_1

CreditValidation_2_0_2

CreditValidation_2_0_3