Home > Testing Electronic Check Services > Testing Chase Paymentech Solutions Transactions


Testing Chase Paymentech Solutions Transactions

Successful Transactions

Use the data in the following table to simulate successful debits and credits for Chase Paymentech Solutions.

Table 8Test Data for Chase Paymentech Solutions
Debits and Credits

Field

Test Values

Required / Optional

check_accountNumber 

n4100

n4101

n4102

n4103

Required

check_accountType 

nC

nS

nX

Required

check_bankTransitNumber 

n121042882

n121107882

n071923284

n122101191

Required

ecDebitService_settlementMethod

nA

nB

nF

Optional

ecDebitService_verificationLevel 

n1

n2

Optional

Testing Chase Paymentech Solutions Declines

For Chase Paymentech Solutions, you can simulate electronic check declines using specific bank account numbers for debits. For a list of these values and the expected results, see Using the Test Simulator.

Testing Cybersource ACH Service Transactions

Use the data in the following table to simulate ACH verification by requesting a debit for the Cybersource ACH Service. As an alternative, you can simulate ACH verification by requesting a credit: the reply fields will be for the credit service instead of the debit service.

Table 9ACH Verification Test Data

 

Triggers

Reply Fields

Type of Field

Account Number

Routing Number

Mapped ACH Verification Code

Raw ACH Verification Code

Corrected Account Number

Corrected Routing Number

Field Name

check_
account
Number

check_
bankTransit
Number

ecDebitReply_verification
Code

ecDebitReply_verification
CodeRaw

ecDebitReply_corrected
Account
Number

ecDebitReply_corrected
Routing
Number

 

12345678

112200439

00

1

0011111111111

011000028

01

2

00111111

1231231230

231385154

00

3

 

123123123

231385154

00

4

00111111

011201762

02

5

011201830

001234567895

011400039

03

6

1234567895

011401533

01111111

011301073

02

7

211070175

1231231230

011001742

02

8

011000138

1231231230

231382704

04

91

12345678

115101438

04

101

1   See the following table for the reply values for this error.

Table 10ACH Verification Error Reply Values

Raw ACH Verification Code

Error Reply Values

9

decision=REJECT

reasonCode=388

10

decision=REJECT

reasonCode=388

 

Testing RBS WorldPay Atlanta

See Using the Test Simulator.

Testing TeleCheck

See Using the Test Simulator.

Going Live

You must go live with Cybersource before you start submitting production transactions. When you go live, your account is updated so that you can send transactions to the Cybersource production server. If you have not already done so, provide your banking information to Cybersource so that your processor can deposit funds to your merchant bank account. For information about going live, see Getting Started with CyberSource Essentials.