Testing Direct Debit Transactions

If you have elected to offer Direct Debits as an alternate payment method, you are required to complete the tests in this section. Data sets are provided for you to use to test your construction of XML request messages, as well as the parsing of the response messages for Direct Debit transactions.

The eCheck Verification test is required only if you plan to perform eCheck Verifications.

To test eCheck Verification transactions:

1. Verify that your XML template is coded correctly (refer to eCheck Verification Transactions).

2. Submit the eCheck Verification transactions using the data sets supplied in Table 2-3.

3. Verify that your response values match those shown in the Key Response Elements section of Table 2-3.

4. After you complete this test, go to the next Direct Debit test.

TABLE 2-3 eCheck Verification Test Data

orderId	Supplied Data Elements		Key Response Elements
	Element	Value	Element	Value
37	<amount> <orderSource> <firstName> <lastName> <accType> <accNum> <routingNum>	3001 telephone Tom Black Checking 10@BC99999 053100300	<response> <message>	301 Invalid Account Number
38	<amount> <orderSource> <firstName> <lastName> <accType> <accNum> <routingNum>	3002 telephone John Smith Checking 1099999999 011075150	<response> <message>	000 Approved
39	<amount> <orderSource> <firstName> <lastName> <companyName> <accType> <accNum> <routingNum>	3003 telephone Robert Jones Good Goods Inc Corporate 3099999999 053100300	<response> <message>	950 Declined - Negative Information on File

To test eCheck Prenotification transactions:

The eCheck Prenotification tests are required only if you plan to perfor eCheck Prenotification. You can only submit eCheck Prenotification transactions in Batches.

1. Verify that your XML templates are coded correctly (refer to eCheck Prenotification Credit Transactions (Batch Only) and eCheck Prenotification Sale Transactions (Batch Only).)

2. Submit the eCheck Verification transactions using the data sets supplied in TABLE 2-4.

3. Verify that your response values match those shown in the Key Response Elements section of TABLE 2-4.

4. After you complete this test, go to the next Direct Debit test.

TABLE 2-4 eCheck Prenotification Test Data

orderId	Supplied Data Elements		Key Response Elements
	Element	Value	Element	Value
ECPreNoteSale	<orderSource> <name> <accType> <accNum> <routingNum>	ecommerce PreNote Sale Corp Corporate 1092969901 011075150	<response> <message>	000 Approved
ECPreNoteCredit	<orderSource> <name> <accType> <accNum> <routingNum>	ecommerce PreNote Credit Corp Corporate 1099339999 011075150	<response> <message>	000 Approved
PreNoteSaleAccNumErr	<orderSource> <name> <accType> <accNum> <routingNum>	ecommerce PreNote Sale Corp Corporate 10@2969901 011100012	<response> <message>	301 Invalid Account Number
PreNoteCreditAccNumErr	<orderSource> <name> <accType> <accNum> <routingNum>	ecommerce PreNote Credit Personal Savings 10@2969901 011100012	<response> <message>	301 Invalid Account Number
PreNoteSaleRoutNumErr	<orderSource> <name> <accType> <accNum> <routingNum>	ecommerce PreNote Sale Personal Checking 6099999992 053133052	<response> <message>	900 Invalid Bank Routing Number
PreNoteCreditRoutNumErr	<orderSource> <name> <accType> <accNum> <routingNum>	ecommerce PreNote Credit Personal Checking 6099999992 053133052	<response> <message>	900 Invalid Bank Routing Number

To test eCheck Sale transactions:

1. Verify that your XML template is coded correctly (refer to eCheck Sale Transactions).

2. Submit the echeckSale transactions using the Supplied Data elements shown in TABLE 2-5. Submit the test transaction with orderId of Canadian Echeck, only if you are provisioned for Canadian Direct Debit transactions.

In addition to the test data provided in the table, you must also provide appropriate data for other child elements of the billToAddress element, such as Address1 (2, 3), city, state, phone, etc.

3. Verify that your response values match those shown in TABLE 2-5.

4. After you complete this test, go to the next test.

TABLE 2-5 eCheck Sale Test Data

orderId	Supplied Data Elements		Key Response Elements
	Element	Value	Element	Value
41	<amount> <orderSource> <firstName> <middleInitial> <lastName> <accType> <accNum> <routingNum>	2008 telephone Mike J Hammer Checking 10@BC99999 053100300	<response> <message>	301 Invalid Account Number
42	<amount> <orderSource> <firstName> <lastName> <accType> <accNum> <routingNum>	2004 telephone Tom Black Checking 4099999992 011075150	<response> <message>	000 Approved
43	<amount> <orderSource> <firstName> <lastName> <companyName> <accType> <accNum> <routingNum>	2007 telephone Peter Green Green Co Corporate 6099999992 011075150	<response> <message>	000 Approved This response will include the accountUpdater element (see accountUpdater ).
44	<amount> <orderSource> <firstName> <lastName> <companyName> <accType> <accNum> <routingNum>	2009 telephone Peter Green Green Co Corporate 9099999992 053133052	<response> <message>	900 Invalid Bank Routing Number
Canadian Echeck	<amount> <orderSource> <name> <firstName> <lastName> <accType> <accNum> <routingNum>	1001 ecommerce Peter Green Peter Green Checking 109999999 000419392	<response> <message>	000 Approved
DD_Sale_Limit	<amount> <orderSource> <name> <firstName> <lastName> <accType> <accNum> <routingNum>	9999999 ecommerce Peter Green Peter Green Checking 555559999 000419392	<response> <message>	965 Allowed daily Direct Debit capture (eCheckSale) limit exceeded.

To test eCheck Credit transactions:

1. Verify that your XML template is coded correctly (refer to eCheck Credit Transactions.)

In addition to the test data provided in the table, you must also provide appropriate data for other child elements of the billToAddress element, such as Address1 (2, 3), city, state, phone, etc.

2. Submit the echeckCredit transactions using the data in the Supplied Data Elements section of Table 2-6.

3. Verify that your response values match those shown in the Key Response Elements section of Table 2-6.

4. After you complete this test, go to the next test.

TABLE 2-6 eCheck Credit Test Data

orderId	Supplied Data Elements		Key Response Elements
	Element	Value	Element	Value
45	<amount> <orderSource> <firstName> <lastName> <accType> <accNum> <routingNum>	1001 telephone John Smith Checking 10@BC99999 053100300	<response> <message>	301 Invalid Account Number
46	<amount> <orderSource> <firstName> <lastName> <companyName> <accType> <accNum> <routingNum>	1003 telephone Robert Jones Widget Inc Corporate 3099999999 011075150	<response> <message>	000 Approved
47	<amount> <orderSource> <firstName> <lastName> <companyName> <accType> <accNum> <routingNum>	1007 telephone Peter Green Green Co Corporate 6099999992 011075150	<response> <message>	000 Approved       This response will include the accountUpdater element (see accountUpdater).
48	<cnpTxnId>	Value returned in eCheck Sale response for Order ID 43	<response> <message>	000 Approved
49	<cnpTxnId>	2	<response> <message>   Declined Transaction report result = 360 - No transaction found with specified cnpTxnId	000 Approved
DD_Credit_Limit	<amount> <orderSource> <firstName> <lastName> <companyName> <accType> <accNum> <routingNum>	9999999 telephone Peter Green Green Co Corporate 5555599993 211370545	<response> <message>	966 Allowed daily Direct Debit credit (eCheckCredit) limit exceeded.

To test eCheck Void transactions:

1. Verify that your eCheck XML template is coded correctly (refer to eCheck Void Transactions (Online Only) )

2. (Re)Submit the echeckSale transaction for Order ID #42 as shown in Table 2-5 with a different value for the id attribute.

   1. Using the cnpTxnId returned in the echeckSaleResponse message, submit an echeckVoid transaction.

   2. The system returns an echeckVoidResponse Response Code of 000 and a message of Approved.

3. Using the cnpTxnId returned in the echeckCreditResponse message for Order ID #46, submit an echeckVoid transaction.

   1. The system returns an echeckVoidResponse Response Code of 000 and a message ofApproved.

4. Submit an echeckVoid request using a value of 2 for the cnpTxnId.

   1. The system returns a Response Code of 000 and a message of Approved; however, the Declined Transaction Report will contain a Response Code of 360 and a message of No transaction found with specified cnpTxnId for this transaction.

5. After you complete this test, go to the next test.