TitlePage CyberSource Verification Services · CyberSource Corporation HQ | P.O. Box 8999 | San...

Title Page

CyberSource Verification ServicesUsing the SCMP API

July 2020

CyberSource Corporation HQ | P.O. Box 8999 | San Francisco, CA 94128-8999 | Phone: 800-530-9095

CyberSource Contact InformationFor general information about our company, products, and services, go to http://www.cybersource.com.

For sales questions about any CyberSource Service, email [email protected] or call 650-432-7350 or 888-330-2300 (toll free in the United States).

For support information about any CyberSource Service, visit the Support Center at http://www.cybersource.com/support.

Copyright© 2020 CyberSource Corporation. All rights reserved. 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.

Restricted Rights LegendsFor 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.

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

http://www.cybersource.com

mailto:[email protected]

http://www.cybersource.com/support/

CO

NTE

NTS

Contents

Recent Revisions to This Document 6

About This Guide 7Audience and Purpose 7Scope 7Conventions 8

Note and Important Statements 8Text and Command Conventions 8

Related Documents 9Customer Support 9

Chapter 1 Introducing Verification Services 10Delivery Address Verification 10

Address Validation 11Address Standardization 12Countries Supported by Delivery Address Verification 12Status and Error Codes 12

Export Compliance 13

Chapter 2 Integrating Verification Services into Your Business 14Requesting Delivery Address Verification 14

Interpreting the Delivery Address Verification Reply 15Returned Reply Fields 15

Requesting Export Compliance 17Handling the Results of Denied Parties List Checks 17Excluding Export Compliance Results 18Configuring Denied Parties List Matches 19

Adjusting Name and Address Word Matching 20Defining Name and Address Matching Rules 20

Verification Services Using the SCMP API | July 2020 3

Contents

Chapter 3 Testing Verification Services 22Requirements for Testing 22Testing Export Compliance 23

Appendix A API Fields 26Formatting Restrictions 26Data Type Definitions 26Request-Level Fields 27Offer-Level Fields 33Reply Fields 35

Appendix B Reply Flags 40

Appendix C Status and Error Codes 41Status Codes: U.S. Addresses 41Status Codes: International Addresses 45Error Codes: U.S. Addresses 48Error Codes: International Addresses 49

Appendix D Request and Reply Examples 51Delivery Address Verification Examples 51

Request 51Reply 52

Export Compliance Examples 53Example of Declined Transaction 53

Request 53Reply 53

Name and Address Word Matching Example 54Name and Address Matching Rule Example 55

Appendix E Export Compliance Standard Codes 56Denied Parties List Check Codes 56Product Codes 58


Contents

Appendix F Country or Region and Territory Postal System Categories 59Category I-A 59Category I-B 60Category II 60Category III 61Category IV 62

Appendix G Restricted and Denied Parties List 68

Appendix H Address Type 73


REV

ISIO

NS

Recent Revisions to This Document

Release ChangesJuly 2020 Updated Appendix G, "Restricted and Denied Parties List" page 75. Fixed

some links in Preface and corrected 2 country abbreviations.

October 2019 This revision contains only editorial changes and no technical updates.

January 2018 Added information about the CyberSource APIs to the CyberSource web site. See the CyberSource API Versions page.

September 2017 Updated Export Compliance to include support for more government agency lists. See "Handling the Results of Denied Parties List Checks," page 17.

Revised the bill_state field description to clarify that the field is only required if the value is CA or US. See bill_state, page 27.

Added the export_sanctions_lists API request field. See export_sanctions_lists, page 30.

Added new international lists to the "Restricted and Denied Parties List," page 68.

August 2017 Added details for testing Export Compliance. See "Requirements for Testing," page 22.

Updated company_name, customer_firstname, and customer_lastname fields to clarify that first name and last name or company name fields must be submitted.

Updated Export Compliance samples. See "Request and Reply Examples," page 51.

April 2016 Added note that Verification Services do not support relaxed requirements for address data. See "Integrating Verification Services into Your Business," page 14.

Updated URL for testing. See "Requirements for Testing," page 22.

October 2014 Corrected the length of the API request field customer_account_id. Changed the number of characters from 50 to 100. See customer_account_id, page 28.

Corrected information about using addresses to trigger Denied Parties List matches with the Export Service. See "Export Compliance," page 13, and "Configuring Denied Parties List Matches," page 19.


https://www.cybersource.com/developers/integration_methods/api_versions/

ABO

UT

GU

IDE

About This Guide

Audience and PurposeThis guide is written for application developers who want to use the CyberSource SCMP API to integrate address verification or export compliance verification services into their order management system.

Implementing CyberSource Verification Services requires software development skills. You must write code that uses the API request and reply fields to integrate Verification Services into your existing order management system.

ScopeThis guide describes only the tasks and API fields you must use to integrate Verification Services into your order management system. It does not describe how to integrate other CyberSource services. For that information, see "Related Documents," page 9.


About This Guide

Conventions

Note and Important Statements

Text and Command Conventions

Note

A Note contains helpful suggestions or references to material not contained in this document.

Important

An Important statement contains information essential to successfully completing a task or learning a concept.

Conventions Usagebold Field and service names; for example:

Include the ics_applications field.

Items that you are instructed to act upon; for example:Click Save.

italic Filenames and pathnames. For example:Add the filter definition and mapping to your web.xml file.

Placeholder variables for which you supply particular values.

Screen text XML elements.

Code examples and samples.

Text that you enter in an API environment; for example:Set the davService_run field to true.


About This Guide

Related Documents Getting Started with CyberSource Advanced for the SCMP API describes how to get

started using the SCMP API. (PDF | HTML)

Decision Manager Using the SCMP API Developer Guide describes how to integrate Decision Manager, a fraud detection service, with your order management system. (PDF | HTML)

Credit Card Services Using the SCMP API describes how to integrate CyberSource payment processing services into your business. (PDF | HTML)

Business Center Reporting User Guide describes how to view and configure Business Center reports. (PDF | HTML)

The CyberSource API Versions page provides information about the CyberSource API versions.

Refer to the Support Center for complete CyberSource technical documentation:

http://www.cybersource.com/en-us/support/technical-documentation.html

Customer SupportFor support information about any CyberSource service, visit the Support Center:

http://www.cybersource.com/support


http://apps.cybersource.com/library/documentation/dev_guides/Getting_Started_SCMP/Getting_Started_SCMP_API.pdf

http://apps.cybersource.com/library/documentation/dev_guides/Getting_Started_SCMP/html/

http://apps.cybersource.com/library/documentation/dev_guides/DM_Dev_Guide_SCMP_API/DM_developer_guide_SCMP_API.pdf

https://apps.cybersource.com/library/documentation/dev_guides/reporting_and_reconciliation/Reporting_User.pdf

https://developer.cybersource.com/library/documentation/dev_guides/reporting_and_reconciliation/Reporting_User/html/

https://www.cybersource.com/developers/integration_methods/api_versions/

http://www.cybersource.com/support

http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/Credit_Cards_SCMP_API.pdf

http://apps.cybersource.com/library/documentation/dev_guides/DM_Dev_Guide_SCMP_API/html/

http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/

https://www.cybersource.com/en-us/support/technical-documentation.html

Verification Services Using the SCMP API | July 2020

HAP

TER

C

1
Introducing Verification Services
CyberSource Verification Services are part of a suite of services that include electronic payment and fraud management. Verification Services consist of two services:

Delivery Address Verification

Export Compliance

Delivery Address VerificationDelivery Address Verification verifies a customer’s delivery address during card-not-present transactions, and then it returns a result. The result contains an API-specific reply code and a status or error code that is specific to the results of address verification. Verification tests produce a valid address and an estimate of the risk associated with the address. As a result, your shipping and customer service costs caused by address errors can be reduced.

The verification process consists of validation and standardization of submitted addresses. After a customer provides address information to your system, you send the address in a request to CyberSource for verification.

When CyberSource Verification Services receives the address information in your request, the address is validated and standardized as described in the following sections.

Note

You are responsible for creating your order acceptance strategy. If you do not have the expertise, you are also responsible for seeking expert help outside of your company. CyberSource cannot make recommendations for your business.

10

Chapter 1 Introducing Verification Services

Address ValidationDuring validation, address information is corrected. For example, the following items are verified:

The street number must be valid for the street. The street name must be valid for the city.

The postal code must be valid for the city.

If the postal code in the submitted address is valid, it is used to determine the city and state or province.

Example 1 Customer-Submitted Address Information

A customer submits the following address information to your system while placing an order:

44 Fisher StreetMtn View, Florida94043

The address information submitted by the customer contains several errors that can be corrected by Verification Services as described in the following table:

Table 1 Address Validation

Submitted Information Problem Corrected Address44 Fisher Street Street number is invalid. 34 Fisher Street

Mtn View

The first word of the city name is abbreviated by using a non-standard abbreviation, so it is considered misspelled. Mountain View

Mtn View, Florida 94043The city and state do not match the postal code.

Mountain View, California 94043



Address StandardizationDuring standardization, address information is arranged in a consistent, preferred format by using common abbreviations. For example:

DEPT is used for department St for Street

SW for Southwest

After the address information submitted by the customer in Example 1 is validated, the address is standardized as follows:

Countries Supported by Delivery Address VerificationDelivery Address Verification uses data from postal service databases, updated monthly from over 200 countries and territories. See Appendix F, "Country or Region and Territory Postal System Categories," on page 59.

Status and Error CodesCyberSource returns information codes for each address when address verification is attempted. These codes can include an API-specific reply code and a status or error code that describe the degree of match or reasons for the failure to match. When you have integrated Verification Services into your business, your system interprets the reply codes according to your business rules. Address verification failure rates depend on the address location and the category of the country, region, or territory as listed in Appendix F, "Country or Region and Territory Postal System Categories," on page 59. An address that requires correction is not considered a failure.

Address verification returns one of these results:

Address requires no correction. You receive the appropriate success information code.

Address requires correction. You receive an API-specific reply code and a status code that describe the type of correction that is applied.

Table 2 Address Standardization

Submitted Information Problem Corrected Address34 Fisher StreetMountain View, California 94043

The street and state names are abbreviated using common abbreviations.

34 Fisher StMountain View, CA94043



Address cannot be verified. You receive an API-specific failure code and an error code that describe the type of failure.

For more information about API-specific reply flags, see "Reply Flags," page 40. For more information about address verification status and error codes, see "Status and Error Codes," page 41.

Export ComplianceExport Compliance enables you to comply with U.S. Export Administration Regulations, as well as internationally supported sanctions lists, which place restrictions on those with whom you can conduct business. The service verifies customer information and returns detailed information about declined orders.

Export Compliance checks customer information by comparing it to many lists that are maintained by government agencies to support export controls. If a customer’s first name and last name or company name appears on any of the lists, you receive information indicating that the transaction is declined. You also receive a description of how the names match a list entry. For more information, see "Restricted and Denied Parties List," page 68.

You can use Export Compliance to manage your international sales territories by listing the allowed and disallowed export countries in each offer. A first name and last name or company name can be matched more than once to a list when different spellings or aliases exist. Although only some of these matches appear in the Business Center, all matches appear in the API reply.

If you use Decision Manager, you can create custom rules based on information codes, name matches, and export programs. In addition, you can create profile selector rules based on a name and address match. For more information, see the Decision Manager User Guide (PDF | HTML).


http://apps.cybersource.com/library/documentation/dev_guides/Decision_Manager_UG/DMUsersGuide.pdf

http://apps.cybersource.com/library/documentation/dev_guides/Decision_Manager_UG/html/


HAP

TER

C

2
Integrating Verification Services into Your Business
For request and reply examples, see "Request and Reply Examples," page 51.

Requesting Delivery Address VerificationTo request the address verification service, use the ics_dav application. When requesting ics_dav, do not request the following services:

Authorization Reversal (ics_auth_reversal). For more information about this service, see Credit Card Services Using the SCMP API (PDF | HTML).

Risk Update (ics_risk_update). For more information about this service, see Decision Manager Developer Guide Using the SCMP 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 ignore_dav_result request field. For descriptions of the request fields you can use, see "API Fields," page 26.

Important

When 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.

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

CyberSource 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.

14




http://apps.cybersource.com/library/documentation/dev_guides/DM_Dev_Guide_SCMP_API/html

Chapter 2 Integrating Verification Services into Your Business

Interpreting the Delivery Address Verification ReplyIf Delivery Address Verification finds a match for the street address, it returns a corrected and standardized address. If you have used the ignore_dav_result 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," page 26. For examples, see "Request and Reply Examples," page 51.

Returned Reply FieldsIf you do not use the ignore_dav_result request field but want to know whether the address is correct, use the dav_rflag field to get the address verification result. This field returns DINVALIDADDRESS if a problem exists with the address.

Address verification is returned in the dav_address_type 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:

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

Table 3 Status and Error Code API Reply Fields

Status Codes Error Codesdav_us_info dav_us_error_info

dav_ca_info dav_ca_error_info

dav_intl_info dav_intl_error_info



Example 2 Status Code Example

Each digit in the status code means something. If you receivedav_us_info=S80000 in the reply from CyberSource, each digit in the code is interpreted as follows:

Example 3 Error 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 dav_us_error_info=E101 in the reply from CyberSource, the city, state, or ZIP code is invalid or missing.

Information Codes

If you use the Score 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 SCMP API (PDF | HTML).

Table 4 Status Code Interpretation

Digit Value Interpretation1st 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

Note

For international addresses, you might receive a successful reply (dav_rflag=SOK) 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.





Requesting Export ComplianceTo request Export Compliance, use the ics_export service. For a list of the fields to use when you request the service, see "Request and Reply Examples," page 51.

Do not request the following services at the same time that you request Export Compliance:

Authorization Reversal (ics_auth_reversal). For more information about this service, see Credit Card Services Using the SCMP API (PDF | HTML).

Risk Update (ics_risk_update). For more information about this service, see the Decision Manager Developer Guide Using the SCMP API (PDF | HTML).

To list the allowed and disallowed countries for each offer, use the offer-level fields export and no_export.

Handling the Results of Denied Parties List ChecksCountries with which U.S. trade is restricted are automatically checked during denied parties checks. You can also check other government agency lists as best fits your business needs. See the export_sanctions_lists request field and "Restricted and Denied Parties List," page 68 for further details.

If a customer’s name or address strongly correlates with an entry in a Denied Parties List (DPL), the following information is returned in the reply from CyberSource:

Reply flag DRESTRICTEDBecause you always receive this flag for blocked countries, all customers from these countries receive this reply flag.

A message indicating that the customer is in a DPL with the name of the country

Reply fields starting with the export_match prefix describe the denied parties check correlation in more detail. You can receive an unlimited number of matches to names, addresses, and programs within the lists.

Note

Export Compliance verifies the IP address in addition to verifying the country.

Note

The denied parties lists are watch lists that are maintained by government entities, such as the U.S. Treasury Department or the Australia Department of Foreign Affairs and Trade.







The following example shows a reply in which the order data matched two denied parties lists:

In the first list (match0), the order matched 3 sub lists: programs 1, 2, and 3.

In the second list (match1), the order matched 2 sub lists: programs 1 and 2.

Example 4 Denied Parties List Check Reply Example

If you use Decision Manager, your custom rules that use Export match program as the order element return all result values delimited with carets (^) in the export_MatchN_programN field. In the preceding example, the values are:

BXA_UNV^US_DEBARRED^BXA_ENT^SDNTK^JADE

The complete matched data is also available in the Case Details window.

Excluding Export Compliance ResultsYou can allow processing to continue regardless of the Export Compliance results by using the ignore_export_result request field. If you use this field, be sure to review all orders that fail Export Compliance.

When a transaction is declined by the DPL check or the export service, reply flag SOK is returned for the transaction. In addition, the export_info field is returned containing one or more information codes. Other services in the request are processed normally.

export_match0_list=Bureau Of Industry and Securityexport_match0_program1=BXA_UNVexport_match0_program2=US_DEBARREDexport_match0_program3=BXA_ENTexport_match1_list=Office of Foreign Assets Controlexport_match1_program1=SDNTKexport_match1_program2=JADE

Note

If you use Decision Manager, you can create custom rules and profile selector rules that use the information codes that you receive from Export Compliance. These rules enable you to route different types of orders to specific review queues in your order management system. If you subscribe to Enhanced Case Management and want to view the export information results in the Case Details window of the Business Center, you must use the ignore_export_result field.



Example 5 Request and Reply Example that Uses the ignore_export_result Field

The following request example shows the international data that is used by Export Compliance and the use of the ignore_export_result field:

The following reply shows that Export Compliance was processed successfully (ics_rflag=SOK). However, three information codes were returned for the shipping address, the host name, and the Denied Parties List check:

Configuring Denied Parties List MatchesBy default, Export Compliance searches for an exact match between a DPL and the information in the request. However, you can adjust the parameters that control what is required for a match by using the following order elements:

NameExport Compliance requires at least the name of the customer or the company name.

AddressYou can search by name and address. Provide as much information as possible to reduce the number of false positives returned in the results.

A false positive result occurs when a DPL contains information that is common to several individuals. For example, many people have the same first name, the same last name, or even the same first and last name. However, it is unlikely that individuals have the same

bill_address1=26 JALAN MT. ERSKINEbill_city=PENANGbill_country=MYcustomer_hostname=www.cybersource.irics_applications=ics_exportignore_export_result=yesship_to_address1=26 JALAN MT. ERSKINEship_to_city=PENANGship_to_country=be

export_info=MATCH-SCO^MATCH-HCO^MATCH-DPCexport_ip_country_confidence=99export_match1_address1=26 JALAN MT. ERSKINE,PENANG,,MY,export_match1_list=Bureau Of Industry and Securityexport_rcode=1export_rflag=SOKexport_rmsg=export service was successfulics_rcode=11ics_rflag=SOKics_rmsg=Request was processed successfully.



first name, last name, company name, and address, especially if all of the information is complete.

Adjusting Name and Address Word MatchingYou can specify how closely a customer’s name, company name, or address must match by using these optional request fields:

export_address_weight export_company_weight export_name_weight

These fields can be set to exact, high, medium, or low to indicate how much the value in the order can deviate from an entry in a DPL. For example, if you set export_name_weight to medium, and the customer’s name does not differ significantly from an entry in a DPL, ics_export detects a match. If you do not include these fields with your request, Export Compliance searches for an exact match only. For usage examples of these fields, see "Request and Reply Examples," page 51.

Defining Name and Address Matching Rules

Use the export_address_operator field to specify how Export Compliance detects name and address matches. You can set this request field to one of the following values:

AND (the default setting)

Export Compliance detects a match only if both the name and the address match an entry in a DPL. Name can be the customer’s name or the company name. Export Compliance evaluates all combinations available in the request:

Name and billing address Name and shipping address Company and billing address

Company and either shipping address, blocked billing, or blocked shipping country

Important

To accurately match customer and company names with entries on a DPL, you must send names in the correct API field (customer_firstname, customer_lastname, and company_name).

Important

Although this is the default setting for the export_address_operator field, you are responsible for ensuring that this setting provides accurate and appropriate results for your business.



However, if a request contains only a name, the AND setting matches the name with any address. Add all available address elements to receive the most accurate match and the fewest false positives. For more information about the behavior of this setting, see "Interactions between Match Weight and the AND Matching Rule."

ORExport Compliance detects a match if the customer’s first name, last name, or company name match an entry on a DPL. An address cannot trigger a DPL match on its own.

IGNOREExport Compliance detects a match based on only the customer’s name or the company name and ignores the address. However, the blocked countries check is still performed.

Interactions between Match Weight and the AND Matching Rule

When the export_address_operator field is set to AND, a combination of customer or company name and address is checked. All possible combinations are evaluated before the DPL check results are returned. The match weight level specified for the customer name or the company name (export_name_weight and export_company_weight) is used for all order elements in the request.

Therefore, if you set name and company to different weights, and send a request that contains a customer name, a company name, and an address, each pair of values is evaluated independently.

Example 6 Export Compliance Evaluation Example

A request includes the following:

First and last name with the name weight set to high (export_name_weight=high)

Company name with the company weight set to low (export_company_weight=low)

Export Compliance evaluates the request as follows:

A high weight is set on the combination of customer name and address. The customer name and address cannot differ significantly from an entry in a DPL to register a match.

A low weight is set on the combination of company name and address. The company name and address can differ significantly from an entry in a DPL to register a match.



HAP

TER

C

3
Testing Verification Services
To ensure that your requests are processed correctly, you must test the basic success and error conditions for each CyberSource service you plan to use.

Requirements for Testing Use your regular CyberSource merchant ID when you are testing your system.

To test a successful transaction, use valid name and address information.

To test a declined transaction, use invalid information, such as an invalid address for Delivery Address Verification or information with missing fields.

When testing the SCMP API, use the CyberSource test server:ics2testa.ic3.com.

If your system is configured correctly, you receive a reply with the expected reply fields and reply flags. See "Request-Level Fields," page 27 and "Reply Flags," page 40.

If your tests are successful, contact your CyberSource representative to activate your account so that you can send transactions to the CyberSource production server. To process customer transactions, you must change the status of your account from test to live production.

After you start processing transactions on the production server, you can configure CyberSource reports. For more information, see the Reporting Developer’s Guide (PDF | HTML).

22

http://apps.cybersource.com/library/documentation/dev_guides/Reporting_Developers_Guide/reporting_dg.pdf

http://apps.cybersource.com/library/documentation/dev_guides/Reporting_Developers_Guide/html

Chapter 3 Testing Verification Services

Testing Export ComplianceUse one of the following sets of request values to test your Export Compliance Service. Include first name and last name.

OR

customer_firstname Mohammed

customer_lastname QASIM

customer_firstname Maria

customer_lastname RODRIGUEZ



Table 5 provides possible reply values.

Table 5 Possible Reply Field Values for Export Compliance Service

Scenario Request Field Values ResponseMatching first/last name (case insensitive)

customer_firstname=Mohammed

customer_lastname=QASIM

export.reason_code=100

export_info=MATCH-DPC

export_ip_country_confidence=-1

export_match1_address1=Waish,Spin Boldak,null,

export_match1_address2=Bypass Road,Chaman,null,

export_match1_address3=Karez Qaran,Musa Qal'ah,Helmand Province,null,

export_match1_address4=Qalaye Haji Ali Akbar Dalbandin Post Office,,,null,

export_match1_address5=Room 33, 5th Floor Sarafi Market,Kandahar,,null,

export_match1_address6=Safaar Bazaar,Garmsir,,null,

export_match1_list=Office of Foreign Assets Control

export_match1_name1=Mohammed QASIM

export_match1_name2=aka, QASIM, Muhammad

export_match1_program1=SDGT

export_rcode=1

export_return_code=1140000

export_rflag=SOK

export_rmsg=export service was successful



Matching first/last name (case insensitive)

customer_firstname=Maria

customer_lastname=RODRIGUEZ

export.reason_code=100

export_info=MATCH-DPC

export_ip_country_confidence= -1

export_match1_list=Office of Foreign Assets Control

export_match1_name1=Maria de Jesus ESPINOZA RODRIGUEZ

export_match1_program1=SDNTK

export_rcode=1


export_rflag=SOK


Non-matching first/last name Use any value. export.reason_code=100

export_ip_country_confidence=-1

export_rcode=1


export_rflag=SOK


Table 5 Possible Reply Field Values for Export Compliance Service (Continued)

Scenario Request Field Values Response



PPEN

DIX

A

A
API Fields
This appendix describes the SCMP (Simple Commerce Message Protocol) API fields that you can use to access Verification Services. SCMP API is a legacy name-value pair API that is supported for merchants who have already implemented it. If you are new to CyberSource and want to connect to services, use the Simple Order API.

Formatting RestrictionsUnless otherwise noted, all fields are order and case insensitive, and they accept special characters such as @, #, and %.

Data Type Definitions

Note

Request-level and offer-level field names and values must not contain carets (^) or colons (:). However, they can contain embedded spaces and any other printable characters. If you use more than one consecutive space, the extra spaces are removed.

Table 6 Data Types

Data Type DescriptionDate and time The format is YYYY-MM-DDThhmmssZ. For example, 2012-08-

11T224757Z is equal to August 11, 2012, at 10:45:57 P.M. The T separates the date and the time. The Z indicates Coordinated Universal Time (UTC), which is also known as Greenwich Mean Time.

Decimal Number that includes a decimal point. Examples: 23.45, -0.1, 4.0, 90809.0468.

Integer Whole number {…, 03, 02, 01, 0, 1, 2, 3, …}.

Nonnegative integer

Whole number greater than or equal to zero {0, 1, 2, 3, …}.

Positive integer Whole number greater than zero {1, 2, 3, …}.

String Sequence of letters, numbers, spaces, and special characters, such as @ and #.

26

http://www.cybersource.com/developers/develop/integration_methods/simple_order_and_soap_toolkit_api/

Appendix A API Fields

Request-Level FieldsSee Getting Started with CyberSource Advanced for the SCMP API (PDF | HTML) for a description of how to work with this name-value pair API.

Table 7 Request-Level Fields

Field Description Used By: Required (R) or Optional (O)

Data Type & Length

bill_address1 First line of the billing address. ics_dav (R)

ics_export (R)

String (60)

bill_address2 Second line of the billing address. ics_dav (O)

ics_export (O)

String (60)

bill_address3 and bill_address4

Third and fourth line of the billing address. ics_dav (O) String (60)

bill_city City of the billing address. For ics_dav, if ship_city is not provided, bill_city is used in its place.

ics_dav (R)

ics_export (R)

String (50)

bill_country Country or region of the billing address. Use the two-character country or region codes (see "Country or Region and Territory Postal System Categories," page 59). For the ics_dav service, if the ship_to_country field is not provided, the bill_country field is used in its place.

ics_dav (R)

ics_export (R)

String (2)

bill_state State or province of the billing address. Use the two-character codes located in the Support Center. For the ics_dav service, if shipping address information is not provided, the bill_state field information is used in place of the ship_to_state field.

Required if the value of bill_state is CA or US.

ics_dav (O)

ics_export (O)

String (2)

bill_zip Postal code of the billing address. Make sure to send only valid and well-formed data. Required only if the bill_country field is US or CA:

US: numeric characters in either of these formats: five characters: NNNNN nine characters: NNNNN-NNNN

CA: six alphanumeric characters in this format:ANA NAN

ics_dav (R for U.S. and Canada)

String (10)




http://apps.cybersource.com/library/documentation/sbc/quickref/states_and_provinces.pdf



comments Brief description of the order or any comment you wish to add to the order.

ics_dav (O)

ics_export (O)

String

company_name Company name of person buying the product.

Important This field or customer_firstname and customer_lastname must be present. Otherwise, your request will fail.

ics_export String (60)

customer_account_id Optional customer’s account ID, tracking number, reward number, or other unique number that you assign to the customer for the purpose that you choose.

ics_dav (O)

ics_export (O)

String (100)

customer_email Customer’s email address, including the full domain name submitted in the form [email protected], such as [email protected].

ics_export (R) String (255)

customer_firstname Customer’s first name.

Important If you submit this field, you must also submit customer_lastname. Alternatively, you can submit company_name field instead of customer_firstname and customer_lastname. Otherwise, your request will fail.


customer_hostname DNS resolved host name from the customer_ipaddress field.

ics_export (O) String (40)

customer_ipaddress IP address of the customer, for example, 10.1.27.63.


customer_lastname Customer’s last name.

Important If you submit this field, you must also submit customer_firstname. Alternatively, you can submit company_name field instead of customer_firstname and customer_lastname. Otherwise, your request will fail.


Table 7 Request-Level Fields (Continued)


Data Type & Length



export_address_operator Parts of the customer’s information that must match with an entry in the DPL (denied parties list) before a match occurs. This field can contain one of the following values:

AND: (default) The customer’s name or company and the customer’s address must appear in the database.

OR: The customer’s name must appear in the database.

IGNORE: You want the service to detect a match only of the customer’s name or company but not of the address.


export_address_weight Degree of correlation between a customer’s address and an entry in the DPL before a match occurs. This field can contain one of the following values:

exact: The address must be identical to the entry in the DPL.

high: (default) The address cannot differ significantly from the entry in the DPL.

medium: The address can differ slightly more from the entry in the DPL.

low: The address can differ significantly from the entry in the DPL.


export_company_weight Degree of correlation between a company address and an entry in the DPL before a match occurs. This field can contain one of the following values:

exact: The company name must be identical to the entry in the DPL.

high: (default) The company name cannot differ significantly from the entry in the DPL.

medium: The company name can differ slightly more from the entry in the DPL.

low: The company name can differ significantly from the entry in the DPL.




Data Type & Length



export_name_weight Degree of correlation between a customer’s name and an entry in the DPL before a match occurs. This field can contain one of the following values:

exact: The name must be identical to the entry in the DPL.

high: (default) The name cannot differ significantly from the entry in the DPL.

medium: The name can differ slightly more from the entry in the DPL.

low: The name can differ significantly the entry in the DPL.


export_sanctions_lists Use this field to specify which list(s) you want checked with the request. The reply will include the list name as well as the response data.

To check against multiple lists, enter multiple list codes separated by a caret (^).

For more information, see "Restricted and Denied Parties List," page 68.


ics_applications ICS applications to process for the request.

At least one application must be specified in the request.

ics_dav (R)

ics_export (R)

String (255)

ignore_dav_result When requesting the ics_dav service with other applications, the ignore_dav_result field enables you to continue processing the request even if the ics_dav service cannot verify the address. This field can contain one of the following values:

yes: Ignore the results of address verification and continue to process the request.

no: (default) If the ics_dav service cannot verify the address, stop processing the request.

ics_dav (O) String (3)



Data Type & Length



ignore_export_result When requesting the ics_export service with other applications or if the denied parties list check is enabled for your merchant ID, the ignore_export_result field enables you to continue processing the request even if the order does not comply with export requirements. This field can contain one of the following values:

yes: Ignore the results of export compliance and continue to process the request. The reply will include information about any matches with denied parties lists.

no: (default) If the order does not pass export compliance, stop processing the request.


merchant_id Your CyberSource merchant ID. Use the same merchant ID for evaluation, testing, and production.

ics_dav (R)

ics_export (R)

String (30)

merchant_ref_number Merchant-generated order reference or tracking number.

ics_dav (R)

ics_export (R)

String (50)

offer0to

offerN

Offers (line items of the order) for the request. At a minimum, offer0 must be present.

ics_dav (O)

ics_export (O)

String (50)

ship_to_address1 First line of the shipping address. ics_dav (R) String (60)

ship_to_address2 to

ship_to_address4

Second to fourth line of the shipping address. ics_dav (O) String (60)

ship_to_city City of the shipping address. ics_dav (R) String (50)

ship_to_country Country or region of the shipping address. Use the two-character country or region codes (see "Country or Region and Territory Postal System Categories," page 59). For ics_export, bill_country is used if ship_to_country is not present.

ics_dav (R)

ics_export (O)

String (2)

ship_to_firstname First name of the recipient. ics_export (O) String (60)

ship_to_lastname Last name of the recipient. ics_export (O) String (60)



Data Type & Length



ship_to_state State or province of the shipping address. Use the State, Province, and Territory Codes for the United States and Canada.

The default value for the ship_to_state field is the value in the bill_state field. Required if the value of the ship_to_country field is CA or US.


ship_to_zip Postal code of the shipping address. Required if the value of the ship_to_country field is CA or US.


timeout Number of seconds the system waits before returning a time-out error. The default is 110.

ics_dav (O)

ics_export (O)

Positive integer (3)



Data Type & Length





Offer-Level FieldsVerification Services use the following offer-level fields. You must provide at least the amount field in your requests for Verification Services. For more information about using the offer-level fields, see “Using Offers or a Grand Total in a Request” in Getting Started with CyberSource Advanced for the SCMP API (PDF | HTML).

Table 8 Offer-Level Fields


Data Type & Length

amount Per-item price of the product. You can include a decimal point (.) but no other special character. The amount is truncated at the request level to the correct number of decimal places.

ics_dav (R)

ics_export (R)

Decimal (15)

export Comma-separated list of ISO country or region codes for countries to which the product can be exported. For a complete list, see "Country or Region and Territory Postal System Categories," page 59. If country or region codes are not specified, or if this field is not included, the U.S. government’s country or region code list is used.

Note The default list of countries restricted by the U.S. always applies. Any country or region not specifically added to the export field is considered restricted.

ics_export (O) String (no length limit)

merchant_product_sku Product’s identifier code. ics_dav (O)

ics_export (O)

String (30)

no_export Comma-separated list of ISO country or region codes for countries to which the product cannot be exported. For a complete list, see "Country or Region and Territory Postal System Categories," page 59.

Note If the export field is also present, the content of the no_export field overrides the content of export.

ics_export (O) String (no length limit)





product_code Type of product that the offer contains, which is also used to determine the category within which the product falls (electronic, handling, physical, service, or shipping).

Multiple product_code field values can apply to the same offer (for example, shipping and handling). The default value for the product_code field is default. For a complete list, see "Product Codes," page 58.

ics_dav (O)

ics_export (O)

String (30)

product_name Name of the product. ics_dav (O)

ics_export (O)

String (30)

quantity Quantity of the product being purchased. ics_dav (O)

ics_export (O)

Integer (non-negative) (10)

Table 8 Offer-Level Fields (Continued)


Data Type & Length



Reply FieldsTable 9 Reply Fields

Field Description Returned By Data Type & Length

client_lib_version Information about the client library used to request the transaction.

ics_dav

ics_export

String (255)

dav_address_type Contains the record type of the postal code with which the address was matched.

U.S. Addresses

Depending on the quantity and quality of the address information provided, this field contains one or two characters:

One character: sufficient correct information was provided to result in accurate matching.

Two characters: standardization would provide a better address if more or better input address information were available. The second character is D (default).

Blank fields are unassigned. When an address cannot be standardized, how the input data was parsed determines the address type. In this case, standardization may indicate a street, rural route, highway contract, general delivery, or PO box.For possible values, see Appendix H, "Address Type," on page 73.

All Other Countries

This field contains one of the following values:

P: Post.

S: Street.

x: Unknown.

ics_dav String (255)

dav_bar_code Delivery point bar code determined from the input address.


dav_bar_code_chkdigit Check digit for the 11-digit delivery point bar code.

ics_dav Non-negative integer (1)

dav_ca_error_info Four-character error code returned for Canadian addresses. For possible values, see "Error Codes: International Addresses," page 49.




dav_ca_info Four-to-ten character status code returned for Canadian addresses. For possible values, see "Error Codes: International Addresses," page 49.


dav_careof Care of data dropped from the standard address.


dav_intl_error_info Four-character error code returned for international addresses. For possible values, see "Error Codes: International Addresses," page 49.


dav_intl_info Four-to-ten character status code returned for international addresses. For possible values, see "Error Codes: International Addresses," page 49.


dav_match_score Indicates the probable correctness of the address match. Returned for U.S. and Canadian addresses. Returns a value from 0-9, where 0 is most likely to be correct and 9 is least likely to be correct, or -1 if there is no address match.

ics_dav Integer (1)

dav_rcode One-digit code that indicates whether the ics_dav request was successful. The field contains one of the following values:

-1: An error occurred.

0: The request was declined.

1: The request was successful.

ics_dav Integer (1)

dav_rflag One-word description of the result of the ics_dav request.


dav_rmsg Message that explains the reply flag dav_rflag. Do not display this message to your customer, and do not use this field to write an error handler.


dav_standard_address First line of the standardized address, including apartment information.


dav_standard_address_noapt

First line of the standardized address, without apartment information. Returned for U.S. and Canadian addresses.


dav_standard_address2 to

dav_standard_address4

Second to fourth line of the standardized address.


dav_standard_city Standardized city name. ics_dav String (255)

dav_standard_county U.S. county if available. ics_dav String (255)

Table 9 Reply Fields (Continued)




dav_standard_country Standardized country or region name. ics_dav String (255)

dav_standard_csz Standardized city, state or province, and ZIP + 4 code or postal code line.


dav_standard_iso_country Standardized two-character ISO country or region code.


dav_standard_state U.S.P.S. standardized state or province abbreviation.


dav_standard_zip Standardized U.S. ZIP + 4 postal code. ics_dav String (255)

dav_us_error_info Four-character error code returned for U.S. addresses; for possible values, see "Error Codes: U.S. Addresses," page 48.


dav_us_info Four-to-ten character status code returned for U.S. addresses; for possible values, see "Status Codes: U.S. Addresses," page 41.


export_ip_country_confidence

Likelihood that the country associated with the customer’s IP address was identified correctly. Returns a value from 1–100, where 100 indicates the highest likelihood. If the country cannot be determined, the value is –1.

ics_export Integer (3)

export_info Returned when the Denied Parties List check (first two codes) or the export service (all others) would have declined the transaction. Multiple information codes are separated by a caret (^). For more information, see "Excluding Export Compliance Results," page 18. This field can contain one or more of the following values:

MATCH-DPC: Denied Parties List match.

UNV-DPC: Denied Parties List unavailable.

MATCH-BCO: Billing country restricted.

MATCH-EMCO: Email country restricted.

MATCH-HCO: Host name country restricted.

MATCH-IPCO: IP country restricted.

MATCH-SCO: Shipping country restricted.


export_matchN_address1 to

export_matchN_addressN

Address found on the list specified in export_matchN_list for the entity (name and address) in the request.


export_matchN_list List on which the first Denied Parties List check match appears. For a list of codes, see "Denied Parties List Check Codes," page 56.






export_matchN_name1 to

export_matchN_nameN

Name found on the list specified in export_matchN_list for the entity (name and address) in the request.


export_matchN_programN Sub-lists matched by the order data. List members are separated by carets (^).


export_rcode One-digit code that indicates whether the ics_export request was successful. The field contains one of the following values:

-1: An error occurred

0: The request was declined

1: The request was successful

ics_export Integer (1)

export_rflag One-word description of the result of the ics_export request.


export_rmsg Message that explains the reply flag export_rflag. Do not display this message to your customer, and do not use this field to write an error handler.


ics_rcode One-digit code that indicates whether the entire request was successful. The field contains one of the following values:

-1: An error occurred

0: The request was declined

1: The request was successful

ics_dav

ics_export

Integer (1)

ics_rflag One-word description of the result of the entire request.

ics_dav

ics_export

String (255)

ics_rmsg Message that explains the reply flag ics_rflag. Do not display this message to your customer, and do not use this field to write an error handler.

ics_dav

ics_export

String (255)

merchant_ref_number Merchant-generated order reference or tracking number. For more information, see "Integrating Verification Services into Your Business," page 14.

ics_dav

ics_export

String (255)

request_id Identifier for the request generated by the client.

ics_dav

ics_export

String (255)





request_token Identifier for the request generated by CyberSource.

Request token data created by CyberSource for each reply. The field is an encoded string that contains no confidential information such as an account or card verification number. The string can contain a maximum of 256 characters.

ics_dav

ics_export

String (256)





PPEN

DIX

A

B
Reply Flags
Reply flags are associated with a request or a service. The flag in the ics_rflag field is associated with a request. The flag in the <service>_rflag field is associated with a service.

Table 10 Reply Flags

Reply Flag Description ServicesThat Can Return This Flag

DINVALIDADDRESS The customer entered an invalid city, state, country or region, or postal code, or the character set used for the transaction is not supported by the address verification service.

ics_dav

DINVALIDDATA The data provided is inconsistent with the request, such as a product with negative cost.

ics_export

DMISSINGFIELD The request is missing a required field. ics_dav

ics_export

DRESTRICTED One or more of these problems occurred:

The customer is on a government agency list containing entities with whom trade is restricted.

A government agency maintains an economic embargo against the country or region indicated in the billing or shipping address.

The customer’s shipping country or region is not on the export list that you submitted for the offers in the order.

ics_export

ESYSTEM System error. For details about the failure, see the contents of the ics_rmsg field. Wait several minutes before resending your request.

ics_dav

ics_export

ETIMEOUT The request timed out. ics_dav

ics_export

SOK The transaction was successful. ics_dav

ics_export

40


PPEN

DIX

A

C
Status and Error Codes
This appendix describes the status and error codes that are returned in API reply fields for U.S. and international addresses. Status codes contain information about corrections or standardizations that are applied to an address. Error codes contain information that explains why an address cannot be verified. Status and error codes are returned in the following reply fields:

Status Codes: U.S. Addresses

Table 11 Status and Error Code API Reply Fields

Status Codes Error Codesdav_us_info dav_us_error_info

dav_ca_info dav_ca_error_info

dav_intl_info dav_intl_error_info

Table 12 Status Codes Returned for U.S. Addresses

Ordinal Digit Value Description

1st

A Address line is truncated to make it fit into the field.

B Both the address line and the city name are truncated.

C City name is truncated to make it fit into the field.

S Nothing is truncated.

41

Appendix C Status and Error Codes

2nd

0 No significant difference between input and corrected data for city, state, ZIP, and ZIP+4.

1 Corrected the ZIP.

2 Corrected the city.

3 Corrected the city and ZIP.

4 Corrected the state.

5 Corrected the state and ZIP.

6 Corrected the city and state.

7 Corrected the city, state, and ZIP.

8 Corrected the ZIP+4.

9 Corrected the ZIP and ZIP+4.

A Corrected the city and ZIP+4.

B Corrected the city, ZIP, and ZIP+4.

C Corrected the state and ZIP+4.

D Corrected the state, ZIP, and ZIP+4.

E Corrected the city, state, and ZIP+4.

F Corrected the city, state, ZIP, and ZIP+4.

Table 12 Status Codes Returned for U.S. Addresses (Continued)




3rd

0 No significant difference between input and corrected data for primary street name, directional prefix (predirectional), directional suffix (postdirectional), and street-type suffix.

1 Corrected the street-type suffix.

2 Corrected the predirectional.

3 Corrected the predirectional and street-type suffix.

4 Corrected the postdirectional.

5 Corrected the street-type suffix and postdirectional.

6 Corrected the predirectional and postdirectional.

7 Corrected the predirectional, street-type suffix, and postdirectional.

8 Corrected the primary street name.

9 Corrected the primary street name and street-type suffix.

A Corrected the predirectional and primary street name.

B Corrected the predirectional, primary street name, and street-type suffix.

C Corrected the primary street name and postdirectional.

D Corrected the primary street name, street-type suffix, and postdirectional.

E Corrected the predirectional, primary street name, and postdirectional.

F Corrected the predirectional, primary street name, postdirectional, and street-type suffix.





4th

0 No significant difference between input and corrected data for county number, CART (carrier-route number), DPBC (delivery point barcode), and unit designator.

1 Corrected the unit designator.

2 Corrected the DPBC.

3 Corrected the DPBC and unit designator.

4 Corrected the CART.

5 Corrected the CART and unit designator.

6 Corrected the CART and DPBC.

7 Corrected the CART, DPBC, and unit designator.

8 Corrected the county number.

9 Corrected the county number and unit designator.

A Corrected the county number and DPBC.

B Corrected the county number, DPBC, and unit designator.

C Corrected the county number and CART.

D Corrected the county number, CART, and unit designator.

E Corrected the county number, CART, DPBC.

F Corrected the county number, CART, DPBC, and unit designator.

5th Reserved for future use.

6th Reserved for future use.





Status Codes: International AddressesTable 13 Status Codes Returned for International Addresses

Ordinal Digit Value Description1st S Status

2nd

0 No significant difference between input and corrected data for country, postal code, region, and locality.

1 Corrected the country.

2 Corrected the postal code.

3 Corrected the country and postal code.

4 Corrected the region.

5 Corrected the country and region.

6 Corrected the postal code and region.

7 Corrected the country, postal code, and region.

8 Corrected the locality.

9 Corrected the country and locality.

A Corrected the postal code and locality.

B Corrected the country, postal code, and locality.

C Corrected the region and locality.

D Corrected the country, region, and locality.

E Corrected the postal code, region, and locality.

F Corrected the country, postal code, region, and locality.



3rd

0 No significant difference between input and corrected data for directional prefix (predirectional), directional suffix (postdirectional), primary street type, primary street name, and primary range.

1 Corrected the predirectional and postdirectional.

2 Corrected the street type.

3 Corrected the predirectional, postdirectional, and primary street type.

4 Corrected the primary street name.

5 Corrected the predirectional, postdirectional, and primary street name.

6 Corrected the primary street type and primary street name.

7 Corrected the predirectional, postdirectional, primary street type, and primary street name.

8 Corrected the primary range.

9 Corrected the predirectional, postdirectional, and primary range.

A Corrected the primary street type and primary range.

B Corrected the predirectional, postdirectional, primary street type, and primary range.

C Corrected the primary street name and primary range.

D Corrected the predirectional, postdirectional, primary street name, and primary range.

E Corrected the primary street type, primary street name, and primary range.

F Corrected the predirectional, postdirectional, primary street type, primary street name, and primary range.

Table 13 Status Codes Returned for International Addresses (Continued)




4th

0 No significant difference between input and corrected data for unit description, unit number, building name, and firm name.

1 Corrected the unit description.

2 Corrected the unit number.

3 Corrected the unit description and unit number.

4 Corrected the building name.

5 Corrected the unit description and building name.

6 Corrected the unit number and building name.

7 Corrected the unit description, unit number, and building name.

8 Corrected the firm.

9 Corrected the unit description and firm.

A Corrected the unit number and firm.

B Corrected the unit description, unit number, and firm.

C Corrected the building name and firm.

D Corrected the unit description, building name, and firm.

E Corrected the unit number, building name, and firm.

F Corrected the unit description, unit number, building name, and firm.

5th

0 No significant difference between input and corrected data for other components that are not considered basic address components.

1 Corrected other primary address components.

2 Corrected other secondary address components.

3 Corrected other primary and secondary address components.

6th

A Europe, Middle East, and Africa (EMEA) engine: archived record used for assignment.

B Global address engine (New Zealand): base record assignment.

I Global address engine (New Zealand): record ignored.

L Global address engine (Brazil): Large Volume Receiver (LVR).

U Global Address Cleanse (New Zealand): unique address.

Table 13 Status Codes Returned for International Addresses (Continued)




Error Codes: U.S. AddressesTable 14 Error Codes Returned for U.S. Addresses

Code DescriptionE101 City, state, or ZIP code is incorrect or missing.

E212 No city and incorrect ZIP code.

E213 Incorrect city, valid state or province, and no ZIP code.

E214 Incorrect city and ZIP code.

E216 Incorrect ZIP code. Cannot determine city.

E302 No primary address line parsed.

E412 Street name not found in directory.

E413 Possible street-name matches too closely to select one.

E420 Primary range is missing.

E421 Primary range is invalid for the street, route, or building.

E422 Predirectional is needed. Input is wrong or missing.

E423 Street-type suffix is needed. Input is wrong or missing.

E425 Street-type suffix, predirectional, or postdirectional is needed. Input is wrong or missing.

E427 Postdirectional is needed. Input is wrong or missing.

E428 Incorrect ZIP code. Cannot match address.

E429 Incorrect city. Cannot match address.

E430 Possible address-line matches too closely to select one.

E431 Urbanization needed. Input is wrong or missing.

E439 Exact match made in EWS (Early Warning System) directory of the USPS.

E500 Other error.

E501 Foreign address.

E502 Input record blank.

E503 ZIP code is not in the area covered by the partial ZIP+4 directory.

E504 Overlapping ranges in the ZIP+4 directory.

E505 Address is not in the USPS directories. Undeliverable address.

E600 Marked by the USPS as unsuitable for mail delivery.

E601 Primary address number not in DPV (Delivery Point Validation) database of the USPS, and ZIP+4 was removed.



Error Codes: International AddressesTable 15 Error Codes Returned for International Addresses

Code DescriptionInput Record Discrepancies

1020 Address validated in multiple countries.

1030 Country code invalid or absent from the request.

1040 At least one address character not in supported character set.

1060 Country is not supported.

Inconsistent Last Line Information

2000 Unable to identify the locality, state, or postal code.

2010 Unable to identify the locality. Invalid postal code.

2020 Unable to identify the postal code. Invalid locality that prevents possible address correction.

2030 Invalid locality and postal code that prevents possible address correction.

2040 Invalid postal code that prevents locality selection.

2050 Last line matches too closely to select one. Last line of address, which depends on the country’s address format, is incorrect. For example, in the U.S., last lines of an address should contain city, state, and postal code.

Inconsistent Address Information

3000 Unable to identify the primary address line. Valid locality, region, and postal code.

3010 Unable to match primary name to the directory. Valid locality, region, and postal code.

3020 Possible primary name matches too closely to select one.

3030 Valid primary street name but missing range.

3040 Valid primary street name but invalid range.

3050 Invalid or missing primary street type that prevents a possible address match.

3060 Missing primary street type and directional information that prevents possible address match.

3070 Invalid or missing directional information that prevents possible address match.

3080 Invalid or missing postal code that prevents possible address match.

3090 Invalid locality that prevents possible address match.

3100 Possible address line matches too closely to select one.

3110 Address conflicts with postal code. The same primary street name has a different postal code.

Address with Low Likelihood of Delivery

4000 Invalid or missing secondary address that prevents a possible secondary address line match. Locality, region, postal code, and primary address are valid.

4010 Possible secondary address matches too closely to select one.



All Other Types of Information

5000 Valid address, but address is classified undeliverable by a postal authority.

5010 Address is not in specified country.

5020 Blank input record.

6000 Unclassified error.

Table 15 Error Codes Returned for International Addresses (Continued)

Code Description



PPEN

DIX

A

D
Request and Reply Examples
Delivery Address Verification ExamplesThe service requested is ics_dav.

Request

bill_address1=1295 charlestonbill_city=Mountain Viewbill_country=usbill_state=cabill_zip=94043ics_applications=ics_davmerchant_id=examplemerchant_ref_number=371CFDA219BD6992C2B044E89

51

Appendix D Request and Reply Examples

Reply

bill_address1=1295 charlestonbill_city=Mountain Viewbill_country=usbill_state=cabill_zip=94043client_lib_version=Perl3.2/MSWin324.0/NT4.0/3_3_0_0dav_address_type=Sdav_bar_code=130795dav_bar_code_chkdigit=5dav_match_score=2dav_rcode=1dav_rflag=SOKdav_rmsg=dav service was successfuldav_standard_address=1295 Charleston Rddav_standard_address_noapt=1295 Charleston Rddav_standard_city=Mountain Viewdav_standard_county=Santa Claradav_standard_country=USdav_standard_csz=Mountain View CA 94043-1307dav_standard_iso_country=USdav_standard_state=CAdav_standard_zip=94043dav_us_info=S80000ics_applications=ics_davics_rcode=1ics_rflag=SOKics_rmsg=Request was processed successfully.request_id=0183045530000167905080merchant_ref_number=371CFDA219BD6992C2B044E89Ics_Dav transaction succeededIcs_Dav : DavUSAddr : 506 Hazelwood Dr|us|ics_rflag=SOK - PASS



Export Compliance Examples

Example of Declined Transaction

Request

Reply

bill_address1=1234 First St.bill_city=Mountain Viewbill_country=USbill_state=CAbill_zip=94043customer_email=maria@example.comcustomer_firstname=Mariacustomer_ipaddress=127.0.0.1customer_lastname=Rodriguezcustomer_phone=650-965-6000ics_applications=ics_exportmerchant_id=examplemerchant_ref_number=391619C45442FD3F484013561offer0=amount:20.00

export.reason_code=100export_info=MATCH-DPCexport_ip_country_confidence=-1export_match1_list=Office of Foreign Assets Controlexport_match1_name1=Maria de Jesus ESPINOZA RODRIGUEZexport_match1_program1=SDNTKexport_rcode=1export_return_code=1140000export_rflag=SOKexport_rmsg=export service was successfulics_decision_reason_code=481ics_rcode=0ics_return_code=1000000ics_rflag=DREJECTics_rmsg=Decision is REJECT.merchant_ref_number=391619C45442FD3F484013561request_id=0183045530000167905080



Name and Address Word Matching ExampleThe following request example specifies that for a match to occur:

The address must be very near an entry on a DPL (Denied Parties List).export_address_weight is set to high.

The customer name or company name can differ slightly more.export_name_weight and export_company_weight are set to medium.

For more information about adjusting how names and addresses are matched with DPLs, see "Adjusting Name and Address Word Matching," page 20.

bill_address1=1295 Charleston Rd.bill_city=Mountain Viewbill_country=USbill_state=CAbill_zip=94043customer_email=jdoe@example.comcustomer_firstname=Johncustomer_ipaddress=127.0.0.1customer_lastname=Doecustomer_phone=650-965-6000export_address_weight=highexport_name_weight=mediumexport_company_weight=mediumics_applications=ics_exportmerchant_id=examplemerchant_ref_number=391619C45442FD3F484013561offer0=amount:20.00



Name and Address Matching Rule ExampleThe following request example specifies that for a match to occur, the DPL must include the customer’s name or the company name and the address by using export_address_operator=AND in the request.

For more information about adjusting the rules for matching names and addresses with DPLs, see "Defining Name and Address Matching Rules," page 20.

bill_address1=1295 Charleston Rd.bill_city=Mountain Viewbill_country=USbill_state=CAbill_zip=94043customer_email=jdoe@example.comcustomer_firstname=Johncustomer_ipaddress=127.0.0.1customer_lastname=Doecustomer_phone=650-965-6000export_address_operator=ANDics_applications=ics_exportmerchant_id=examplemerchant_ref_number=5255F145DD42A52E7BD745F14offer0=amount:20.00



PPEN

DIX

A

E
Export Compliance Standard Codes
Export Compliance returns the following codes.

Denied Parties List Check CodesThe following table contains result codes that are returned for Denied Parties List (DPL) checks. Each code represents one of the denied parties lists that are checked by Export Compliance. These codes are returned in the export_matchN_list reply field. When these codes are returned, Export Compliance has detected a match between order data and an entry in the Denied Parties List represented by the code.

Table 16 Denied Parties List Check Codes

Code Description

GOV-US-DBR Debarred Parties List

GOV-US-DPL Denied Party List, Bureau of Export Administration

GOV-US-ENT Entity List, Bureau of Export Administration

GOV-US-SDN-BAKN Balkans List - Specially Designated Nationals List

GOV-US-SDN-BPI-PA Blocked Pending Investigation - Patriot Act, Specially Designated Nationals List

GOV-US-SDN-CU Cuba List - Specially Designated Nationals List

GOV-US-SDN-FTO Foreign Terrorist Organization, Specially Designated Global Terrorist - Specially Designated Nationals List

GOV-US-SDN-IQ Iraq List - Specially Designated Nationals List

GOV-US-SDN-IR Iran List - Specially Designated Nationals List

GOV-US-SDN-KP North Korea List - Specially Designated Nationals List

GOV-US-SDN-LY Libya List - Specially Designated Nationals List

GOV-US-SDN-SD Sudan List - Specially Designated Nationals List

GOV-US-SDN-SDFT Specially Designated Terrorist, Foreign Terrorist Organization, Terrorism List Government Sanctions - Specially Designated Nationals List

GOV-US-SDN-SDGT Specially Designated Global Terrorist - Specially Designated Nationals List

56

Appendix E Export Compliance Standard Codes

GOV-US-SDN-SDNT Specially Designated Narcotic Trafficker - Specially Designated Nationals List

GOV-US-SDN-SDNTK Specially Designated Narcotic Trafficker (Kingpin Act) - Specially Designated Nationals List

GOV-US-SDN-SDT Specially Designated Terrorist - Specially Designated Nationals List

GOV-US-SDN-SDTG Specially Designated Terrorist, Terrorism List Government Sanctions Regulations - Specially Designated Nationals List

GOV-US-SDN-TABN Taliban List - Specially Designated Nationals List

GOV-US-SDN-UNITA National Union for the Total Independence of Angola & The Armed Forces for the Liberation of Angola - Specially Designated Nationals List

GOV-US-SDN-YU Federal Republic of Yugoslavia (Milosevic) - Specially Designated Nationals List

GOV-US-SPS-EMB Embargo List - U.S. Dept. of Commerce, Bureau of Export Administration and Office of Foreign Assets

Table 16 Denied Parties List Check Codes (Continued)

Code Description


Appendix E Export Compliance Standard Codes

Product CodesThe following table lists the values that you can use with the product_code offer field in your requests.

Table 17 Product Codes

Code Description

adult_content Adult content.

coupon Coupon applied to the entire order.

default Default value for the product code. CyberSource uses default when a request provides no value for the product code.

electronic_good Electronic product other than software.

electronic_software Software distributed electronically rather than on tapes, disks, or other media.

gift_certificate Gift certificate not issued with CyberSource Stored Value Services.

handling_only Separate charge that is generally a fee imposed by the seller on the customer. The fee pays for the seller’s administrative selling costs.

service Service that you perform for the customer.

shipping_and_handling Shipping is a separate charge for shipping the product to the purchaser. Handling is generally a fee imposed by the seller to pay for administrative selling costs.

shipping_only Charge for transporting tangible personal property from the seller to the purchaser. Documentation must be maintained that clearly establishes where title to the tangible personal property passed from the seller to the purchaser.

stored_value Stored Value certificate.

subscription Subscription to a web site or other content.



PPEN

DIX

A

F
Country or Region and Territory Postal System Categories
This appendix groups countries, regions, and territories according to the similarity of their postal systems. Delivery Address Verification uses the databases maintained by these postal systems to verify order address information.

Category I-AThese countries or regions have rigorous testing and a postal certification process that results in the largest amount and greatest accuracy of postal data.

Important

This note applies to categories II, III, and IV. If Delivery Address Verification cannot verify an address completely, or if the address cannot be matched with a postal database entry, you do not receive a successful reply. If the address is listed in a postal database, the service validates the accuracy of the address provided by the customer. When evaluating the reply of the service, make sure that you consider the error and status codes that also may be present in the reply. See "Status and Error Codes," page 41.

Table 18 Category I-A Country or Region and Territory Postal Systems

Country or Region CodeAustralia AU

Canada CA

United StatesIncludes: American Samoa [AS] Federated States of Micronesia [FM] Guam [GU] Marshall Islands [MH] Northern Mariana Islands [MP] Palau [PW] Puerto Rico [PR] Virgin Islands [VI]

US

59

Appendix F Country or Region and Territory Postal System Categories

Category I-BThese countries or regions provide complete address data, including all street names and all valid address ranges for the buildings on the streets. Although the postal systems of these countries lack the rigor of the Category I-A postal systems, these countries generally provide reasonably accurate and almost complete postal information.

Category IIThese countries or regions have fairly reliable postal systems and provide street names, city names, and postal codes for large and small cities. However, they provide incomplete ranges for the addresses of buildings. Therefore, you can often trust the validation results for the street name, city name, and postal code, but you cannot trust the validation of building addresses.

Table 19 Category I-B Country or Region and Territory Postal Systems

Country or Region CodeNetherlands NL

United KingdomIncludes: Ireland [IE]

GB

Table 20 Category II Country or Region and Territory Postal Systems

Country or Region CodeDenmark

Includes: Faroe Islands [FO]

DK

FranceIncludes: French Guiana [GF] Guadeloupe [GP] Martinique [MQ] Reunion [RE] Mayotte [YT] Monaco [MC] Saint Pierre and Miquelon [PM] French Polynesia [PF] New Caledonia [NC] Wallis and Futuna [WF]

FR

Germany DE



Category IIIThe postal systems in these countries provide street names, city names, and postal codes for large cities only and incomplete or no information for smaller cities. These postal systems may also provide an extremely limited set of building address ranges. Therefore, you can trust the validation results for city name, street name, and postal code for larger cities. For smaller cities, you can trust validation results for city name and postal code.

SwitzerlandIncludes: Liechtenstein [LI]

CH

Table 21 Category III Country or Region and Territory Postal Systems

Country or Region CodeAustria AT

Belgium BE

Finland FI

ItalyIncludes: Vatican City [VA] San Marino [SM]

IT

Luxembourg LU

New Zealand NZ

Norway NO

Poland PL

Portugal PT

South Africa ZA

Spain ES

Sweden SE

Table 20 Category II Country or Region and Territory Postal Systems (Continued)

Country or Region Code



Category IVIn these countries or regions, the postal systems are highly variable. Most countries or regions provide a list of cities and postal codes. However, all cities and postal codes might not be present in the country’s or region’s postal database.

Table 22 Category IV Country or Region and Territory Postal Systems

Country or Region CodeAfghanistan AF

Albania AL

Algeria DZ

Andorra AD

Angola AO

Anguilla (UK) AI

Antigua and Barbuda AG

Argentina AR

Armenia AM

Aruba AW

Azerbaijan AZ

Bahamas BS

Bahrain BH

Bangladesh BD

Barbados BB

Belarus BY

Belize BZ

Benin BJ

Bermuda (UK) BM

Bhutan BT

Bolivia BO

Bosnia and Herzegovina BA

Botswana BW

Brazil BR

British Virgin Islands (UK) VG

Brunei BN

Bulgaria BG

Burkina Faso BF

Burundi BI

Cambodia KH



Cameroon CM

Cape Verde CV

Cayman Islands (UK) KY

Central African Republic CF

Chad TD

Chile CL

China CN

Christmas Island (AU) CX

Cocos (Keeling) Islands (AU) CC

Columbia CO

Comoros KM

Congo, Democratic Republic of the CD

Congo CG

Cook Islands (NZ) CK

Costa Rica CR

Côte d’Ivoire CI

Croatia HR

Cuba CU

Cyprus CY

Czech Republic CZ

Djibouti DJ

Dominica DM

Dominican Republic DO

Ecuador EC

Egypt EG

El Salvador SV

Equatorial Guinea GQ

Eritrea ER

Estonia EE

Ethiopia ET

Falkland Islands (UK) FK

Fiji FJ

Gabon GA

Gambia GM

Georgia GE





Ghana GH

Gibraltar (UK) GI

Greece GR

Greenland (DK) GL

Grenada GD

Guatemala GT

Guinea GN

Guinea-Bissau GW

Guyana GY

Haiti HT

Honduras HN

Hong Kong HK

Hungary HU

Iceland IS

India IN

Indonesia ID

Iran IR

Iraq IQ

Israel IL

Jamaica JM

Japan JP

Jordan JO

Kazakhstan KZ

Kenya KE

Kiribati KI

Korea, Democratic People’s Republic (North) KP

Korea, Republic of (South) KR

Kosovo KV

Kuwait KW

Kyrgyzstan KG

Laos LA

Latvia LV

Lebanon LB

Lesotho LS

Liberia LR





Lithuania LT

Libya LY

Macau MO

Macedonia MK

Madagascar MG

Malawi MW

Malaysia MY

Maldives MV

Mali ML

Malta MT

Mauritania MR

Mauritius MU

Mexico MX

Moldova MD

Mongolia MN

Montenegro ME

Montserrat (UK) MS

Morocco MA

Mozambique MZ

Myanmar MM

Namibia NA

Nauru NR

Nepal NP

Netherlands Antilles (NL) AN

Nicaragua NI

Niger NE

Nigeria NG

Niue NU

Norfolk Island (AU) NF

Oman OM

Pakistan PK

Panama PA

Papua New Guinea PG

Paraguay PY

Peru PE





Philippines PH

Pitcairn Islands (UK) PN

Qatar QA

Romania RO

Russia RU

Rwanda RW

Saint Helena (UK) SH

Saint Kitts and Nevis KN

Saint Lucia LC

Saint Vincent and the Grenadines VC

Samoa WS

Sao Tome and Principe ST

Saudi Arabia SA

Senegal SN

Serbia RS

Seychelles SC

Sierra Leone SL

Singapore SG

Slovakia SK

Slovenia SI

Solomon Islands SB

Somalia SO

South Georgia and the South Sandwich Islands (UK) GS

Sri Lanka LK

Sudan SD

Suriname SR

Swaziland SZ

Syria SY

Taiwan TW

Tajikistan TJ

Tanzania TZ

Thailand TH

Timor-Leste TL

Togo TG

Tokelau TK





Tonga TO

Trinidad and Tobago TT

Tunisia TN

Turkey TR

Turkmenistan TM

Turks and Caicos Islands (UK) TC

Tuvalu TV

Uganda UG

Ukraine UA

United Arab Emirates AE

Uruguay UY

Uzbekistan UZ

Vanuatu VU

Venezuela VE

Vietnam VN

Western Sahara EH

Yemen YE

Zambia ZM

Zimbabwe ZW





PPEN

DIX

A

G
Restricted and Denied Parties List
Export Compliance uses the following government agency lists to screen order data. If you use Decision Manager, you can use these lists to create custom rules.

Important

To leverage any lists other than the default categories of OFAC and TEL, users must specify list categories when calling the service. When requesting a list category, all respective programs are reviewed.

Table 23 Restricted and Denied Parties List

List Category Program Abbreviation NameAUSTRALIA AUS_UNSC Australia Department of Foreign Affairs and Trade

(DFAT) United Nations Security Council (UNSC) Resolution

AUS_ALQ Australia DFAT UNSCR 1267 - Al Qaida and Taliban

AUS_CAR Australia DFAT UNSCR 2127 - Central Africa Republic

AUS_IRN Australia DFAT UNSCR 1737 - Iran

AUS_IRQ Australia DFAT UNSCR 1518 - Iraq

AUS_AUTO_LIB Australia Autonomous Sanctions Regulations 2011 - Libya

AUS_AUTO_KOR Australia Autonomous Sanctions Regulations 2011 - North Korea

AUS_KOR Australia DFAT UNSCR 1718 - North Korea

AUS_SOM Australia DFAT UNSCR 751 - Somalia

AUS_SDT Australia DFAT Foreign Affair

AUS_SUD Australia DFAT UNSCR 1591 - Sudan

AUS_LBR Australia DFAT UnSCR 1521 - Liberia

AUS_UKR Autonomous (Ukraine)

AUS_AUTO_ZIM Australia Autonomous Sanctions Regulations 2011 - Zimbabwe

BIS BIS_DPL BIS Denied Person List

BIS_ENT BIS Entity List

BIS_UNV BIS Unverified List

68

Appendix G Restricted and Denied Parties List

CAN_CCTER CAN_CCTER Canada Criminal Code Terrorist Entities

CAN_FACFO CAN_FACFO Canada Freezing Assets of Corrupt Foreign Officials (FACFO) Act

CAN_JVCFO CAN_JVCFO Canada Justice for Victims of Corrupt Foreign Officials Regulations

CAN_SEMA CAN_SEMA Canada Special Economic Measures Act (SEMA)

CANADA_SC CANADA_SC Canada Sanctioned Countries List

DOS_CISADA DOS_CISADA Dept of State Comprehensive Iran Sanctions, Accountability and Divestment Act of 2010 (CISADA)

DOS_DTC US_DEBARRED Defense Trade Controls Debarred Parties List

DOS_ISN ISN_ISNA Iran Syria Non-Proliferation Act of 2005

ISN_MSL BIS Missile Sanctions Laws

ISN_CBW BIS Chemical and Biological Weapons Sanctions

ISN_NPWMD Nonproliferator Weapons of Mass Destruction

ISN_LME Sanctions for the Transfer of Lethal Military Equipment

ISN_Iran_Iraq Iran-Iraq Arms Nonproliferation Act of 1992

ISN_INKSNA Iran, North Korea, Syria Nonproliferation Act Sanctions

ISN_INPA Iran Nonproliferation Act of 2000

ENGLAND HMTreasury Her Majesty’s Treasury (HM Treasury) Sanction List

HMT_AFG HM Treasury Afghanistan Sanction

HMT_SYR HM Treasury Syria Sanction

HMT_BEL HM Treasury Belarus Sanction

HMT_CAF HM Treasury Central African Republic Sanction

HMT_CON HM Treasury Congo Sanction

HMT_EGY HM Treasury Egypt Sanction

HMT_IRN HM Treasury Iran Sanction

HMT_DPRK HM Treasury North Korea Sanction

HMT_GIN HM Treasury Republic of Guinea Sanction

HMT_GNB HM Treasury Guinea-Bissau Sanction

HMT_SOM HM Treasury Somalia Sanction

HMT_ALQ HM Treasury Al-Qaida Sanction

HMT_SUD HM Treasury Sudan Sanction

HMT_SDT HM Treasury Terrorist Financing Sanction

HMT_UKM Ukraine (Misappropriation)

Table 23 Restricted and Denied Parties List (Continued)

List Category Program Abbreviation Name



HMT_UKS Ukraine (Sovereignty)

HMT_YEM Yemen

HMT_ZIM HM Treasury Zimbabwe Sanction

EUROPE EUROPE European Sanctions and Embargoes

FATF FATF Financial Action Task Force on Money Laundering

FBI FBI_10MW Federal Bureau of Investigation (FBI) Ten Most Wanted Fugitives List

FBI_FGT FBI Wanted Fugitives List

HMT_USTI HMT_USL HM Treasury Ukraine Sovereignty and Territorial Integrity (USTI) List

INTERPOL INTERPOL Recent Most Wanted List & Hague International Criminal Court

JAPAN JAPAN Japan Ministry of Economy, Trade and Industry (METI) Sanction List

OFAC BALKANS Balkans

BELARUS Belarus Executive Order and Designations

BPI-PA Blocked Pending Investigation - Patriot Act of 2001

BPI-SDNT Blocked Pending Investigation - SDNT

BPI-SDNTK Blocked Pending Investigation - SDNT Kingpin Act

BURMA Burma Sanctions

JADE Burma Junta’s Anti-Democratic Efforts

COTED Côte d'Ivoire (Ivory Coast) Sanctions

CUBA Cuba Sanctions

DRCONGO Democratic Republic of the Congo

FinCEN_311F FinCEN 311 List - The Finding

FinCEN_311R FinCEN 311 List - The Final Rule

FinCEN_311P FinCEN 311 List - The Notice of Proposed Rulemaking

FTO Foreign Terrorist Organization

IRAN Iran

IRAQ2 Iraq Sanctions - Blocking property of the former regimes - Exec 13315

IRAQ3 Iraq Sanctions - Executive Order 13350

LEBANON Lebanon

LIBERIA Liberia

LIBYA2 Libya Sanctions





NPWMD Non-Proliferators Weapons of Mass Destruction

NS-PLC Non-SDN Palestinian Legislative Council

DPRK North Korea

SOMALIA Somalia Sanctions

SDGT Specially Designated Global Terrorist

SDNT Specially Designated Narcotics Traffickers

SDNTK Specially Designated Narcotics Traffickers - Kingpin Act

SDT Specially Designated Terrorist

SUDAN Sudan

DARFUR Sudan Darfur Region

SYRIA Syria

TCO Transnational Criminal Organizations

WMD Weapons of Mass Destruction Trade Control Regulations

ZIMB Zimbabwe

OFAC_SSI UKRAINE-EO13662 OFAC Sectoral Sanctions Identifications List - UKRAINE Executive Order 13662

TEL DOS_TEL Terrorist Exclusion List

UNSL UN_ALQ UN Resolutions 1267 (1999) and 1989 (2011) concerning Al-Qaeda and associated individuals and entities

UN_CAR UN Resolution 2127 (2013) concerning Central African Republic

UN_CON UN Resolution 1533 (2004) concerning the Democratic Republic of the Congo

UN_DPRK UN Resolution 1718 (2006) concerning the Democratic People’s Republic of Korea

UN_GNB UN Resolution 2048 (2012) concerning Guinea-Bissau

UN_IRN UN Resolution 1737 (2006) concerning the Islamic Republic of Iran

UN_IRQ UN Resolution 1518 (2003) concerning Iraq and Kuwait

UN_IVO UN SCR 1572 - Cote d'Ivoire

UN_LBR UN SCR 1521 - Liberia

UN_LIB UN Resolution 1970 (2011) concerning Libya

UN_MLI UN SCR 2374 - Mali





UN_SLE UN SCR 1132 - Sierra Leone

UN_SOM United Nations Sanction List - Resolutions 751 (1992) and 1907 (2009) concerning Somalia and Eritrea

UN_SOSUD UN SCR 2206 - South Sudan

UN_SUD UN Resolution 1591 (2005) and 2206 (2015) concerning The Sudan

UN_TAL UN Resolution 1988 (2011) concerning All States - Taliban

UN_YEM UN Resolution 2140 (2014) concerning Yemen

WBNK WBNK_DEBARRED World Bank Listing of Ineligible Firms and Individuals





PPEN

DIX

A

H
Address Type
The following address type codes are returned in the dav_address_type reply field.

Table 24 Address Type Codes

Code DescriptionF Firm.

G General delivery.

H High-rise apartment or office building.

M Military.

P Post office box.

R Rural route or highway contract.

S Street (usually one side of one city block).

FD Firm default. The standardization process was unable to assign a firm extended ZIP code.

GD General delivery default. Assign when general delivery is the only primary name listed for the ZIP code.

HD High-rise default. The standardization process assigned the extended ZIP code for the entire building. Assignment at the unit, floor, or wing level is possible. A suite or apartment number may be out of range.

RD Rural route or highway contract default. The standardization process assigned the extended ZIP code for the entire route but was unable to assign the box number.

SD Street default. The standardization process assigned the extended ZIP code for the block because no extended ZIP code for the building.

UD Unique default. Either the owner of the ZIP code did not assign extended ZIP codes, or the address was not matched.

73

Date post:	10-Jul-2020
Category:	Documents
Upload:	others
View:	12 times
Download:	0 times