U.S. Bank E-Payment Service
Implementation Questionnaire
The purpose of this questionnaire is to gather information necessary to implement the
U.S. Bank E-Payment Service payment site and administrative terminal. It also collects
information necessary for the transmission of the standard E-Payment Service remittance file.
Section 1 – Contact Information (to be completed by Questionnaire Contact)
Company Name
########################################
Company Address
########################################
Primary
Secondary*
Questionnaire Contact(s) – Primary contact(s) for questions regarding this Questionnaire
Name
##############
Phone Number
############
Email Address
###############
Technical Contact(s) – Primary contact(s) for technical issues regarding the Implementation
Name
###############
Phone Number
############
Email Address
###############
Security Officer(s) – Setup and maintain admin user access and entitlements for your organization
Name
###############
Phone Number
############
Email Address
###############
Contact(s) for Planned Outages – Notified of planned system outages
Name
###############
Email Address / text pager
###############
Contact(s) for Unplanned Outages – Notified of unplanned system outages
Name
###############
Email Address / text pager
###############
FTP Contact(s) – Contact for FTP issues in production
Name
###############
Phone Number
############
Email Address
###############
File Delay Contact(s) – Contact for file delays in production (notification will be sent via email)
Name
Phone Number
Email Address (or text pager)
* Optional, except Security Officer
Doc # PC-001, v4.2
1 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 2 –Admin Organization Setup (to be completed by Questionnaire Contact)
Admin Organizations define the Biller Group / Biller combinations that an admin user can access.
You can have one or many admin organizations for each Biller Group / Biller combination. Here are
two examples;
1. You have three separate E-Payment Service applications (Billers) and the admin users that
support these applications have permission to view payers, payments, reports, etc for all
three applications. In this example, you would only need to define one admin organization
2. You have three separate E-Payment Service applications (Billers) and the admin users that
support these applications only have permission to view payers, payments, reports, etc for
one of the three applications. In this example, you would need to define at least three
admin organizations, one for each biller, and possibly a fourth that would allow certain
admin users to access all three billers.
The Support Phone Number for each Admin Org ID below should be the same as the primary
Security Officer defined in Section 1 above.
1. Existing Admin Org. Does an E-Payment Service Admin Org already exist to which you would
like to add the biller you are defining in this document?
Yes
If yes, provide the ID(s)
1. Admin Org ID
No
2. Admin Org ID
3. Admin Org ID
If no, enter a 3 to 6 character abbreviation for each new admin organization along with
organization name and support phone number
1. Admin Org ID
######
Organization Name (max 25 characters)
Support Phone Number
2. Admin Org ID
Organization Name (max 25 characters)
Support Phone Number
3. Admin Org ID
Organization Name (max 25 characters)
Support Phone Number
Section 3 – Biller Group Setup (to be completed by the Technical Contact)
A Biller Group is a collection of related applications or Billers that share the same user registration
database. [Biller Group > Biller > Product]
1. Existing Biller Group. Does a Biller Group already exist for your service?
Yes
If yes, provide the three character ID ### and skip the remainder of Section 3
No
If no, enter a 3 character abbreviation
Doc # PC-001, v4.2
and complete the remainder of Section 3
2 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 3 – Biller Group Setup (to be completed by the Technical Contact)
2. Logo. Provide a customized graphic containing the logo to be displayed in the upper-left
corner on all pages. If this is a photographic image, it should be in JPEG format; otherwise, it
should be in GIF format. This graphic must be 150 pixels wide by 70 pixels high. Background
areas within the image should be transparent. (See Attachment A for the location of the logo)
Name of Logo file:
3. Navigation Background. The navigation background is an image on the left side of the screen
that repeats the length of the page. You may accept our default background as is, or customize it
to suit your needs. This graphic must be 1595 pixels wide by 50 pixels high. Background areas
within the image should be transparent. (See Attachment A for the location of the Navigation
Background)
Default Navigation Background
Other – File Name:
Names
Biller Group Short Name
4.
Biller Group Report Title
5.
Biller Group Browser Title
6.

Biller Group Short Name - used in conjunction with the Biller Short Name (Section 4) in
confirmation emails sent to the user of the payment system. Max 16 characters (See
Attachment B for a sample email confirmation)

Biller Group Report Title: used as the title line on Pay Connexion reports. This title may be
up to 80 characters long.

Biller Group Browser Title: a line of text to be displayed in conjunction with the Biller
Browser Title (Section 4) in the title bar of the Payer's browser window. This title may be up
to 40 characters long. (See Attachment A for the location of the Biller Browser Title)
7. Privacy Policy.
Option 1 – Use the site’s standard privacy policy and link to a Privacy Policy on your site. You
must provide responses for a and b below if you select this option. (See Attachment C for a
sample of how this link will appear on the E-Payment Service)
a. Provide the URL to your privacy statement
b. Provide how your company name should appear in the privacy statement
Option 2 – Use the site’s standard privacy policy. You must provide a response for a below if
you select this option. (See Attachment D for a sample of how this link will appear on the EPayment Service)
a. Provide how your company name should appear in the privacy statement
Option 3 – You may provide an html file of your privacy policy to be displayed on the EPayment Service. You must provide the file in .jpg or .gif format if you select this option.
a. File Name:
Doc # PC-001, v4.2
3 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 3 – Biller Group Setup (to be completed by the Technical Contact)
8. Custom Holidays. Does your financial institution not accept transactions on certain dates in
addition to Federal Banking Holidays and weekends? If yes, please specify these dates below for the
next three years. Use the YYYY-MM-DD format and be sure to include a name for each custom
holiday in the Description field.
Date
Description
Date
1
1
2
2
3
3
Description
Section 4 – Biller Setup (to be completed by the Technical Contact)
A Biller is a hierarchy level that defines items such as the customer service text, banner, ACH cutoff,
and settlement account. A remittance file is created for each biller. (Note: All applications within a
Biller must have the same settlement account. If a separate settlement account is required for a
particular application, that application should be setup as a separate biller)
[Biller Group > Biller > Product]
1. Existing Biller. Does a Biller already exist for your service?
Yes
If yes, provide the three character ID
and skip the remainder of Section 4
No
If no, enter a 3 character abbreviation ### and complete the remainder of Section 4
Names
Biller Short Name
2. ################
Biller Report Title
3. #######################################
Biller Browser Title
4. #######################################

Biller Short Name - used in conjunction with the Biller Group Short Name (Section 3) in
confirmation emails sent to the user of the payment system. Max 16 characters (See
Attachment B for a sample email confirmation)

Biller Report Title: used as the title line on Pay Connexion reports. This title may be up to 80
characters long.

Biller Browser Title: a line of text to be displayed in conjunction with the Biller Group Browser
Title (Section 3) in the title bar of the Payer's browser window. This title may be up to 40
characters long. (See Attachment A for the location of the Biller Browser Title)
Doc # PC-001, v4.2
4 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Payment Channels
5. Payment Channels. Select the payment channels you wish to offer to allow Payers to initiate
payments.
Web
Live Agent (through your Customer Service)
IVR
Live Agent (through U.S. Bank Customer Service)
Electronic Check Payments (E-check)
6. E-check Payments. Will you accept E-check payments? (Processed through ACH)
Yes
No (Skip to Question # 14)
If you selected ‘Yes’ to accept E-Check Payments in question 6 above, NACHA requires that you
employ commercially reasonable fraudulent transaction detection systems in order to minimize the
potential for fraud. For most applications this will require you to authenticate users on your site and
pass a ‘shared secret’ to the E-Payment Service application so that we can re-authenticate users on
our site. The ‘shared secret’ for authentication purposes is titled ‘Payer ID’ in this document.
7. Payer ID. Will Payer ID be required for all products? If you selected only ‘IVR’ in question 5
above, skip to Question # 8.
Yes (Default)
No – I will be utilizing the pre-registration file
No (You must provide documentation to U.S. Bank describing how you are meeting NACHA
authentication requirements if you will not be requiring Payer ID for all products)
8. Scheduled Payment Date. Which date will the Payer select as their Scheduled Payment Date
when submitting a payment?
Payment Effective Date. This date is based on the e-check cutoff time and cannot be less than
the next business day.
Biller Business Date. This date is based on the biller business date cutoff time and cannot be
less than the current business day.
9. E-Check Cutoff Time. Specify a cutoff time for E-Check payments. The daily cutoff time for ECheck payments is 6:00 pm ET unless an alternate time is specified. Cutoffs later than 6:00 ET will
have their settlement delayed by one business day.
Default cutoff time (6:00 PM ET)
:00
am/
pm Eastern Time (Must be between 2 AM EST and 6 PM EST)
10. Biller Business Date Cutoff Time. If you selected ‘Biller Business Date’ in Question # 8 above,
specify the cutoff time when the Biller Business Date will advance. Payments submitted after this
time will be assigned the next biller business date.
:00
am/
pm Eastern Time (Must be between 1 PM EST and 12 AM EST. Note:
The 12 AM EST job runs at 11:58 PM)
Doc # PC-001, v4.2
5 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Electronic Check Payments (E-check), cont
11. Biller Business Date Holidays. If there are specific dates that you will not accept transactions,
specify these dates below for the next three years. Use YYYY-MM-DD format.
Date
Description
Date
1
1
2
2
3
3
Description
12. E-Check Return Information:
Standard Set-Up: The standard set-up for the E-Payment Service includes a feed of E-Check return
information into the E-Payment Services application. This information is then available via online
reporting and as part of the remittance file at the end of the day.
Alternate Set-Up: You may alternately choose to receive E-Check Return information through
another method, such as information reporting through U.S. Bank; however, if such a method is
chosen, return information will not update Payer and administrative payment records on the EPayment Service. If you prefer alternate delivery of E-Check Return information, please consult
your Treasury Management Sales Consultant to discuss options.
Standard Return set-up through E-Payment Services
Alternate Return set-up
13. Returned E-Check Payments. Do you want to disable Payers from making E-Check payments
if they are responsible for a specified number of returns due to insufficient funds?
Yes
No
(Skip to Question # 14)
If Yes, enter the number of E-Check returns due to insufficient funds that will result in a Payer
being disabled.
1
2
3
4
Other:
If Yes, enter the time period in which the number of returns specified in above must occur to cause
a Payer to be disabled.
30 days
90 days
180 days
365 days
Other:
Credit Card Payments
14. Credit Card Payments. Will you accept credit card payments?
Yes
No
(Skip to Question # 19)
15. Credit Card Types. Select the credit cards that you will accept.
Visa
Mastercard
Discover
American Express
Doc # PC-001, v4.2
6 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Credit Card Payments, cont
16. Credit Card Authorization Attempt Limit. The credit card authorization attempt limit is a fraud
prevention feature that allows you to limit the number of credit card authorization attempts a Payer
is allowed to initiate within a single session on the web and IVR. (An authorization attempt is
defined as sending a credit card transaction to the merchant processor for authorization)
No Limit
Limit – enter the number of authorization attempts you will allow
17. Address Verification Service (AVS). Do you wish to use AVS response data to accept or reject
credit card payments?
Yes
No
(Skip to Question # 18)
If Yes, select the acceptable response codes for AVS fraud protection. Only transactions approved
by the processor with a response code that you have selected below as ‘acceptable’ will be
processed.
X = Exact AVS match
Y = Address (street) and 5 digit zip code match
A = Address (street) matches, but zip code does not match
W = 9 digit zip code matches, but address (street) does not match
Z = 5 digit zip code matches, but address (street) does not match
N = No match on address (street) or zip code
R = Retry, system unavailable or timed out
C = Street address and postal code in wrong formats
O = No response sent
P = Postal codes match, but street address not verified due to incompatible formats
S = Service not supported by issuer
U = Address information is unavailable (domestic issuer)
B = Street address match, but postal code is in wrong format (international issuer)
D = Street address and postal code match (international issuer)
E = AVS Error
G = Card issued by a non-US issuer that does not participate in the AVS system
I = Address information not verified by international issuer
18. Card Verification Data (CVD). Do you wish to use CVD response data to accept or reject credit
card payments?
Yes
No
(Skip to Question # 19)
If Yes, select the acceptable response codes for CVD fraud protection. Only transactions
approved by the processor with a response code that you have selected below as ‘acceptable’ will
be processed.
M = CVD match
N = CVD does not match
P = CVD not processed
S = Issuer indicates that CVD data should be present on the card, but the merchant has
indicated that the CVD data is not present on the card
U = Issuer has not certified for CVD or Issuer has not provided Visa with the encryption keys
Doc # PC-001, v4.2
7 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Convenience Fees
A convenience fee is an additional charge you may add to the transaction for the convenience of
making the payment. Convenience fees defined for credit card payments are subject to the card
association policies.
19. Convenience Fees. Do you wish to charge a convenience fee for processing a payment?
Yes
No (Skip to Question # 27)
20. Convenience Fee Settlement. Will you be collecting the convenience fee or will U.S. Bank be
collecting the fee on your behalf?
Biller
U.S. Bank
21. E-Check Convenience Fee Processing. Will you process e-check payments as one or two
transactions?
One Transaction
Two Transactions
N/A
22. Convenience Fee Refunds. When you refund a payment, do you wish to refund the convenience
fee?
E-Check
Payments
Credit Card
Payments
Always refund the convenience fee
Give the Administrative User initiating the refund the option
Never refund the convenience fee
23. Select the convenience fee structure you want to apply to these payments.
Flat Fee (Go to Question # 24)
Percentage Fee (Skip to Question # 25)
Tiered Fee (Skip to Question # 26)
24. Flat Convenience Fees for One-Time Payments
One-Time Payments
Web
IVR
Recurring Payments
Admin
Web
Admin
N/A
N/A
E-check
Credit Card
Doc # PC-001, v4.2
8 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Convenience Fees, cont
25. Percentage Convenience Fees for One-Time Payments
One-Time Payments
Web
IVR
Recurring Payments
Admin
Web
Admin
N/A
N/A
E-check
Credit Card
26. Tiered Convenience Fees
One-Time Payments
Tier
Lower
Upper
(#.# #)
(#.# #)
E-Check Payments
Web
IVR
Admin
Recurring Payments
Credit Card Payments
Web
IVR
Admin
E-Check Payments
Web
Admin
1
2
3
4
5
6
IVR
If you did not select ‘IVR’ in Question # 5 above, Skip to Question 36. Please note that the PreRegistration file is required if you have selected IVR.
27. Phone Number. Enter the 10-digit phone number that the Payer will call to access the EPayment Service IVR payment system. If you have a number you wish to use, enter it below.
Otherwise, this field will be completed by the U.S. Bank Implementation Specialist.
28. Biller Description. Enter a description that will be read to the Payer at the beginning of the
call. This field may be a maximum of 128 characters. This prompt will be read to the caller as
‘Welcome to the <Biller Description> Payment System.’
29. User ID Label. Provide a description, up to 128 characters, to be read to the caller to identify
the information they should enter for their User ID. This should describe the value sent as the User
ID in the pre-registration file. This prompt will be read to the caller as ‘Enter <User ID Label>.’
Doc # PC-001, v4.2
9 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
IVR, cont
30. Password Label. Provide a description, up to 128 characters, to be read to the caller to identify
the information they should enter for their password. This should describe the value sent as the
password in the pre-registration file. This prompt will be read to the caller as ‘Enter <Password
Label>.’
31. IVR Authorized Products. In the pre-registration file, you can define the Products (Section 5) for
which Payers can initiate payments. Do you wish to restrict Payers to initiating payments for which
they are authorized?
Yes
No
32. IVR Call Error Handling. If an error occurs while handling a call, what action would you like the
system to take;
Read ‘Exit Message’ to the Payer (Thank you for calling [Biller Description – question 28 above].
Please call customer service at [Customer Service Phone Number – question 83 below] if you have
any questions.)
Transfer the call to your Customer Service center
Transfer the call to the US Bank Customer Care Center
33. IVR Call Error Handling. If you choose to have the call transferred to your customer service
center in question 32 above, enter the 10-digit phone number to transfer the call to.
34. Product Prompt. Choose the method in which Payers will select the product for which they wish
to initiate a payment.
The Payer will enter a numerical product code (Skip to Question # 35)
A list of descriptions will be read to the Payer for selection (Skip to Question # 36)
35. Product Code Description. If you choose ‘The Payer will enter a numerical product code’ in
Question # 34 above, enter a Product Code Description below, up to 128 characters. This prompt
will be read to the caller as ‘Enter <Product Code Description>.’
Miscellaneous
36. Co-Branding. Do you wish to employ the US Bank logo on the E-Payment Services site? (See
Attachment A for the location and size of the US Bank co-brand)
Yes
No
37. Products. Enter the number of products you will define at this time. (You will need to complete
a Section 5 & Section 6 for each product you wish to define)
1
Doc # PC-001, v4.2
10 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Payer Registration
38. Register Users. Will you allow registered Payers on the web, either provided through the preregistration file or through Payer self-registration?
Self-Registration
Pre-Registration File
Both
None
39. Unregistered Users. Will you allow Payers to make payments without registering on the E-Payment
Service site? (Select No if using IVR or a Pre-Registration File)
Yes
No
40. Change Password. If you are providing a Pre-Registration File, will you allow Payers to change
their password on the E-Payment Service site?
Allow Change Password
Allow Change Password & Force Change Password on First Visit
No
Real-Time Transmissions
41. Real-time Payment Confirmation. Do you want to receive real-time payment confirmations for
payments that are initiated, edited, or canceled for any of the products you will define?
Yes
No
42. Real-time Eligibility Lookup. This IVR only feature allows you to manage Payer eligibility in realtime. Do you want to utilize the real-time eligibility lookup for any of the products you will define?
Yes
No
FTP File Transfers
There are four types of files that can be transmitted via FTP

Remittance File – a daily transmission (Monday through Friday, excluding Federal and Custom
Holidays) of payments processed for the previous day(s).

Payment Account File – a daily transmission (Monday through Friday, excluding Federal and
Custom Holidays) that provides you with information regarding payment accounts changed in the EPayment Service by Payers, admins, or NOC’s.

Pre-Registration File – allows you to pre-register your users in order to ease their use of the
system. This file is required if you select IVR, Auto-Login, or Authorized Products.

Pre-Registration Response File –this file is sent each time a pre-registration file is processed. It
includes any records that were not processed along with the appropriate error codes.
Doc # PC-001, v4.2
11 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
FTP File Transfers
Remittance File
Payment Account File
Standard or Custom
43.
Standard
Host IP Address
44.
.
User ID
45.
55.
Password
46.
56.
Transfer Type
47.
PGP Encryption
48.
Public Key
49.
57.
PGP Key User ID
50.
58.
Remote File Name
51.
File Format
52.
Commands
53.
.
Custom
.
54.
ASCII
Yes
N/A
No (Skip to # 51)
Yes
Default
Other
CSV
XML
59.
Both
60.
Other
CSV
XML
Both
.
.
.
Pre-Registration Response File
User ID
63.
72.
Password
64.
73.
Transfer Type
65.
PGP Encryption
66.
Public Key
67.
76.
PGP Key User ID
68.
77.
Remote File Name
69.
Doc # PC-001, v4.2
Default
61.
62.
71.
ASCII
Yes
Default
Binary
74.
No (Skip to # 69)
75.
Other
78.
CSV
70.
.
Binary
Host IP Address
Commands
.
Binary
Pre-Registration File
File Format
.
.
.
.
ASCII
Yes
Default
Binary
No (Skip to # 78)
Other
CSV
79.
12 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
FTP File Transfers, cont
FTP File Transfer Descriptions

Standard or Custom – the daily remittance file can be provided in the standard file layout or a
custom file layout. See your U.S Bank Treasury Management Consultant for more details regarding
a custom file layout.

Host IP Address – the remote server IP address where you would like the file delivered. This must
be the actual IP, not a URL.

User ID – the User ID that will be used to access the FTP Server, up to 23 characters. This ID must
have already been established on the FTP Server.

Password – the corresponding password for the User ID entered in c above, up to 16 characters.

Transfer Type – the transfer type for this transmission

PGP Encryption – do you want U.S. to encrypt the file using PGP

PGP Public Key – the PGP Public Key for encryption

PGP Key User ID – the PGP Key User ID for encryption

Remote File Name – specify the name you want on the file. If you choose a name other than the
default, it must be static and no more than 60 characters. The Default File Names are as follows;

Remittance File: Biller Group Abbreviation_Biller Abbreviation_YYYY_MM_DD

Payment Account File:
Biller Group Abbreviation_Biller Abbreviation_Updated_Payment_Accounts_YYYY_MM_DD

Pre-Registration File: Biller Group Abbreviation_Biller Abbreviation_Pre_Reg.csv

Pre-Registration Response File:
Biller Group Abbreviation_Biller Abbreviation_Pre_Reg_Resp.csv

File Format – the format of the file

Commands – if you would like the file placed in a specific directory, specify the commands here.
Authorized Products
80. Authorized Products on the Web. Do you want to allow the Payer to select the product they wish to
pay for on the E-Payment Service Site? (NOTE: This feature requires the use of the pre-registration file)
Yes
No (Skip to Question # 82)
81. Authorized Products Web Screen Label. If you selected ‘Yes’ to Question # 80, enter a Product
Code Description, up to 40 characters long. This will display to the user as ‘Please select the
<Authorized Products Screen Label> you wish to pay.
Graphics
82. Banner: Provide a customized graphic containing the banner to be displayed at the top of all pages
(to the right of the Biller Group logo). If this is a photographic image, it should be in JPEG format;
otherwise, it should be in GIF format. This graphic must be 600 pixels wide by 70 pixels high. (See
Attachment A for location of the banner)
File Name: ########.GIF ################
Doc # PC-001, v4.2
13 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 4 – Biller Setup (to be completed by the Technical Contact)
Customer Service
83. Customer Service Phone Number. Enter your ten-digit customer service number. This number will
be displayed when a Payer clicks the Customer Service link for assistance with a payment question, and
will be included in payment confirmation emails. (See Attachment B for a sample email confirmation)
###-###-####
84. Customer Service Text: Enter text that defines the hours your telephone customer service is
available. You may choose to include an email address to allow customers to contact you. You may
enter up to 256 characters, including spaces and punctuation.
85. Email Confirmation Address. Enter the email address from which you want all system-generated
email confirmations to come. You may wish to provide an address such as noreply@yourdomain.com.
Please note that some Spam filters reject emails sent from a “noreply” address (See Attachment B for
the location of this address)
##########@###########.edu
Return Linking
86. Payment Inquiry Default Return URL: You may allow your users to link to the payment system for
purposes other than making a payment, i.e., to manage saved accounts, check payment history, or
manage pending payments. Enter the complete URL (including http:// or https://) to which the user
should be directed when leaving the payment system. You may enter up to 256 characters.
############ SMS Main Menu URL ############
Section 5 – Product Setup (to be completed by the Technical Contact)
A “Product” is the final application-level hierarchy under Biller. If you would like to setup more than one
product, you must complete an additional Section 5 (Product Setup) and Section 6 (Product Parameter)
for each product. [Biller Group > Biller > Product]
1. Payment Channels. If you selected more than one payment channel in Section 4 above, please select
the payment channels you wish to offer for this product.
Web
Live Agent (through your Customer Service)
IVR
Live Agent (through U.S. Bank Customer Service)
2. Product Description. Provide a complete description of this product, up to 48 characters long. This
description appears in payment confirmation emails and onscreen when payment details are displayed.
(See Attachment B for a sample email confirmation)
3. Report Label. Provide a name for this product, up to 32 characters long. This name is used to identify
this product in reports.
Doc # PC-001, v4.2
14 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 5 – Product Setup (to be completed by the Technical Contact)
Payment Amount
The E-Payment Service provides you the option to pass an amount due to the application and define
associated business rules
Amount Due
4.
Always Pass
Never Pass (skip to Question # 7)
Over Payments
5.
Yes
No
Partial Payments
6.
Yes
No
Min / Max Payment Amount
7. Minimum
Transfer Mode
9.
8. Maximum
Session Transfer
Pre-Registration File
Amount Due Descriptions

Amount Due – will you pass an amount due to the E-Payment Service

Over Payments – will you allow the Payer to pay more than the amount due for this product

Partial Payments - will you allow the Payer to pay less than the amount due for this product

Minimum / Maximum Payment Amount – the minimum and maximum payment amount you will
accept for this product (Note: You must enter $0 if you accept Visa payments)

Transfer Mode – will you pass the amount due in the session transfer or the pre-registration file
Due Date
The E-Payment Service provides you the option to pass a due date to the application and define
associated business rules
Due Date
10.
Late Payments
11.
Payment Warehousing
12. 0
Transfer Mode
13.
Always Pass
Yes
Never Pass (skip to Question # 12)
No
Session Transfer
Pre-Registration File
Due Date Descriptions

Due Date – will you pass a due date to the E-Payment Service

Late Payments – will you allow the Payer to select a payment date after the due date

Payment Warehousing – will you allow the Payer to schedule the payment for a future date. If
yes, enter the number of days in the future you will allow a Payer to schedule a payment, up to 365
days. If no, enter 0.

Transfer Mode – will you pass the due date in the session transfer or the pre-registration file
Doc # PC-001, v4.2
15 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 5 – Product Setup (to be completed by the Technical Contact)
Real-Time Messages
There are two types of real-time communication that can be transmitted by the E-Payment Service

Real-Time Payment Confirmation– a real-time message sent to the Biller via http(s) each time
a one-time or recurring payment is initiated, edited, cancelled, processed, declined, refunded, or
stopped.

Real-Time Eligibility Lookup – a real-time request sent to the Biller via http(s) each time a
Payer logs into the IVR and selects to make a payment for this product
Real-Time Payment Confirmation
Real-Time Eligibility Lookup
Destination IP Address
14.
19.
Destination URL
15.
20.
Message Format
16.
Client User ID
17.
21.
Client Password
18.
22.
XML
User Password Required
URL Encoded
N/A
XML
23.
Yes
No
Real-Time Communication Description

Destination IP Address – enter the destination IP Address where the real-time messages will be
sent for this product

Destination URL – enter the destination URL where the real-time messages will be sent for this
product

Message Format – the real-time payment confirmation message is available in two formats, XML
and URL encoded. Select one.

Client User ID – you may define two fields, User ID and Password, to be sent in the real-time
communication to allow you to confirm the source of the message.

Client Password – if you choose to define a Client User ID to be sent in the real-time
communication you must also define a Client Password.

User Password Required – you have the option to receive the user’s password in the real-time
eligibility lookup in order to validate the identity of the user.
Miscellaneous
24. Payment Frequencies. Select the payment frequencies you will make available to Payers initiating
payments for this product.
Single Payments Only
Recurring Payments Only
Both
25. Convenience Fee for Recurring E-check Payments. Do you wish to charge Payers using e-checks a
convenience fee for initiating Recurring Payments for this Product?
Yes
No
Doc # PC-001, v4.2
N/A
16 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 5 – Product (to be completed by the Technical Contact)
Miscellaneous
26. ACH File Label. Enter a label to be used in the ACH file for this product. You may enter up to 10
characters, including spaces and punctuation.
##########
27. Convenience Fee ACH File Label. If you selected to process e-check payments as two transactions in
Section 4, enter the label to be used in the ACH file for the convenience fee transaction associated with
the payment.
Default (conv fee)
Other
(max 10 characters)
N/A
28. ACH Addenda. Will this product require an ACH Addenda record?
Yes
No
29. Screen Label. Provide a name for this product, up to 32 characters long. This name appears
wherever a label is needed to identify this value when it appears onscreen in the payment system. (See
Attachment A for the location of the screen label)
##########################
30. Payer ID Screen Label. Provide a label that will be used to identify the Payer ID when it appears
onscreen in the payment system. This label can be up to 32 characters long. (If you are utilizing a preregistration file, skip to question 31)
STUDENT ID
31. Payment Default Return URL: Enter the complete URL (including http:// or https://) of the page to
which the user should be directed when leaving the payment system after making a payment. You may
enter up to 256 characters, including spaces and punctuation.
############ SMS Main Menu URL ############
32. Email Confirmation Inquiry URL. The Email Confirmation Inquiry URL will be included in all payment
confirmation emails generated for this Product. This is a URL on your site that Payers will access in order
to link to the E-Payment Services in order to manage accounts, view pending payments, and view
payment history. (See Attachment B for an example)
Doc # PC-001, v4.2
17 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 5 – Product (to be completed by the Technical Contact)
33. Custom Text on Payer Site Confirmation Screen. You may define text up to 750 characters to be
displayed to the Payer on the Confirmation Screen after completion of a successful payment on the web.
34. Custom Text on Admin Site Confirmation Screen. You may define text up to 750 characters to be
displayed to the admin user on the Confirmation Screen after completion of a successful payment on the
admin site.
35. IVR Product Description. Enter a description for this product that will be read to the Payer when
listing the products on the IVR.
36. Auto-Login. Do you wish to utilize the auto-login feature for this product? This feature allows you to
pass a Payer’s username and password in the session transfer and log the Payer into the E-payment
service, thus providing a more seamless experience to your Payers.
Yes (Requires the use of the pre-registration file and encrypted session transfer)
No
You may define additional values that you will pass in the session transfer or collect from the user on the
payment screen for this product. These additional values are called product parameters. A product
parameter can be used for any of the following purposes:

To pass, in the session transfer, a value that can be displayed on the Make a Payment page.

To display an input field on the Make a Payment page and collect a value entered or selected by
the Payer.

To pass or collect a value to be included in the Remittance file.
Standard pricing includes up to 10 product parameters. If you would like to set up more than 10
parameters, please contact your sales representative for pricing. You are not required to have any
product parameters.
37. Number of Product Parameters. How many parameters will you define for this product? (You will
define each parameter in Section 6 that follows)
Doc # PC-001, v4.2
18 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
Descriptions / Labels
NOTE: The Product parameters must be entered on this page in the order you wish to have them displayed to a
Payer or admin.
Description
Parameter # 1
StudentID
Parameter # 2
StudentName (optional)
Parameter # 3
orderNumber (optional)
Parameter # 4
YRQ (optional)
IVR Description
Parameter # 5
Parameter # 6
Parameter # 7
Parameter # 8
Parameter # 9
Parameter # 10

Description: Enter a description for this value. This is for internal processing only, and does not
appear anywhere in the system. The description may consist of 1 to 48 alphanumeric characters.

IVR Description: If ‘IVR’ was not selected for this product in question 1 of Section 5, skip this
question. Provide a description for this parameter that will be read to the Payer when prompting
them for this parameter on the IVR. The description may consist of 1 to 128 alphanumeric
characters. This prompt will be read to the caller as ‘Please enter <IVR Description>.’
Doc # PC-001, v4.2
19 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
Descriptions / Labels, cont
Parameter Type
Parameter # 1
Pass
Collect
Constant
Parameter # 2
Pass
Collect
Constant
Parameter # 3
Pass
Collect
Parameter # 4
Pass
Parameter # 5
Web Screen Label
Remittance
File
Real-Time
Payment
Confirmation
Yes
No
Yes
No
(Optional)
Yes
No
Yes
No
Constant
(Optional)
Yes
No
Yes
No
Collect
Constant
(Optional)
Yes
No
Yes
No
Pass
Collect
Constant
Yes
No
Yes
No
Parameter # 6
Pass
Collect
Constant
Yes
No
Yes
No
Parameter # 7
Pass
Collect
Constant
Yes
No
Yes
No
Parameter # 8
Pass
Collect
Constant
Yes
No
Yes
No
Parameter # 9
Pass
Collect
Constant
Yes
No
Yes
No
Parameter # 10
Pass
Collect
Constant
Yes
No
Yes
No

Parameter Type: Product parameters can be passed to the E-Payment Service in the session
transfer or pre-registration file (pass), collected from the Payer during the payment process
through an entry box, IVR prompt, or list (collect), or defined as a constant value for all
payments during setup (constant).

Screen Label: Provide a screen label for this parameter that will display on the web site and
admin site when this parameter is referenced. The screen label may consist of 1 to 32
alphanumeric characters. (See Attachment A for a location of the screen label)

Remittance File: Do you want this product parameter to be included in the Remittance file.

Real-Time Payment Confirmation: Do you want this product parameter included in the realtime payment confirmation?
Doc # PC-001, v4.2
20 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
“Passed Value” Product Parameters Only
Complete this table for all parameters that will be passed in the session transfer or the preregistration file.
Always/
Sometimes
Display
(Web)
Display
(IVR)
Numeric
Alphanumeric
Date
Parameter # 1
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Parameter # 2
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format (optional)
Parameter # 3
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format (optional)
Parameter # 4
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format (optional)
Parameter # 5
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format
Parameter # 6
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format
Parameter # 7
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format
Parameter # 8
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format
Parameter # 9
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format
Parameter # 10
Always
Sometimes
Yes
No
Yes
No
Min
Max
Min
Max
Format
Format

Always/Sometimes: If you selected ‘Yes’ to Passed Value (Pass) for this parameter, will you
always pass a value for this parameter or sometimes pass a value for this parameter?

Display (Web): If you selected ‘Yes’ to Passed Value for this parameter, do you want this
parameter displayed on the public and admin web sites?

Display (IVR): If you selected ‘Yes’ to Passed Value for this parameter, do you want this
parameter read on the IVR?

Numeric: If you selected ‘Yes’ to Passed Value for this parameter and this will be a numeric
value, enter the minimum and maximum length here.

Alphanumeric: If you selected ‘Yes’ to Passed Value for this parameter and this will be an
alphanumeric value, enter the minimum and maximum length here.

Date: If you selected ‘Yes’ to Passed Value for this parameter and this will be a date, enter the
format here.
Doc # PC-001, v4.2
21 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
“Constant Value” Product Parameters
Complete this table for all parameters that will be a constant value defined during implementation.
Value
Display (Web)
Display (IVR)
ACH Addenda
Position
ACH Addenda
Parameter # 1
Yes
No
Yes
No
Yes
No
Parameter # 2
Yes
No
Yes
No
Yes
No
Parameter # 3
Yes
No
Yes
No
Yes
No
Parameter # 4
Yes
No
Yes
No
Yes
No
Parameter # 5
Yes
No
Yes
No
Yes
No
Parameter # 6
Yes
No
Yes
No
Yes
No
Parameter # 7
Yes
No
Yes
No
Yes
No
Parameter # 8
Yes
No
Yes
No
Yes
No
Parameter # 9
Yes
No
Yes
No
Yes
No
Parameter # 10
Yes
No
Yes
No
Yes
No

Value: If you selected ‘Yes’ to Constant Value for this parameter, enter a constant value for this
parameter, 1 – 20 alphanumeric characters.

Display (Web): If you selected ‘Yes’ to Constant Value for this parameter, do you want this
parameter displayed on the public and admin web sites?

Display (IVR): If you selected ‘Yes’ to Constant Value for this parameter, do you want this
parameter read on the IVR?

ACH Addenda: If you selected ‘Yes’ to Constant Value for this parameter, does this parameter
need to be included in the ACH Addenda Record?

ACH Addenda Position: If you selected ‘Yes’ to Constant Value for this parameter and ‘Yes’ to
ACH Addenda, enter the position number here.
Doc # PC-001, v4.2
22 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
“Collected Value” Product Parameters
Complete this table for all parameters that will be collected from the Payer during the payment
process.
Required
Numeric
Alphanumeric
Parameter # 1
Yes
No
Min
Max
Min
Max
Parameter # 2
Yes
No
Min
Max
Min
Max
Parameter # 3
Yes
No
Min
Max
Min
Max
Parameter # 4
Yes
No
Min
Max
Min
Max
Parameter # 5
Yes
No
Min
Max
Min
Max
Parameter # 6
Yes
No
Min
Max
Min
Max
Parameter # 7
Yes
No
Min
Max
Min
Max
Parameter # 8
Yes
No
Min
Max
Min
Max
Parameter # 9
Yes
No
Min
Max
Min
Max
Parameter # 10
Yes
No
Min
Max
Min
Max
Date Format
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYMMDD
YYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY
YYQ
YYMM
MM
MMDDYYYY

Required: If you selected ‘Yes’ to Collected Value for this parameter, do you want to require the
Payer to enter a value in order to complete a payment?

Numeric: If you selected ‘Yes’ to Collected Value for this parameter and this will be a numeric
value, enter the minimum and maximum length here.

Alphanumeric: If you selected ‘Yes’ to Collected Value for this parameter and this will be an
alphanumeric value, enter the minimum and maximum length here.

Date Format: If you selected ‘Yes’ to Collected Value for this parameter and this will be a date,
select the format here.
Doc # PC-001, v4.2
23 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
“Collected Value” Product Parameters
Complete this table for all parameters that will be collected from the Payer during the payment
process.
Drop Down
List
Display (Web)
Display (IVR)
ACH Addenda
Parameter # 1
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 2
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 3
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 4
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 5
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 6
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 7
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 8
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 9
Yes
No
Yes
No
Yes
No
Yes
No
Parameter # 10
Yes
No
Yes
No
Yes
No
Yes
No
ACH Addenda
Position

Drop Down (Pre-Defined) List: If you selected ‘Yes’ to Collected Value for this parameter, this
type of collected parameter allows you to present / read a list of values to the Payer during the
payment process and allow them to make a selection. If you select ‘Yes’ for any of the
parameters, make sure to define your list on Page 25.

Display (Web): If you selected ‘Yes’ to Collected Value for this parameter, do you want this
parameter displayed on the public and admin web sites?

Display (IVR): If you selected ‘Yes’ to Collected Value for this parameter, do you want this
parameter read on the IVR?

ACH Addenda: If you selected ‘Yes’ to Collected Value for this parameter, does this parameter
need to be included in the ACH Addenda Record?

ACH Addenda Position: If you selected ‘Yes’ to Collected Value for this parameter and ‘Yes’ to
ACH Addenda, enter the position number here.
Doc # PC-001, v4.2
24 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Section 6 – Product Parameters (to be completed by the Technical Contact)
“Collected Value” Product Parameters
Parameter #
Drop Down (Pre-Defined) Values (Public & Admin)
IVR Voice Description

Parameter #: Enter the parameter # for which you want to defined pre-defined values

Drop Down (Pre-Defined) Values (Public & Admin): These values will displayed to the
Payer in a dropdown list on the public and admin web sites.

Drop Down (Pre-Defined) Values (IVR): These values will read to the Payer as options on
the IVR.
Doc # PC-001, v4.2
25 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Attachment A – Sample Screen
Sec 3, Q 6
Biller Group
Browser Title
Sec 4, Q 4
Biller
Browser Title
Sec 3, Q 2
Logo
150 wide x
70 high
Sec 4, Q 82
Banner
600 wide x 70
high
Sec 5, Q 29
Screen Label
Sec 4, Q 36
Co-branding
Page 20
Web Screen Label
Sec 3, Q 3
Navigation
Background
Doc # PC-001, v4.2
26 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Attachment B – Sample Email Confirmation
Sec 4, Q 85
Email Confirmation
Address
Sec 5, Q 2
Product
Description
Sec 5, Q 33
Sec 3, Q 4
Biller Group
Short Name
Doc # PC-001, v4.2
Sec 4, Q 2
Biller Short
Name
Email Confirmation
Inquiry URL
Sec 4, Q 83
Customer Service
Phone Number
27 of 28
U.S. Bank E-Payment Service
Implementation Questionnaire
Attachment C – Standard Privacy Policy with a link to your Privacy Policy
E-Payment Service Privacy Policy
Your payment is being processed using the U.S. Bank E-Payment Service. As part of this
service, we collect information necessary to complete the transaction and as requested by
[YOUR COMPANY NAME HERE]
Information necessary to process and service the transaction will be provided to [YOUR
COMPANY NAME HERE], whose use of this information is governed by their privacy policy
[URL FOR YOUR COMPANY PRIVACY POLICY HERE]. For information regarding the security
and use of your information by U.S. Bancorp, visit U.S. Bank’s Consumer Online Privacy
Statement.
Attachment D – Standard Privacy Policy
E-Payment Service Privacy Policy
Your payment is being processed using the U.S. Bank E-Payment Service. As part of this
service, we collect information necessary to complete the transaction and as requested by
[YOUR COMPANY NAME HERE]
Information necessary to process and service the transaction will be provided to [YOUR
COMPANY NAME HERE]. For information regarding the security and use of your information
by U.S. Bancorp, visit U.S. Bank’s Consumer Online Privacy Statement.
Doc # PC-001, v4.2
28 of 28