2009
Table Of Contents
- Contents
- Signing Up for Payflow ACH Payment Service
- About ACH Payments
- Summary of Authorization Requirements
- How Payflow ACH Payment Works
- ACH Payment Flow
- Timetable for a Typical ACH Payment
- Example of a Successful Business-to-Business Debit/Sale Payment
- Example of a Business-to-Business Sale/Debit Payment With a Customer Return Within Three Posting Days
- Example of a Business-to-Consumer Sale/Debit Payment With a Customer Return After Three Posting Days
- Example of a Successful Business-to-Consumer Credit Payment
- Example of a Business-to-Consumer Credit Payment With a Customer Side Return
- ACH Payment Types
- Retrying Returned Payments
- Notifications of Change
- Using PayPal Manager to Perform ACH Payments
- Using the Payflow Pro SDK to Perform ACH Payments
- Testing ACH Payments Using the Payflow SDK
- Responses to ACH Payment Requests
- Index
Payflow ACH Payment Service Guide 45
7
Testing ACH Payments Using the
Payflow SDK
This chapter describes the process of testing ACH payments using the Payflow SDK. For
complete information on using the SDK, see Payflow Pro Developer’s Guide. You can safely
skip this chapter if you have a Payflow Link account.
Responses to payment requests are described in Chapter 8, “Responses to ACH Payment
Requests.”
Testing ACH Payments — General Information
The test procedures presented in this chapter produce consumer-side results. Merchant-side
status is delayed by the specified number of posting days.
The test system settles test payments on the standard ACH schedule (every day that precedes a
banking day, typically Sunday through Thursday). See “Schedule of Submission for
Settlement” on page 13.
Test Server
Submit test ACH payment requests of any payment format or authorization type to the ACH
test server at pilot-payflowpro.paypal.com.
Test ABA Routing Number
Use ABA Routing Number 111111118 or any valid number for testing.
Test Bank Account Numbers
Do not use a real bank account number for testing. You must use one of the test bank account
numbers provided in this chapter.
IMPORTANT: Any consumer transaction to the test server using a non-test account number
results in an R03 error (invalid account number) after settlement (the
transaction proceeds without error during OLTP). This ensures that you are
notified in the case that you mistakenly sent a live transaction to the test
server.