Testing Authorization (including Indicators), AVS Only, Capture, Credit, Sale, and Void Transactions

To test your handling of 2-series (BIN) number for Mastercard, you can substitute a 2-series test card number (see Appendix C - Test Card Numbers) in any Auth/Sale test and you will receive a 000 - Approved Response Code in the response message.

TABLE 2-1 Authorization Test Data provides 26 data sets you use to test your construction of Authorization, AVS Only, Sale and Force Capture transactions, as well as your ability to parse the information contained in the XML response messages. You also use some of the approved authorizations as the basis for testing Capture and Credit transactions.

You do not necessarily have to perform all Authorization test. The tests you perform depend upon the Worldpay features you have elected to use. The tests are divided as follows:

  • Order IDs 1 through 9 - used to test standard Authorization requests and responses. Also used for AVS Only test and Sale test. (Capture test use the cnpTxnId returned in the response messages.)

  • Order IDs 10 through 13 - include if you plan to use Partial Authorization

  • Order IDs 14 and 20 - include if you plan to use the Prepaid Indicator feature (see Prepaid Indicator)

  • Order IDs 21 through 24 - include if you plan to use the Affluence Indicator feature (see Affluence Indicator)

  • Order ID 25 - include if you plan to use the Issuer Country feature (see Issuer Country Indicator)

To test Authorization transactions:

  1. Verify that your Authorization XML template is coded correctly (see Authorization Transactions)

  2. Submit authorization transactions using the data shown in the Supplied Data Elements of Order IDs 1 through 9 of TABLE 2-1 Authorization Test Data.

  3. Verify that your response values match those shown in Key Response Elements for Order IDs 1 through 9 as shown in TABLE 2-1 Authorization Test Data.

  4. If you wish to test AVS only transactions, re-submit Order IDs 1 through 5, 7, 8, and 9 (skip order 6), but substitute 000 for the amount. The AVS result returned will be the value shown in the Key Response Elements section.

Some Issuers do not return an Auth Code for $0 Authorizations. You should code your systems to handle this possibility.

  1. If you plan to use Partial Authorizations, submit authorization transactions using the data shown in the Supplied Data Elements of Order IDs 10 through 13 of TABLE 2-1 Authorization Test Data.

  2. Verify that your response values match those shown in Key Response Elements for Order IDs 10 through 13 as shown in TABLE 2-1 Authorization Test Data.

  3. If you elected to receive Prepaid Indicators, submit authorization transactions using the data shown in the Supplied Data Elements of Order IDs 14 through 20 of TABLE 2-1 Authorization Test Data. Verify that your response values match those shown in Key Response Elements for Order IDs 14 and 15 as shown in TABLE 2-1 Authorization Test Data.

  4. If you elected to receive Affluence Indicators, submit authorization transactions using the data shown in the Supplied Data Elements of Order IDs 21through 24 of TABLE 2-1 Authorization Test Data. Verify that your response values match those shown in Key Response Elements for Order IDs 16 through 19 as shown in TABLE 2-1 Authorization Test Data.

  5. If you elected to receive Issuer Country information, submit an authorization transaction using the data shown in the Supplied Data Elements of Order ID 25 of TABLE 2-1 Authorization Test Data. Verify that your response values match those shown in Key Response Elements for Order ID 25 as shown in TABLE 2-1 Authorization Test Data.

  6. If you elected to receive Issuer Insights data, submit an authorization transaction using the data shown in the Supplied Data Elements of Order ID IssuerInsights of TABLE 2-1 Authorization Test Data. Verify that your response values match those shown in Key Response Elements for Order ID 25 as shown in TABLE 2-1 Authorization Test Data. This data includes the accountRangeId element in the response message.

  7. If you plan to handle transactions using Healthcare (IIAS) cards, submit authorization transactions using the data shown in the Supplied Data Elements of Order IDs 26 through 31A of TABLE 2-1 Authorization Test Data. Verify that your response values match those shown in Key Response Elements for Order IDs 26 through 31 as shown in TABLE 2-1 Authorization Test Data.

To Test Sale transactions:

  1. Verify that your Sale XML template is coded correctly (seeSale Transactions).

  2. Submit sale transactions using the data shown in the Supplied Data Elements of Order IDs 1 through 9 of TABLE 2-1 Authorization Test Data.

  3. Verify that your response values match those shown in Key Response Elements for Order IDs 1 through 9 as shown in TABLE 2-1 Authorization Test Data.

To Test Capture transactions:

  1. Verify that your Capture XML template is coded correctly (see Capture Transactions.).

  2. Submit capture transactions for Order IDs 1A through 5A using the cnpTxnId value returned in the response messages for Authorization Order IDs 1 through 5.

  3. Verify that your response values match those shown in Key Response Elements for Order IDs 1A through 5A as shown in TABLE 2-1 Authorization Test Data.

To test Credit transactions:

  1. Verify that your Credit XML template is coded correctly (see Credit Transactions.)

  2. Submit credit transactions for Order IDs 1B through 5B using the cnpTxnId value returned in the response messages for Capture Order IDs 1A through 5A.

  3. Verify that your response values match those shown in Key Response Elements for Order IDs 1B through 5B as shown in TABLE 2-1 Authorization Test Data.

If you coded to schema V11 or above, verify the Approved status of credit transaction by reviewing the Decline transaction report.

To test Void transactions (in this test you have the option of voiding either Credit or Sale transactions):

  1. Verify that your Void XML template is coded correctly (seeVoid Transaction (Online Only)).

  2. Submit void transactions for Order IDs 1C through 5C (and 6B if voiding Sale transactions) using the cnpTxnId value returned in either the response messages for Credit Order IDs 1B through 5B, or the response messages for Sale (not Auth) Order ID 1 through 6.

Verify that your response values match those shown in Key Response Elements for Order IDs 1C through 5C (include 6B only if you elect to void the Sales transactions) as shown in TABLE 2-1 Authorization Test Data.

TABLE 2-1 Authorization Test Data

orderID

Supplied Data Elements

Key Response Elements

Element

Value

Element

Value

1

Authorization/Sale/AVS:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

 

10100

John & Mary Smith

1 Main St.

Burlington

MA

01803-3747

US

VI

4457010000000009

0150

349

Authorization Response:

<response>

<message>

<authCode>

<avsResult>

<cardValidationResult>

 

 

 

 

 

 

000

Approved

11111

01

M

 

 

 

 

 

1A

Capture:

 

<cnpTxnId>

 

Value returned in Auth response for Order Id 1

Capture Response:

<response>

<message>

 

000

Approved

1B

Credit:

 

<cnpTxnId>

 

Value returned in Capture response for Order Id 1A

Credit Response:

<response>

<message>

 

000

Approved

1C

Void:

 

<cnpTxnId>

 

Use either the value returned in the Credit response for Order Id 1B, or the value returned in the Sale response (not Auth) for Order Id 1.

Void Response:

<response>

<message>

 

000

Approved

2

Authorization/Sale/AVS

<amount>

<name>

<addressLine1>

<addressLine2>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

<authenticationValue>

 

10100

Mike J. Hammer

2 Main St.

Apt. 222

Riverside

RI

02915

US

MC

5112010000000003

0250

261

BwABBJQ1AgAAA AAgJDUCAAAAAA A=

Authorization Response:

<response>

<message>

<authCode>

<avsResult>

<cardValidationResult>

<authenticationResult>

 

 

 

 

 

 

 

 

000

Approved

22222

10

M

Note: Not returned for Mastercard

 

 

 

 

 

2A

Capture:

 

<cnpTxnId>

 

Value returned in Auth response for Order ID 2

Capture Response:

<response>

<message>

 

000

Approved

2B

Credit:

 

<cnpTxnId>

 

Value returned in Capture response for Order ID 2A

Credit Response:

<response>

<message>

 

000

Approved

2C

Void:

 

<cnpTxnId>

 

Use either the value returned in the Credit response for Order Id 2B, or the value returned in the Sale response (not Auth) for Order Id 2.

Void Response:

<response>

<message>

 

000

Approved

3

Authorization/Sale/AVS:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

 

10100

Eileen Jones

3 Main St.

Bloomfield

CT

06002

US

DI

6011010000000003

0350

758

Authorization Response:

<response>

<message>

<authCode>

<avsResult>

<cardValidationResult>

 

 

 

 

 

 

 

000

Approved

33333

10

M

 

 

 

 

 

 

3A

Capture:

 

<cnpTxnId>

 

Value returned in Auth response for Order Id 3

Capture Response:

<response>

<message>

 

000

Approved

3B

Credit:

 

<cnpTxnId>

 

Value returned in Capture response for Order Id 3A

Credit Response:

<response>

<message>

 

000

Approved

3C

Void:

 

<cnpTxnId>

 

Use either the value returned in the Credit response for Order Id 3B, or the value returned in the Sale response (not Auth) for Order Id 3.

Void Response:

<response>

<message>

 

000

Approved

4

Authorization/Sale/AVS:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

 

10100

Bob Black

4 Main St.

Laurel

MD

20708

US

AX

375001000000005

0450

Authorization Response:

<response>

<message>

<authCode>

<avsResult>

 

 

 

 

 

 

 

000

Approved

44444

13

 

 

 

 

 

 

4A

Capture:

 

<cnpTxnId>

 

Value returned in Auth response for Order Id 4

Capture Response:

<response>

<message>

 

000

Approved

4B

Credit:

 

<cnpTxnId>

 

Value returned in Capture response for Order Id 4A

Credit Response:

<response>

<message>

 

000

Approved

4C

Void:

 

<cnpTxnId>

 

Use either the value returned in the Credit response for Order Id 4B, or the value returned in the Sale response (not Auth) for Order Id 4.

Void Response:

<response>

<message>

 

000

Approved

5

Authorization/Sale/AVS:

<amount>

<type>

<number>

<expDate>

<cardValidationNum>

<authenticationValue>

 

10100

VI

4100200300011001

0550

463

BwABBJQ1AgAAA AAgJDUCAAAAAA A=

Authorization Response:

<response>

<message>

<authCode>

<avsResult>

<cardValidationResult>

 

000

Approved

55555

32

M

5A

Capture:

 

<cnpTxnId>

 

Value returned in Auth response for Order ID 5

Capture Response:

<response>

<message>

 

000

Approved

5B

Credit:

 

<cnpTxnId>

 

Value returned in Capture response for Order ID 5A

Credit Response:

<response>

<message>

 

000

Approved

5C

Void:

 

<cnpTxnId>

 

Use either the value returned in the Credit response for Order Id 5B, or the value returned in the Sale response (not Auth) for Order Id 5.

Void Response:

<response>

<message>

 

000

Approved

6

Authorization/Sale:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

 

10100

Joe Green

6 Main St.

Derry

NH

03038

US

VI

4457010100000008

0650

992

Authorization Response:

<response>

<message>

<avsResult>

<cardValidationResult>

 

110

Insufficient Funds 34

P

6A

Void:

<cnpTxnId>

 

Use the value returned in the Sale response (not Auth) for Order Id 6.

Void Response:

<response>

<message>

 

Declined Transaction report result = 360 - No transaction found with specified cnpTxnId

 

000

Approved

 

 

 

 

7

Authorization/Sale/AVS:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

 

10100

Jane Murray

7 Main St.

Amesbury

MA

01913

US

MC

5112010100000002

0750

251

Authorization Response:

<response>

<message>

 

<avsResult>

<cardValidationResult>

 

301

Invalid Account Number

34

N

8

Authorization/Sale/AVS:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

 

10100

Mark Johnson

8 Main St.

Manchester

NH

03101

US

DI

6011010100000002

0850

184

Authorization Response:

<response>

<message>

<avsResult>

<cardValidationResult>

 

 

 

 

 

 

 

 

123

Call Discover

34

P

 

 

 

 

 

 

 

9

Authorization/Sale/AVS:

<amount>

<name>

<addressLine1>

<city>

<state>

<zip>

<country>

<type>

<number>

<expDate>

<cardValidationNum>

 

10100

James Miller

9 Main St.

Boston

MA

02134

US

AX

375001010000003

0950

0421

Authorization Response:

<response>

<message>

<avsResult>

<cardValidationResult>

 

 

 

 

 

 

 

 

303

Pick Up Card

34

P

 

 

 

 

 

 

 

The data sets for orderId 10 through 13 are designed to test Authorization transactions resulting in partial authorizations. If you are not coding to use partial authorizations, you may skip these tests.

10

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

40000

VI

84457010140000141

0950

true

<response>

<message>

<approvedAmount>

 

010

Partially Approved

32000

 

11

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

60000

MC

5112010140000004

1150

true

<response>

<message>

<approvedAmount>

010

Partially Approved

48000

12

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

50000

AX

375001014000009

0450

true

<response>

<message>

<approvedAmount>

 

010

Partially Approved

40000

 

13

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

15000

DI

6011010140000004

0850

true

<response>

<message>

<approvedAmount>

 

010

Partially Approved

12000

 

The data sets for orderId 14 through 20 are designed to test Authorization transactions that return Prepaid Indicator information in the response message. If you are not coding to use the optional Prepaid Indicator feature of the Insights feature set, you may skip these tests.

14

<amount>

<type>

<number>

<expDate>

10100

VI

4457010200000247

0850

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

2000

NO

GIFT

15

<amount>

<type>

<number>

<expDate>

10100

MC

5500000254444445

0350

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

2000

YES

PAYROLL

16

<amount>

<type>

<number>

<expDate>

10100

MC

5592106621450897

0350

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

0

YES

PAYROLL

17

<amount>

<type>

<number>

<expDate>

10100

MC

5590409551104142

0350

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

6500

YES

PAYROLL

18

<amount>

<type>

<number>

<expDate>

10100

MC

5587755665222179

0350

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

12200

YES

PAYROLL

19

<amount>

<type>

<number>

<expDate>

10100

MC

5445840176552850

0350

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

20000

YES

PAYROLL

20

<amount>

<type>

<number>

<expDate>

10100

MC

5390016478904678

0350

<response>

<message>

<type>

<availableBalance>

<reloadable>

<prepaidCardType>

000

Approved

PREPAID

10050

YES

PAYROLL

The data sets for orderId 21 through 24 are designed to test Authorization transactions that return Affluence Indicator information in the response message. If you are not coding to use the optional Affluence Indicator feature of the Insights feature set, you may skip these tests.

21

<amount>

<type>

<number>

<expDate>

10100

VI

4100200300012009

0950

<response>

<message>

<affluence>

000

Approved

AFFLUENT

22

<amount>

<type>

<number>

<expDate>

10100

VI

4100200300013007

1150

<response>

<message>

<affluence>

 

000

Approved

MASS AFFLUENT

23

<amount>

<type>

<number>

<expDate>

10100

MC

5112010201000109

0450

<response>

<message>

<affluence>

000

Approved

AFFLUENT

24

<amount>

<type>

<number>

<expDate>

10100

MC

5112010202000108

0850

<response>

<message>

<affluence>

 

000

Approved

MASS AFFLUENT

The data set for orderId 25 is designed to test Authorization transactions that return Issuer Country information in the response message. If you are not coding to use the optional Issuer Country feature of the Insights feature set, you may skip these tests.

25

<amount>

<type>

<number>

<expDate>

10100

VI

4100200310000002

1150

<response>

<message>

<issuerCountry>

000

Approved

BRA

The data set for orderId IssuerInsights is designed to test Authorization transactions that return an Account Range Id in the response message.

IssuerInsights

<amount>

<type>

<number>

<expDate>

12789

VI

4457010200000247

1150

<response>

<message>

<issuerCountry>

000

Approved

108

The data sets for orderId 26 through 31A are designed to test Authorization transactions involving Healthcare Care (IIAS) transaction. If you are not coding to perform Healthcare Care (IIAS) transactions, you may skip these tests.

26

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

18698

MC

5194560012341234

1250

true

20000

<response>

<message>

 

 

341

Invalid healthcare

amounts

27

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

<RxAmount>

18698

MC

5194560012341234

1250

true

15000

16000

<response>

<message>

 

 

341

Invalid healthcare

amounts

28

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

<RxAmount>

15000

MC

5194560012341234

1250

true

15000

3698

<response>

<message>

000

Approved

29

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

<RxAmount>

<visionAmount>

<clinicOtherAmount>

<dentalAmount>

18699

VI

4024720001231239

1250

true

31000

20910

1000

9050

1049

<response>

<message>

 

 

341

Invalid healthcare

amounts

30

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

<RxAmount>

<visionAmount>

<clinicOtherAmount>

<dentalAmount>

20000

VI

4024720001231239

1250

true

20000

20901

1000

9050

1049

<response>

<message>

 

341

Invalid healthcare amounts

31

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

<RxAmount>

<visionAmount>

<clinicOtherAmount>

40000

VI

4024720001231239

1250

true

18699

1000

15099

17699

<response>

<message>

<approvedAmount>

010

Partially Approved

18689

31A

<amount>

<type>

<number>

<expDate>

<allowPartialAuth>

<totalHealthcareAmount>

<RxAmount>

<visionAmount>

6000

VI

4024720001231239

1250

true

5000

5000

1000

<response>

<message>

000

Approved