Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

After an application is in production by 2JFP7wu

VIEWS: 5 PAGES: 7

									E-Payment Services - Co-Hosted Developer's Guide

Introduction
This document is intended to provide agency application developers with a detailed understanding of E-
Payment transaction processing and the steps required to implement E-Payment services for their web
application. A high level technical overview can be found in the Technical Overview document.

Note: For Internal E-Payment Applications need to be self signed cert.
     For External E-Payment Applications need to be veri-sign cert.

Figure 1 show the steps involved in E-Payment transaction processing. These steps are later described in
more detail.

    (1) Redirect to proxy with request parameters                                             (2) Forward redirect with request parameters



            (4) Receive RTPC request parameters          State E-Payment                 (3b) Return RTPC with request parameters
                                                           Proxy Server

                           (5) Send response                                                   (6) Send response




                                                            (3a) Send customer
    State Web                                                  to Return URL
                                                                                                                           U. S. Bank
    Application


                                            Receive remittance file either through automated FTP
                                      from U. S. Bank or by manually retrieving from U. S. Bank website
                                                (not part of the real-time transaction process)




                                               Figure 1: E-Payment transaction processing



Redirect to US Bank (Session Transfer)
Agency web applications that are using E-Payment services need to send a redirect to US Bank to perform
transaction processing. This redirect involves posting a form to the E-Payment proxy server that includes
several parameters. The proxy server then forwards the request to US Bank. The redirect includes steps 1
and 2 in Figure 2.




                                                                   1 of 7
      (1) Redirect to proxy with request parameters                                             (2) Forward redirect with request parameters



              (4) Receive RTPC request parameters          State E-Payment                 (3b) Return RTPC with request parameters
                                                             Proxy Server

                             (5) Send response                                                   (6) Send response




                                                              (3a) Send customer
      State Web                                                  to Return URL
                                                                                                                             U. S. Bank
      Application


                                              Receive remittance file either through automated FTP
                                        from U. S. Bank or by manually retrieving from U. S. Bank website
                                                  (not part of the real-time transaction process)




                                                         Figure 2: Redirect to US Bank



Under the standard contract pricing, US Bank limits an agency web application to a maximum of 10
parameters that can be submitted in the redirect (additional parameters may be submitted at an additional
charge). The State has reserved one of the 10 parameters for a revenue accounting code. Also, the
following parameters are required by US Bank but are not counted as part of the 10 agency-specified
parameters:

     billerId
     billerGroupId
     productCode (The product code is a six-character value. The first three characters represent the
      agency number and the last three characters represent the application abbreviation.)

Figure 3 below shows a sample form that can by used by agencies as a starting point for their application’s
redirect to US Bank. The agency is responsible for modifying this form appropriately for their application.

    <form name="epayForm" action=”https://paytest.wisconsin.gov/epay/enter” method="post"

    // Required parameters. Replace with values for your application
    <input type="hidden" name="productCode" value="370RVR" />
    <input type="hidden" name="RevenueCode" value="ZZBT" />
    <input type="hidden" name="billerId" value="DNR" />
    <input type="hidden" name="billerGroupId" value="WIS" />
    <input type="hidden" name="amountDue" value="17.5" />

    // Optional parameters specific to an agency web application
    <input type="hidden" name="CleanWaterDonation" value="0">
    <input type="hidden" name="ConvenienceFee" value="1">
    <input type="hidden" name="aVehicleType" value="B" />
    <input type="hidden" name="bRegistrationNumber" value="WS1000CP" />

    <input type="submit" value="Make Payment">

    </form>
                                                                       2 of 7
                                              Figure 3: Sample redirect form

Note: Our E-Payment service is expecting a submit button without the ‘name’ attribute, which would cause it
to fail.

Note: You can determine the ordering of parameters on US Bank’s payment pages by alphabetically
ordering the parameter names. For example, the parameters in Figure 4 will determine the order of the
fields under the Payment Details section in Figure 5.


    <input   type="hidden"   name="aGamingType" value="Gaming Type">
    <input   type="hidden"   name="bGamingCategory" value="Gaming Category">
    <input   type="hidden"   name="cLicenseeName" value="Name">
    <input   type="hidden"   name="dTransactionNumber" value="Trans No">


                             Figure 4: Sample parameters for ordering fields on US Bank screen




                         Figure 5: Sample screen showing screen fields ordered by parameter names



Real-Time Payment Confirmation (RTPC) from US Bank
If agencies wish to receive real-time payment confirmation for successful payment events, they must
provide the E-Payment implementation lead with a RTPC URL for their web application. The RTPC involves
the following steps, which are also highlighted in steps 3, 4, 5, and 6 in Figure 6.

     US Bank sends a request to the E-Payment proxy server containing several request parameters for a
      transaction. The request parameters include a unique confirmation ID as well as the original parameters
      sent from the agency application to US Bank. Note: some of the parameter names are different on the
      RTPC compared to the redirect to US Bank.
     The E-Payment proxy server then forwards this request to the RTPC URL provided by the agency.

                                                          3 of 7
   The RTPC URL for the agency web application must return a response to the E-Payment proxy server
    to communicate that the RTPC was received. See RTPC URL below for more details.
   The E-Payment proxy server returns a response to US Bank to communicate that the RTPC processing
    completed.

     (1) Redirect to proxy with request parameters                                             (2) Forward redirect with request parameters



             (4) Receive RTPC request parameters          State E-Payment                 (3b) Return RTPC with request parameters
                                                            Proxy Server

                            (5) Send response                                                   (6) Send response




                                                             (3a) Send customer
     State Web                                                  to Return URL
                                                                                                                            U. S. Bank
     Application


                                             Receive remittance file either through automated FTP
                                       from U. S. Bank or by manually retrieving from U. S. Bank website
                                                 (not part of the real-time transaction process)




                                                     Figure 6: RTPC from US Bank

RTPC URL
Agencies need to provide the E-Payment implementation lead with their RTPC values for both test and
production environments. The RTPC page for agency web applications must trap any errors that occur
when processing the transaction. The RTPC page can consist of some logic for processing a transaction
and must return a response consisting of the text string ‘OK’ in a single line for successful processing (refer
to US Bank specs for more details).

The sample form in Figure 7 can be used by agencies as a starting point for testing their RTPC page. The
form contains the request parameters that are returned from US Bank. This allows agencies to perform their
own testing before the integration testing with U. S Bank. This form is intended for testing purposes only
and is not a part of E-Payment transaction processing.




                                                                   4 of 7
 <form action="https://paytest.wisconsin.gov/epay/confirm" method="post">

 // Required parameters. Replace with values for your application
 <input     type="hidden"            name="BillerProductCode" value="370RVR">
 <input     type="hidden"            name="amountDue" value="0.50">
 <input     type="hidden"            name="ConvenienceFee" value="0.25">
 <input     type="hidden"            name="RevenueCode" value="ABC">
 <input     type="hidden"            name="billerId" value="DNR">
 <input     type="hidden"            name="billerGroupId" value="WIS">
 <input     type="hidden"            name="ConfirmationId" value="73537">

 // Optional parameters specific to an agency web application
 <input type="hidden" name="aVehicleType" value="Boat">
 <input type="hidden" name="CleanWaterDonation" value="1.00">
 <input type="hidden" name="bRegistrationNumber" value="12345">

 <input type="submit" value="Make Payment">
 </form>



                                                    Figure 7: Sample RTPC test form



Return from US Bank to web application
US Bank then sends a request to the Return URL provided by the agency. US Bank does not wait for the
proxy to return an RTPC response before sending the customer to the Return URL. The Return URL is
shown as step 3b in Figure 8.



    (1) Redirect to proxy with request parameters                                             (2) Forward redirect with request parameters



            (4) Receive RTPC request parameters          State E-Payment                 (3b) Return RTPC with request parameters
                                                           Proxy Server

                           (5) Send response                                                   (6) Send response




                                                             (3a) Send customer
    State Web                                                   to Return URL
                                                                                                                           U. S. Bank
    Application


                                            Receive remittance file either through automated FTP
                                      from U. S. Bank or by manually retrieving from U. S. Bank website
                                                (not part of the real-time transaction process)


                                            Figure 8: Exit from US Bank to web application




                                                                 5 of 7
Remittance file
The remittance file contains transaction information for an agency web application and can be retrieved in
two different ways. Either US Bank can send the remittance file to the State E-Payment FTP server on a
daily basis or the agency can retrieve the file manually from the US Bank.

Receipt of the remittance file is highlighted in Figure 9. The file is available in both XML and CSV formats.


      (1) Redirect to proxy with request parameters                                              (2) Forward redirect with request parameters



              (4) Receive RTPC request parameters            State E-Payment                 (3b) Return RTPC with request parameters
                                                               Proxy Server

                             (5) Send response                                                    (6) Send response




                                                                (3a) Send customer
      State Web                                                    to Return URL
                                                                                                                              U. S. Bank
      Application


                                              Receive remittance file either through automated FTP
                                        from U. S. Bank or by manually retrieving from U. S. Bank website
                                                  (not part of the real-time transaction process)


                                                      Figure 9: Receipt of remittance file



E-Payment Servers
The following servers are used for E-Payment services. Agency web applications need to be able to send
requests to and receive requests from the test and production servers.

State FTP E-Payment Server for Remittance File (there is no test server)
       Server Name: ftp.doa.state.wi.us
       IP Address: 165.189.88.180

Production Environment
IP Addresses: 165.189.80.242
Redirect URL: https://payment.wisconsin.gov/epay/enter
RTPC URL: https://payment.wisconsin.gov/epay/confirm
RTEL URL: https://payment.wisconsin.gov/epay/rtelReq

Test Environment
IP Address: 165.189.80.66
Redirect URL: https://paytest.wisconsin.gov/epay/enter
RTPC URL: https://paytest.wisconsin.gov/epay/confirm (NOTE: only for testing purposes prior to US Bank
integration testing)
RTEL URL: https://paytest.wisconsin.gov/epay/rtelReq

Important: Although the US Bank documentation directs you to point the session transfer directly to
US Bank, you must direct it to the one of the redirect url’s above based on the environment you are
using (test or production). All session transfers and RTPC’s must be routed through the DET proxy.
                                                                     6 of 7
Note: When an agency initially sets up an application, US Bank will configure the application in their
production environment and disable credit card processing for testing purposes. Once the application is
live, US Bank enables credit card processing. After an application is in production, US Bank creates a “test
application” which is a clone of the production application with different biller information and credit card
processing turned off.

The following parameters can be used for testing credit card payment in the “test environment” (not the
production environment):

   Credit card type: VISA
   Credit card number: 4111111111111111
   Expiration date: Any date
   Confirmation number: Any code




                                                    7 of 7

								
To top