Home > Integrating Verification Services into Your Business

Integrating Verification Services into Your Business

For request and reply examples, see Request and Reply Examples.

 

nWhen requesting these services, be sure to send only valid and well-formed data in all fields, especially in the credit card account number, billing address, email address, and IP address fields.

nTo use these services, you must collect the full address from your customers; Verification Services do not support relaxed requirements for address data.

nCybersource supports multi-byte characters for all services except Delivery Address Verification, Stored Value, and Customer Profiles. Before implementing any of these services, contact your Cybersource representative to clarify any questions you have about multi-byte character support.

Requesting Delivery Address Verification

To request the address verification service, set the davService_run field to true. When requesting davService, do not request the following services:

nAuthorization Reversal (ccAuthReversalService). For more information about this service, see Credit Card Services Using the Simple Order API (PDF | HTML).

nRisk Update (riskUpdateService). For more information about this service, see Decision Manager Developer Guide Using the Simple Order API (PDF | HTML).

To ignore the result of the address verification request so that the results do not prevent other services from functioning, use the businessRules_ignoreDAVResult request field. For descriptions of the request fields you can use, see API Fields.

Interpreting the Delivery Address Verification Reply

If Delivery Address Verification finds a match for the street address, it returns a corrected and standardized address. If you have used the businessRules_ignoreDAVResult request field, only a standardized address is returned. The standardized address is divided into separate fields for the street address, city, state, province, territory, and postal code. For descriptions of all the reply fields, see API Fields. For examples, see Request and Reply Examples.

Returned Reply Fields

The reply contains the standardized address in the reply fields that begin with
davReply_standardized.

If you do not use the businessRules_ignoreDAVResult request field but want to know whether the address is correct, use the davReply_reasonCode field to get the address verification result.

Address verification is returned in the davReply_addressType field if the address can be normalized. If the request contains both the shipping and billing addresses, the reply contains information about the shipping address only. To obtain the most comprehensive address verification information, Cybersource recommends that you send separate requests for the billing address and the shipping address.

Status and Error Codes

For each verified address, you receive a status or an error code. Status codes contain information about corrections or standardizations that are applied to the address. Error codes contain information that explains why an address cannot be verified. Status and error codes are returned in the following reply fields:

Table 3Status and Error Code API Reply Fields

Status Codes

Error Codes

davReply_usInfo

davReply_usErrorInfo

davReply_caInfo

davReply_caErrorInfo

davReply_intlInfo

davReply_intlErrorInfo

For a complete list of the status and error codes that can be returned in reply fields, see Status and Error Codes.

Example 2Status Code Example

Each digit in the status code means something. If you receive

davReply_usInfo=S80000 in the reply from Cybersource, each digit in the code is interpreted as follows:

Table 4Status Code Interpretation

Digit

Value

Interpretation

1st

S

Nothing truncated.

2nd

8

Assigned a different ZIP+4.

3rd

0

With primary name, directionals, and suffix, no significant difference between input and corrected data.

4th

0

With country number, CART (carrier-route number), DPBC (delivery point barcode), and unit designator, no significant difference between input and corrected data.

5th

0

No meaning is currently assigned to the 5th and 6th digits. They are reserved for future use.

6th

0

Example 3Error Code Example

All error codes start with the letter E and contain a 3-digit number, which indicates one specific type of error. You do not interpret each individual digit for error codes. For example, if you receive davReply_usErrorInfo=E101 in the reply from Cybersource, the city, state, or ZIP code is invalid or missing.

 

For international addresses, you might receive a successful reply (reasonCode=100) that contains an error code. You are responsible for determining the level of risk for such an address match. Review these addresses carefully before making a final decision on the order.

Information Codes

If you use the Advanced Fraud Screen scoring service in the same request, and the normalized address appears to be risky, a RISK-AVS information code is returned. This code means that the combined AVS (Address Verification Service) test result and the normalized billing address are risky. For example, a risky address may be one in which the AVS result indicates an exact match, but the normalized billing address is not deliverable. All information codes are listed in the “Information and Reply Codes” appendix of the Decision Manager Developer Guide Using the Simple Order API (PDF | HTML).