Citizen Self Service – Online Payments Guide

Module: Productivity Products/Tools Topic: MSS Munis Self Service Citizen Self Service – Online Payments Guide

Objective This document provides step-by-step instructions on how to add payment services for Munis Self Services. In addition, it provides some information about each available payment-processing vendor.

Overview of Web Payment Process When a citizen attempts a payment, MSS logs the attempt in the pending web payment table in your Munis database. The citizen is redirected to the payment vendor’s website where they enter their contact and payment info. If the payment is authorized by the payment processor vendor, a “postback” is sent to MSS and the pending web payment table record is updated with the authorization code. The process of importing web payments is not a true import of an external file. It actually involves taking payments from the pending web payment table and creating a payment batch. The usual method of doing this is to obtain a report of the previous day’s activity (or previous three days’ activity if it is Monday) from the payment processing vendor. Some vendors will email you the report and some require you to create your own reports through their websites. Once you have the report in hand, you simply run the Munis web payment import program for the same date range and it will show you all payments that have an authorization code populated. It is imperative that the number of payments and dollar amounts match between the Munis web payment import program and the payment processing vendor’s report. In the event of a discrepancy, the payment processing vendor’s report must be considered the correct source and Munis needs to be manipulated to match. There are many different points of failure when making a payment (client PC, client internet connection, MSS server, Munis server, networking hardware, payment vendor’s server, etc…) and sometimes a payment is approved but the authorization code doesn’t make it back to your Munis database. In that event, there is a Maintain Payments button that lets you view ALL web payment attempts that have been made. You can identify the missing payment and manually enter in the authorization code (or anything else - your initials, the date, etc...) to make your Munis import match up with the vendor’s report. As long as the authorization code field is not blank, the payment will get picked up when you re-run the web payment import. Once a payment has been imported into Munis, the record is marked and can never be imported again, so there is no danger in running the web payment import for the same time frame over and over again.

Citizen Self Service – Online Payments Guide

Payment Gateway Options Munis Self Service can interface with several different payment gateways. Before you can accept web payments through Citizen Self Service, you must establish a relationship with one of the following payment gateway vendors:

• Official Payments Corporation (OPAY or OPC) • JP Morgan Chase - Pay Connexion • Govolution - Velocity Payment System • Forte (formerly Federal Payments) - Secure Web Pay Checkout • ETS – EMoney Hosted ECOM • VPS – Value Payment Systems • Paymentus • UniBank • Authorize.Net • Xpress-Pay • Elavon Converge • OpenEdge • BridgePay • PayPal Payflow Pro • InforME Redirect

The details for each vendor are listed later in this document. It is possible to use one vendor for Credit Cards and another vendor for eChecks. You could also configure different payment vendors for different bill categories.

SSL Certificates If you are hosting MSS on your own server and want to take payments through it, you must install an SSL Certificate to encrypt traffic between the browser and the server.


Multiple Payment Types When using the same vendor for both eChecks and Credit Cards, it is important to know whether or not the vendor presents the citizen with the payment type choice. If the payment processor lets the citizen choose between Credit Card/eCheck, then you do not want MSS to ask the same question. When a vendor supports both payment types and presents the option, you should only check the “Allow credit card selection” box in MSSHosting.

Notes for whether or not you should check both boxes will be included in the MSS Hosting Setup section for each vendor.


Shopping Cart There is a fairly steep requirement to be able to use the shopping cart feature. As can be seen on the Payment Administration screen (below), you need to define a single Credit Card and a single eCheck gateway through which payments for all bill types will be funneled. Many of the payment gateway vendors will need to assign a different product/URL/account/etc… for each bill type, and this is usually necessary because the money needs to end up in different bank accounts for Real Estate payments vs Utility Billing payments, for example. If multiple payment gateway definitions need to be defined in MSSHosting for either Credit Cards or eChecks based on bill type, then the Shopping Cart cannot be used.


General MSSHosting Setup Use the following steps to add a payment service for Citizen Self Service. If Tyler hosts your MSS, these steps will be done for you.

1. Open the MSS Hosting website Example: http://example.com/MSSHosting

2. Enter MSS Admin credentials to login, if prompted

3. Click Edit next to the appropriate client

4. Click Client Configuration

5. Click Payment Services

http://example.com/MSSHosting


6. Click Add New

7. Select the desired payment gateway from Type drop-down list:


8. Enter Name and check Allow check payment and/or Allow credit card.

In some situations, you will need to create multiple interfaces. In those cases, it is recommended that you clearly differentiate your Payment Service Name with something like:

[Vendor] [Credit Card or eCheck] [Bill Type (in more than one)] [Live/Train/Test]

Examples: “OPC Credit Card Real Estate (LIVE)” “PayPal eChecks Motor Vehicle (TRAIN)”

NOTE: For some payment vendors, you will only want to specify one of the “Allow” options even if you’re using it for both. Please see the specific instructions for your payment interface later in this document.

9. Click Continue.

10. Enter the configuration info for the selected vendor. The gateway-specific screens are included

in the separate sections for each payment gateway vendor below.

11. Click Update

12. Now that you have defined your payment gateway(s) in MSS Hosting, you can enable them in MSS Administration by logging into MSS as an administrator. Go to Administration > Citizen Administration > Payment Administration to get started.


Official Payments Corporation (aka OPC or OPAY)

Overview/Requirements

• OPC supports both credit cards and eChecks OPC must provide you with an internet merchant account

• This payment model passes a convenience fee to the citizen to cover transaction costs. • OPC convenience fees can vary by bill type, but they have a Fee Calculator at

http://www.officialpayments.com that you can use to get an approximation. You should get an actual quote from them to be sure, though.

Contact

If you would like to proceed with OPC, please contact the Official Payments Client Services team at [email protected] or (866) 352-5002.

Implementing OPC

Once OPC sales has finished setting you up as an OPC customer, you will be assigned an OPC Implementer. When working with your OPC Implementer, remind them that the MSS-to-OPC interface utilizes OPC’s CoBrand+ product with the following Post-in Parameters: cde-BillNumb-0, cde-BillYear-1, cde-AccoNumb-2, cde-CustID-3 and cde-SessID-4. You also need to tell the OPC Implementer that they will need to set you up to use a back-end postback. If that is not done, the authorization codes will not make it back to MSS. You will need to provide the OPC Implementer with a set of 5 URLs so that they can interact with MSS: Return: https://xxx/citizens/Payments/PaymentAmount.aspx Redirect: https://xxx/citizens/default.aspx Error: https://xxx/citizens/Payments/PaymentError.aspx Postback: https://xxx/citizens/Payments/Confirmation.aspx Test Postback: https://yyy/citizens/Payments/Confirmation.aspx In the URLs above, change “xxx” to the base address of your Live MSS site and “yyy” to the base address of either your Training MSS site or your Test MSS site. OPC can only point to one or the other, so it’s up to you to decide which environment you want to use for testing payments. Please note also that the Postback URLs are just placeholders. You will determine the real Postback URL in the “MSS Hosting Setup” section below and that will over-ride what OPC is using for the URL.

Your OPC implementer will provide the Product ID(s) needed to configure the OPC interface in MSS Hosting (see the following “MSS Hosting Setup” section).

http://www.officialpayments.com/

mailto:[email protected]

https://xxx/citizens/Payments/PaymentAmount.aspx

https://xxx/citizens/default.aspx

https://xxx/citizens/Payments/PaymentError.aspx

https://xxx/citizens/Payments/Confirmation.aspx

https://yyy/citizens/Payments/Confirmation.aspx


MSS Hosting Setup

Multiple Payment Types: If using both eCheck and Credit Cards, check only one of them. See the section entitled “Multiple Payment Types” on page 3 for more info.

You will need to define one OPC payment service in MSS Hosting for each Product ID. For example, if you are separating your Tax and UB payments into two different OPC Product IDs, then you would need to set up two separate payment services in MSS Hosting for Live. For your Live MSS site, the Payment URL should be: https://www.officialpayments.com/pc_entry_cobrand.jsp?lockAmount=true For your test MSS site(s), the Payment URL should be: https://staging.officialpayments.com/pc_entry_cobrand.jsp?lockAmount=true You should always check “Enable use of Postback URL for silent payment confirmation”. The “Postback URL” should be automatically filled in for you, but MSS tries to build it based on the “Web site root URL” and “Web site application path” fields on the Client Configuration page in Hosting. You may need to adjust this URL manually. It should ultimately end up being your MSS base URL + “/PaymentConfirmation.ashx?svc=x&client=y” where “x” is the service number that corresponds to the payment service for the client in question and y corresponds to the MSS client number. The “Return URL” could be the root URL of your MSS website (or a page on your municipal website). It doesn’t have any effect on the payment process and merely controls where the “Return” link on the OPC receipt screen takes the user. The “Error URL” should be set to the base path of the MSS site with “/citizens/Payments/PaymentError.aspx” appended to it. “Maximum Payment Amount” should only be used if OPC has set you up with a cap on the amount that can be paid in a single transaction.


JP Morgan/Chase - Pay Connexion


• The Pay Connexion interface supports both credit cards and eChecks. • The Pay Connexion interface does allow you to pass along a convenience fee to the citizen.

You also have the option to pay the transaction fees instead of passing them to the citizen. • IMPORTANT NOTE: JPM/Chase requires signatures and 6-8 weeks notice before you make

ANY changes, whether it be an SSL Certificate renewal or need to change a URL.

Contact

If you want to proceed with JP Morgan/Chase's Pay Connexion product, please contact: Ed Muendell Senior Vice President (914) 993-2264 [email protected]

Implementing JP Morgan/Chase

Once JPM/Chase sales has finished setting you up as a customer, you will be assigned an implementer that will guide your project through to "Go Live".

You will need to provide the implementer with a set of 4 URLs for each product (Tax, Water, etc...) so that they can interact with MSS: Production Return URL: the link back to your Live MSS inquiry screen for Tax, Water, etc... Production RTPC URL: your Live base URL + "/PaymentConfirmation.ashx?svc=x&client=y" Test Return URL: the link back to your Train or Test MSS inquiry screen for Tax, Water, etc... Test RTPC URL: your Test base URL + "/PaymentConfirmation.ashx?svc=x&client=y" The "x" and "y" above will vary based on the client id and the payment interface id. Those values can be found in your MSS Hosting site.

MSS Hosting Setup

JP Morgan/Chase's implementer will provide you with the information needed to complete the setup form.


Govolution


• The Govolution Velocity Payment System interface supports both credit cards and eChecks. • This interface does allow you to pass along a convenience fee to the citizen. • MSS integrates with Govolution’s vRelay Integrated Web product. Tyler Cashiering integrates

with a different Govolution product called vLink

Contact

If you are interested in using Govolution, please contact: Gregory L. Jackson Sales Director - New Accounts 703-894-5000 ext. 3002 Cell: 703-851-4784 [email protected]

MSS Hosting Setup

The Application ID and Message version should be provided by your Govolution Project Manager. The Payment URL used for testing payments is: https://demo.velocitypayment.com/vrelay/verify.do The Payment URL used for live payments is: https://www.velocitypayment.com/vrelay/verify.do URLs You will need to provide Govolution with two URLs, but before you can define them you will need to take note of two parameters from your MSS Hosting screens. 1) From the "Home" screen, make note of the ID for the Client that you are setting up:



2) From the Payment Services screen, make note of the Service ID:

The two URLs that your Govolution Project Manager will need are:

1) Session Verification: https://<MSSBaseURL>/PaymentSessionVerification.ashx

2) Session Notification: https://<MSSBaseURL>/RespondingPaymentConfirmation.ashx?svc=<Service ID>&client=<Client ID>

For example, if you are testing payments in your Training environment and the base URL for MSS Train is "www.tylertown.com/MSSTrain", your Train client ID is 2 (from the example above) and Govolution is defined as Service ID 0, then your URLS would be as follows: Session Verification: https://www.tylertown.com/MSSTrain/PaymentSessionVerification.ashx Session Notification: https://www.tylertown.com/MSSTrain/RespondingPaymentConfirmation.ashx?svc=0&client=2 Govolution will also need two other URLs, but these aren't tied directly to the MSS/Govolution interface: Continue After Fail URL: you will usually want to link this to a help or contact screen on your website so that the citizen can get assistance from you if they experience an error with making a payment Exit V-Relay URL: this is usually your department or municipality home page UDFs There are five User Defined Fields (UDFs) that must be set up as follows with your Govolution Project Manager: UDF1: Property Code (this could be Parcel, Personal Property ID, Utility Billing Account, etc...) UDF2: Bill Category (this is the AR Category Code. Real Estate = 20, Personal Property = 25, etc...) UDF3: Bill Year and Bill Number (will appear in this format: "2012 - 12345678" UDF4: Customer Name UDF5: Session Identifier All UDFs should be required and UDF5 should not be shown on screen.

Other Settings/Considerations

You will need to tell the Govolution Project Manager to configure the VPS to host your receipt page. The citizen will not be redirected back to MSS after they make their payment. The authorization code will be posted back to MSS "silently" without affecting the user's browsing experience. Govolution must be told to not allow citizens to change the payment amount after we redirect the client to their site. Govolution should set “Modify Billing Data” to “Yes”.


Forte - Secure Web Pay Checkout


• This interface supports both credit cards and eChecks. • This interface gives you the option to either pass along a convenience fee to the citizen or to

absorb the convenience fee. • This payment gateway supports the Illinois E-Pay program.

Contact

If you are interested in using Secure Web Payments Checkout, please contact: Jami Hughes Director of Sales [email protected] (866) 764-2002 ext. 721

Be sure to tell Forte that you will need the Secure Web Pay Checkout product to interface with MSS.

MSS Hosting Setup

Multiple Payment Types: If using both eCheck and Credit Cards, check both options. See the section entitled “Multiple Payment Types” on page 3 for more info.

The "API Login ID" and "Secure Transaction Key" will be provided by your Forte project manager. You will have different credentials for Live and Test. The "Payment URL" used for testing payments is: https://sandbox.paymentsgateway.net/swp/co/default.aspx The "Payment URL" used for live payments is: https://swp.paymentsgateway.net/co/default.aspx At the bottom of the page, you'll be shown a URL that needs to be entered in the Secure Web Payments administration site. See the next section for details on where to enter that on the Secure


Web Pay website. This URL also needs to be entered into the "Return (postback) URL" field on this MSS Hosting screen. NOTE: The automatically displayed URL is based off of the "Web site root URL" from the Client Configuration screen. The "Continue button URL" should be populated with the web page URL where you want citizens to be taken after they finish the payment. Typically, this would be back to your own municipal website. You can customize the wording on the SWP "Continue" button with the "Continue button text" field.

Secure Web Pay Setup

Log into the Forte paymentsgateway.net website and choose "Gateway Settings" and "Secure Web Pay" on the left. On the "Main" tab, enter the Postback URL from the MSSHosting page in the "Return Page 1" field. Click the "Update" button on the bottom of the page.


Click the "Field Settings" tab. Set the Consumer Order ID to "Required" and enter "Account Info" as the description. Set “Data 1” to “Required” and enter “Bill Info” as the Description. Click the "Update" button.


ETS – EMoney Hosted ECOM


• This interface supports credit cards only (no eChecks) • The ETS interface does not natively allow you to pass along a convenience fee to the citizen; all

transaction fees must be absorbed by the client or you must use the Global Convenience Fee option in MSS Payment Administration.

Contact

If you are interested in using the ETS interface, please contact: Sean Lynch Relationship Manager 10 Pidgeon Hill Drive Suite 200 Sterling, VA 20165 Direct Line: (800) 834.7790 ext. 222 Fax: (703) 421.9158 [email protected]

Be sure to tell ETS that you will need the EMoney Hosted ECOM product set up to interface with MSS.

MSS Hosting Setup

The "ECOM Request ID" and "ECOM Response ID" will be provided by your ETS project manager. You will have different values for Live and Test. Do NOT put the curly braces around the codes when entering them in the MSS Hosting Setup screens. The "Payment URL" used for testing payments is: https://test.etsemoney.com/ecomh/main.aspx The "Payment URL" used for live payments is: https://www.etsemoney.com/ecomh/main.aspx The "Verification URL" used for testing payments is: https://test.etsemoney.com/ecomh/verify.aspx The "Verification URL" used for live payments is: https://www.etsemoney.com/ecomh/verify.aspx


At the bottom of the MSSHosting page, there will be a "Recommended postback URL". ETS will need this (see below).

ETS EMoney TransVault Hosted ECOM Setup

Your ETS contact will need several different URLs from you to complete the setup on their side. Approval URL: use the "Recommended postback URL" from the MSS Hosting page. Decline URL: use the "Recommended postback URL" from the MSS Hosting page. Error URL: use the "Recommended postback URL" from the MSS Hosting page. Cancel URL: this one is flexible. You could return the citizen to your municipal website, to a MSS page, etc… Referral URL list: not required for our interface with them Privacy Policy URL: this should be a page on your municipal website Refund Policy URL: this should be a page on your municipal website


VPS – Value Payment Systems


• This interface supports both credit cards and eChecks • This interface does allow you to pass a convenience fee to the citizen. • Introduced in Munis Version 10.3

Contact

If you are interested in using the VPS interface, please contact: Alisdair Kinloch Channel Sales Representative (615) 730-6367 ext. 333 [email protected]

MSS Hosting Setup


The values for Partner ID, Partner User Name and Partner Password will be provided by VPS. The Partner Name can be set based on the client’s preference. The Live VPS payment initiation URL is: https://gateway.vpsenv.com/Passthrough/vpssubmit.aspx The Test VPS payment initiation URL is: http://demo.valuepaymentsystems.com/vpssubmit/VPSSubmit.aspx The Live VPS payment page URL is:

https://paylocalgov.com/integratedpay/makesecurepayment.aspx?tid= (older style) OR https://www.paylocalgov.com/passthrough/Payment/CurrentSession/ (newer style)

The Test VPS payment page URL is:

https://demo.valuepaymentsystems.com/integratedpay/MakePayment.aspx?tid= (older style) OR https://devel.vpsenv.com/apipayment/Payment/CurrentSession/ (newer style)

The Partner’s redirection URL should be a page on your municipal website or your MSS website. This controls where the “Exit” button on the VPS website takes the citizen after they’ve made their payment. The Partner’s payment postback URL should be the base URL for your MSS page with “/PaymentConfirmation.ashx?svc=x&client=y”. “x” and “y” will vary depending on the Service and Client number assigned in hosting. A suggested URL will be shown below this field to guide you on what those values should be. The Submit line items as parameter is a matter of client preference. Options are “Bill Numbers” or “Account Numbers”. NOTE: The postback URL must be URLencoded. Change “&” to “%26” and change “=” to “%3d”


Paymentus


• This interface supports both credit cards and eChecks • This interface does allow you to pass a convenience fee to the citizen. • Introduced in Munis Version 9.4

Contact

If you are interested in using the Paymentus interface, please contact: Paymentus Customer Care, PH: 800-420-1663

Email: [email protected]

MSS Hosting Setup

Multiple Payment Types: If using both eCheck and Credit Cards, check only one of them.

Configuration is VERY simple. Paymentus will provide you with one URL and you will need to provide them with one URL. The Paymentus URL should start with “secure1” for test or “ipn” for production. A “Recommended Postback URL” will be generated for you, but you should ensure that it starts with your base MSS Url followed by “PaymentConfirmation.ashx?svc=x&client=y” where “x” and “y” match the service and client ids assigned in the MSS Hosting site. Paymentus will assign you different URLs for Live and Test.

Instructions for Paymentus

Tell your Paymentus contact that you are using MSS and that you will need them to host your payment site. If you are also using/planning to use Tyler Cashiering, please be aware that it will require a completely separate setup on the Paymentus side. You must also tell your Paymentus contact that MSS will pass the Account Number in two fields that they should string together into their hyphenated account field: header.accountNumber and header.accountToken. That field should be made read-only so citizens can’t alter it. The citizen should also not be allowed to edit the payment amount.



UniBank


• This interface supports both credit cards and eChecks • This interface does allow you to pass a convenience fee to the citizen. • Introduced in Munis Version 10.1 • This software is branded AndroPay in Maine

Contact

If you are interested in using the UniPay interface, please contact: Debbie Mateer UniPay Supervisor - Government Banking Department [email protected] Toll Free: 877-227-1157 Ext. 1131 Direct: 508-849-4255

UniBank Configuration

You will need to provide UniBank with the postback URL. A “Recommended PostBack URL” will be generated for you at the bottom of the MSS Hosting payment configuration screen. UniBank should use the exact names for the following variables when posting back to MSS:

AmountPaid UniqueID BillNumber TaxYear Name PropertyAddress ConfirmationNumber


MSS Hosting Setup

Multiple Payment Types: If using both eCheck and Credit Cards, check only one of them. See the section entitled “Multiple Payment Types” on page 3 for more info.

All of the required values will be provided to you by UniBank. The Optional Configuration Settings can be used to adjust the behavior of the UniBank payment pages.


Authorize.Net


• This interface supports both credit cards and eChecks • This interface gives you the option to either pass along a convenience fee to the citizen or to

absorb the convenience fee. • Introduced in Munis Version 10.3

Contact

If you are interested in using the Authorize.Net website, please go to http://www.authorize.net/

MSS Hosting Setup

Payment Transaction URL: enter https://secure.authorize.net/gateway/transact.dll Authorize.NET Version: 3.1 The rest of the fields will be supplied by Authorize.Net. The Recommended Silent Postback URL will be needed on the Authorize.Net website.

Testing

For test credentials, see http://developer.authorize.net/hello_world/testing_guide/

https://secure.authorize.net/gateway/transact.dll

http://developer.authorize.net/hello_world/testing_guide/


Authorize.Net Setup

Log in to the account.authorize.net website and click on “Account”

You will need to update two sections on the Authorize.Net Account Settings page:


On the “Payment Form” page, click on “Form Fields”. Check just the following fields under “Customer Billing Information” and leave all other boxes unchecked:

On the “Silent Post URL” page, you will need to provide the URL that Authorize.Net will use to post authorizations back to Munis. The MSS Hosting page will suggest a “Recommended Silent Post URL”, but you need to review that carefully to make sure it is a valid internet URL. It should be the base MSS URL with “PaymentConfirmation.ashx?svc=x&client=y” appended, where x and y are your service and client IDs as show in MSSHosting. Once you are done, click the “Submit” button.


Xpress-Pay


• This interface supports both credit cards and eChecks • This interface gives you the option to either pass along a convenience fee to the citizen or to

absorb the convenience fee. • Introduced in Munis Version 10.5

Contact

If you are interested in using Xpress-Pay, contact Peter Rogati Director of Operations Systems East, Inc. (607) 753-6156 [email protected]

MSS Hosting Setup


Elavon Converge


• This interface supports both credit cards and eChecks • The Elavon Converge interface does not natively allow you to pass along a convenience fee to the

citizen; all transaction fees must be absorbed by the client or you must use the Global Convenience Fee option in MSS Payment Administration.

• Introduced in Munis Version 10.5

Contact

If you are interested in using Elavon Converge, please contact: Darren Trainer Regional Sales Manager Government, Utilities and Higher Ed 817-788-1677 [email protected]

MSS Hosting Setup

Elavon will provide you with the Merchant ID (look for a 6-digit “Account ID” on the Elavon website), User ID and Pin.

Typically, the Payment URL for Test transactions will be: https://demo.myvirtualmerchant.com/VirtualMerchantDemo/process.do

The Payment URL for Live transactions should be: https://www.myvirtualmerchant.com/VirtualMerchant/process.do


Elavon Converge Setup

Elavon will provide you with a URL and credentials for configuring your Converge merchant setup. Log in and go to Terminal > Merchant > Payment Fields. Click one of the “Add New Field” buttons to create a new custom field named “confNbr”.

Set the Display Name to “confNbr”, the Field Type to “Text”, and the Maximum Number of Characters to “50”. Check the boxes for “Forward on Approval” and “Forward on Decline” and click the “Add New Field” button to save the custom field.


There will be a number of fields that are available to show your clients, but the only ones that the MSS interface require to be used are:

ssl_result ssl_first_name ssl_last_name ssl_avs_address ssl_address2 ssl_city ssl_state ssl_avs_zip ssl_email ssl_txn_time

Please make sure that “Forward on Approval” and “Forward on Decline” are checked for each of the fields listed above.

To allow Converge to “talk back” to MSS, you need to set up a MSS URL in the Converge website. Navigate to Terminal > Advanced > System Setup. Under “Export Options”, enter the base URL for your MSS site followed by “/PaymentConfirmation.ashx?svc=x&client=y”, where x and y correspond to the Client ID and Service ID set up in MSSHosting. You can get those numbers under the “Suggested postback URL” note on the MSSHosting configuration page for the interface:


For example, if your MSS URL is https://www.anytown.gov/MSS and the Suggested postback URL were the above, then the URL you would enter in these three fields

would be https://www.anytown.gov/MSS/PaymentConfirmation.ashx?svc=0&client=1

Make sure “Enable Export Script” is checked.

https://www.anytown.gov/MSS/PaymentConfirmation.ashx?svc=0&client=1


OpenEdge


• This interface supports both credit cards and eChecks • The OpenEdge interface does not natively allow you to pass along a convenience fee to the


• Introduced in Munis Version 10.5 • MSS interfaces with OpenEdge’s HostPay product

Contact

If you are interested in using OpenEdge, please contact: Susan Gresham Merchant Sales Representative (800) 774-6462 x3608 [email protected]

MSS Hosting Setup


Merchant Account Id: OpenEdge calls this the “Account Token”. It should be an 82-character string.

Payment Page Url: For testing, use: https://ws.test.paygateway.com/HostPayService/v1/hostpay/paypage/ For production, use: https://ws.paygateway.com/HostPayService/v1/hostpay/paypage/

Pay Page Header Label: This customizable text appears at the top of the HostPay payment form.

Postback Url: This should be constructed based on the “Recommended silent postback URL” below the form.

https://ws.test.paygateway.com/HostPayService/v1/hostpay/paypage/

https://ws.paygateway.com/HostPayService/v1/hostpay/paypage/


BridgePay


• This interface supports both credit cards and eChecks • The BridgePay interface does not natively allow you to pass along a convenience fee to the



Contact

If you are interested in using BridgePay, please contact: David Martinez 407-960-6483 [email protected]

MSS Hosting Setup

Update the following fields:



WebLINK URL: For testing, use: https://www.bridgepaynetsecuretest.com/WebLink3/WebLink.aspx For production, use: https://www.bridgepaynetsecuretx.com/WebLink3/WebLink.aspx

BridgePay Login: BridgePay will provide this to you.

Password (unencrypted): BridgePay will provide this to you.

Payment Server Mode: “Test mode” for test, “Live mode (real payments)” for production.

Postback URL: This should be constructed based on the “Recommended silent postback URL” below the form.

Prefer use of Payment Token over Login/Password: uncheck this box.

https://www.bridgepaynetsecuretest.com/WebLink3/WebLink.aspx

https://www.bridgepaynetsecuretx.com/WebLink3/WebLink.aspx


PayPal Payflow Pro


• This interface only supports credit cards. It will not accept eChecks. • This interface does not natively allow you to pass along a convenience fee to the citizen; all

transaction fees must be absorbed by the client or you must use the Global Convenience Fee option in MSS Payment Administration.


Contact

If you are interested in using the PayPal Payflow Pro interface, please visit PayPal.com.

MSS Hosting Setup


InforME


• This interface only supports credit cards. It will not accept eChecks. • This interface does allow you to pass a convenience fee to the citizen. • Introduced in Munis Version 10.3 • This interface is ONLY available to Maine clients

Contact

If you are interested in using the InforME interface, please contact: Dustin Biggs [email protected] 207-621-2600 x039

MSS Hosting Setup

Service Code, Merchant ID and Merchant Key will be provided by InforME. State Code will be “ME”.

Prepare checkout post URL Production: https://securecheckout.cdc.nicusa.com/CommonCheckPage/Payment/FrmClient Test: https://stageccp.dev.cdc.nicusa.com/CommonCheckout/Commoncheckpage/Payment/FrmClient Payment redirection URL Production: https://securecheckout.cdc.nicusa.com/CommonCheckPage/Default.aspx Test: https://stageccp.dev.cdc.nicusa.com/CommonCheckout/Commoncheckpage/Default.aspx

Payment cancellation URL should be your MSS home page. This is where users will be taken if they cancel their payment attempt on the InforME website.


Citizen Self Service – Online Payments Guide

Documents

Transcript of Citizen Self Service – Online Payments Guide