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.
Company Name / ########################################
Company Address / ########################################
Primary
/Secondary*
Questionnaire Contact(s) – Primary contact(s) for questions regarding this QuestionnaireName / ##############
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
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;
- 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
- 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.
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 2. Admin Org ID 3. Admin Org ID
No 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 and complete the remainder of Section 3
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)
- Provide the URL to your privacy statement
- Provide how your company name should appear in the privacy statement
- Provide how your company name should appear in the privacy statement
- File Name:
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 / Description
1 / 1
2 / 2
3 / 3
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)
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 E-Check 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)
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 / Description
1 / 1
2 / 2
3 / 3
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 E-Payment 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
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
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
- E-Check Convenience Fee Processing. Will you process e-check payments as one or two transactions?
22. Convenience Fee Refunds. When you refund a payment, do you wish to refund the convenience fee?
E-Check Credit Card
Payments 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 / Recurring Payments
Web / IVR / Admin / Web / Admin
E-check
Credit Card / N/A / N/A
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 / Recurring Payments
Web / IVR / Admin / Web / Admin
E-check
Credit Card / N/A / N/A
26. Tiered Convenience Fees
One-Time Payments / Recurring Payments
Lower / Upper / E-Check Payments / Credit Card Payments / E-Check Payments
Tier / (#.# #) / (#.# #) / Web / IVR / Admin / Web / IVR / Admin / 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 Pre-Registration 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 E-Payment 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>.’
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.)