Payment processing configuration
Most importantly, you must add a merchant account to process payments through the portal. You must then add a cash register that uses that merchant account. To configure your cash register for use in the portal, enter the register ID in the Cashiering Register ID attribute on the node in the Portal configuration.
You will also need an open cash drawer. After you create the cash drawer and count it in, you can keep it open indefinitely. Finally, the user name that is used to connect to the back office (specified in the IPS User Name attribute of the node) must be associated with an employee ID. The employee ID is used to log in to the cash register, and is recorded in register and drawer transactions.
See the Infor Public Sector Cashiering Administration Guide and the Infor Public Sector Cashiering User Guide for more information.
For merchant accounts, Rhythm for Civics supports these payment gateway providers:
- Elavon Converge and Elavon Fusebox are supported out of the box.
- Payment Express PX fusion is also supported out of the box.
- You can define a generic web form gateway provider. This gives you the ability to define your own pay form in HTML format, which has a post target pointing to the payment gateway directly. Rhythm for Civics looks for the form target and posts the sensitive credit card data directly from the client's browser to the payment gateway in exchange for a result token. Rhythm for Civics will process the payments with just the result token
- You can define a generic hosted page gateway provider. The hosted payment pages are hosted on external, third party sites for processing the payment. The responsibility for transmitting, processing and storing sensitive credit card data is offloaded to the external site.