Your SlideShare is downloading. ×
Pay Day: How to Get Results from an Electronic Payment Manager
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Pay Day: How to Get Results from an Electronic Payment Manager


Published on

Published in: Economy & Finance, Business

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. NASACT 2004 Annual Conference November 15, 2004 Biloxi, Mississippi Pay Day: How to Get Results from an Electronic Payment Manager
  • 2. Mississippi History
    • Initiation of 2001
      • Enterprise portal for the State
      • Enterprise payment processor
        • Key component of infrastructure
        • Flexibility required
        • Integration with SAAS required
        • Concept was true “plug-and-play”
        • Here’s what we had in mind. . . . .
  • 3. Enterprise Payment Concept Still at the Agencies
  • 4. Electronic Payment Processing
    • What are electronic payments?
      • The processing of payments through electronic means
    • What is Enterprise Payment Processing?
      • Enables agencies to accept and process multiple payment types for different entities across the entire organization
    • Why is it important?
      • Enables governments to achieve and leverage economies of scale and scope
      • Enables governments to streamline financial activities
      • Enables governments to centralize control of the process to improve maintainability and support
  • 5. Practical Considerations
    • Solution should allow a choice of banks and payment service providers
    • Solution should support multiple payment methods, including ACH and e-checks to give more options to citizens, thereby increasing usage
    • Passing convenience fees or other charges along to users suppresses usage levels
    • Solution should help streamline financial reconciliation through tight integration with your existing financial system
    • Solution should provide strong Enterprise and agency-level reporting
    • Solution should provide flexible integration with client applications (Web Services/SOAP, Java, COM) to support the technologies in place at various agencies
  • 6. Technical Lessons Written in Java for platform independence All ANSI SQL databases supported (Oracle, MS SQL Server, DB/2, etc.) Uses high bandwidth, high speed connections to PSP and/or banking network Applications can be hosted in same facility or remotely Easy integration to back office systems Applications can be developed by 3 rd party vendors and access PaymentEngine TM via APIs
  • 7. Applications using Payment Engine
  • 8. What Is Payment Engine
  • 9. What Is Payment Engine
    • Real time payment authorizations (today’s implementation)
      • Visa and MasterCard credit and debit cards
      • E-check
      • Automatic payment settlement/deposit with State’s designated bank
      • Integration with SAAS (SPI)
      • Voids
      • Refunds
      • Automated return/chargeback processing
      • Current Mississippi Implementation
      • Financial reporting
      • Payment tracking/audit trail with unique confirmation numbers
      • Secure hosted service
  • 10. What Is Payment Engine
    • PE daily extract feeds settled data to the SAAS Payment Interface (SPI)
    • SPI generates “CC” documents
      • Specialized SAAS cash receipt documents
      • Gross settlement amount posted
      • Remain on SUSF until funds hit Treasury’s bank account
    • Net settlement
      • ACH transfer
      • Deposited to Treasury’s bank account
    • Processing fees
      • Recorded as an expense to Paymentech
      • EzGov fees billed monthly
    • Unbudgeted/unappropriated DFA fund
      • Collects convenience fee deposits
      • Records expenses of transaction processing costs
    • Reports
      • SAAS Activity Report
      • Enterprise Settlement Report
      • Agency Settlement Report
  • 11. What Is the “SPI”
    • SPI – SAAS Payment Interface
    • Defines Payment Allocations
      • Agency transaction
        • Flat amounts and percentages
        • Full accounting line distribution
      • Agency handling fees
      • Convenience fees (to DFA fund)
      • Paymentech expense (to DFA fund)
      • Effective dated
    • Imports payment extract (settlement) file from EzGov
    • Exports transactions to SAAS with appropriate distributions
    • Works so well we plan to piggyback other settlement processes
  • 12.  
  • 13. What Applications and When? Maps Public Service Commission October-04 License Renewals Board of Nursing October-04 Bid Package Acquisition Transportation August-04 License Renewals Board of Medical Licensure May-04 Land Filings Secretary of State April-04 Annual Report Filings Secretary of State September-03 UCC Filings Secretary of State October-02 License Renewals, Reinstatements, Moving Violation Reports Public Safety June-02 Hunting and Fishing Licenses Wildlife Fisheries and Parks March-02 Boat Registrations Wildlife Fisheries and Parks February-02 License Renewals, Exam Registration, Licensee List Board of Architecture October-01
  • 14. Payment Tracker
  • 15. Agency Settlement Report
  • 16. Enterprise Settlement Report
  • 17. What’s Next
    • Payment Manager Migration
    • Web-services front end
      • APO/FPO address options
      • Additional testing facilities with EzGov
      • Reporting Database
        • Activity Report
        • Deposit Report
        • Ad hoc reporting
      • Partial refunds
      • International currency handling
      • American Express payment option
      • Discover Card payment option
      • ACH debit transactions
        • Similar to e-check but with fewer validations done at the front end
        • G ood option for establishing recurring debit transactions for applications   
  • 18. For More Information: Cille Litchfield Chief Systems Information Officer Department of Finance and Administration (601) 359-1433 [email_address] Christie Acker Account Executive EzGov, Inc. (404) 836-7962 [email_address]