Testing the Recycling Engine

The Certification test cases for the Recycling Engine serve two purposes. First, you use the test transactions to verify your handling of the responses you receive if you submit additional Authorization transactions for a declined auth being handled by the engine. Second, you can verify your process for retrieving and processing recycling completion files via sFTP.

There are three test scenarios you can use to test the Recycling Engine and your ability to parse the response messages and/or result Batches. The particular data sets and scenarios you use depends upon the version of cnpAPI you use, as well as your plans for retrieving the response messages. Use the following to determine which tests you should run:

  • If you plan to retrieve recycling results via the results Batches posted daily to the FTP site, perform the tests in Scenario 1

  • If you are using cnpAPI schema version V8.6 or above, perform the tests in Scenario 2

Scenario 1

To test your handling of the Recycling Results Session file:

  1. Submit authorization (or sale) transactions using the values provided in the Supplied Data Elements column of Table TABLE 2-24   Recycling Engine Test Data - Results Session File Pick-up. Please use the same value for the orderId and if applicable, the recycleId elements.

If your configuration is set for Worldpay to recycle by default, you can omit the <recycleBy> element.

  1. Wait a minimum of 2 hours after submitting the last transaction. After 2 hours, retrieve the Results Session file from the FTP site.

TABLE 2-24   Recycling Engine Test Data - Results Session File Pick-up

orderId

Supplied Data Elements

Key Response Elements

Element

Value

Element

Value

XXXCase1Order1r1

<amount>

<type>

<number>

<expDate>

<recycleBy>

10000

VI

4457012400000027

1220

Cnp

Initial Response:

<response>

<message>

 

<recyclingEngineA ctive>

Final Response (in FTP Session File):

<response>

<message>

 

110

Insufficient Funds

true

 

 

 

000

Approv

XXXCase1Order2

<amount>

<type>

<number>

<expDate>

<recycleBy

10000

MC

5160124000000029

1220

Cnp

Initial Response:

 

<response>

<message>

 

<recyclingEngineA ctive>

Final Response (in FTP Session File):

<response>

<message>

 

 

110

Insufficient Funds

 

true

 

000

Approved

 

XXXCase1Order3

<amount>

<type>

<number>

<expDate>

<recycleBy>

10000

VI

4100200700000059

1220

Cnp

Initial Response:

<response>

<message>

 

<recyclingEngineActive>

Final Response (in FTP Session File):

<response>

<message>

 

110

Insufficient Funds

 

true

 

 

110

Insufficient Funds

XXXCase1Order4

 

 

 

 

 

 

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

10000

MC

5500010000000052

1220

Cnp

 

 

Initial Response:

 

<response>

<message>

<recyclingEngineActive>

Final Response (in FTP Session File):

<response>

<message>

 

 

110

Insufficient Funds

true

 

 

110

Insufficient Funds

XXXCase1Order5

<amount>

<type>

<number>

<expDate>

<recycleBy>

10000

VI

4457032800000047

1220

Cnp

Initial Response:

 

<response>

<message>

<recyclingEngineActive>

Final Response (in FTP Session File):

<response>

<message>

 

 

 

110

Insufficient Funds

true

 

 

328

Cardholder requests that recurring or installment payment be stopped.

XXXCase1Order6

 

 

 

 

 

 

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

10000

MC

5160328000000042

1220

Cnp

 

 

Initial Response:

<response>

<message>

<recyclingEngineActive>

Final Response (in FTP Session File):

<response>

<message>

 

110

Insufficient Funds

true

 

 

120

Call Issuer

XXXCase1Order7

 

 

 

 

 

<amount>

<type>

<number>

<expDate>

<recycleBy>

10000

VI

5160328000000042

1220

Cnp

Initial Response:

 

<response>

<message>

 

<recyclingEngineActive>

Final Response (in FTP Session File):

None - This type of decline is not recycled.

302

Account Number Does Not Match Payment Type

false

 

 
Scenario 2

To test your handling of the Intercept Response Codes/Messages, as well as the Recycling Results Session file and Normal Batch/Online responses:

  1. Submit authorization (or sale) transactions using the values provided in the Supplied Data Elements column of TABLE 2-25   Recycling Engine Test Data - Intercept and Online or Results Session File Pick-up. Please use the same value for the orderId and if applicable, the recycleId elements.

If your configuration is set for Worldpay to recycle by default, you can omit the <recycleBy> element.

  1. If you are using schema version V8.6 or above, resubmit any of the first four transactions within 36 hours to receive a response message containing the intercept Response Reason Code 372 - Soft Decline - Auto Recycling In Progress. If you are using schema version 8.5 or below, you will receive a response message with the same Response Reason Code as in the initial response message.

  2. Wait a minimum of 36 hours after submitting the last of the initial transactions. After 36 hours, you can retrieve the Results Session file from the FTP site and/or resubmit the transaction. The responses will contain the data shown for the Final Response.

TABLE 2-25   Recycling Engine Test Data - Intercept and Online or Results Session File Pick-up

orderId

Supplied Data Elements

Key Response Elements

Element

Value

Element

Value

XXXCase3Order1

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

 

 

 

 

 

20000

DI

6223012400000025

1220

Cnp

 

 

 

 

 

 

 

Initial Response:

<response>

<message>

<recyclingEngineActive>

Intermediate Attempts (V8.6):

<response>

<message>

 

<recyclingEngineA ctive>

Final Response (Online/Normal Batch, or in FTP Session File):

<response>

<message>

 

 

350

Generic Decline

true

 

372

Soft decline - Recycling In Progress

true

 

 

000

Approved

XXXCase3Order2

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

 

 

 

 

 

20000

AX

377201240000025

1220

Cnp

 

 

 

 

 

 

 

Initial Response:

<response>

<message>

<recyclingEngineActive>

 

Intermediate Attempts (V8.6):

 

<response>

<message>

 

<recyclingEngineActive>

Final Response (Online/Normal Batch, or in FTP Session File):

<response>

<message>

 

350

Generic Decline

true

 

 

 

372

Soft decline - Recycling In Progress

true

 

 

 000

Approved

XXXCase3Order3

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

 

 

 

 

 

 

 

20000

DI

6223012400000033

1220

Cnp

 

 

 

 

 

 

 

 

 

Initial Response:

<response>

<message>

<recyclingEngineA ctive>

 

Intermediate Attempts (V8.6):

<response>

<message>

 

<recyclingEngineA ctive>

 

Final Response (Online/Normal Batch, or in FTP Session File):

<response>

<message>

 

 

350

Generic Decline

true

 

 

372

Soft decline - Recycling In Progress

true

 

 

 

373

Hard Decline - Auto Recycling Complete

XXXCase3Order4

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

 

 

 

 

 

 

 

20000

DI

6011002078551608

1220

Cnp

 

 

 

 

 

 

 

 

 

Initial Response:

<response>

<message>

<recyclingEngineActive>

Intermediate Attempts (V8.6):

<response>

<message>

 

<recyclingEngineActive>

Final Response (Online/Normal Batch, or in FTP Session File):

<response>

<message>

 

 

 

 

101

Issuer Unavailable

true

 

372

Soft decline - Recycling In Progress

true

 

 

373

Hard Decline - Auto Recycling

Complete

 

XXXCase3Order5

<amount>

<type>

<number>

<expDate>

<recycleBy>

 

 

 

20000

VI

377203280000048

1220

Cnp

 

 

 

Initial Response:

<response>

<message>

 

<recyclingEngineActive>

All Responses:

None - This type of decline is not recycled.

 

302

Account Number Does Not Match Payment Type

false