Cashiering setup

To set up a hosted page payment gateway provider you must configure a merchant account in Infor Public Sector. Select Hosted Page from the Payment Server Gateway list.

When you select Hosted Page, two additional tabs are displayed: Redirect and Payments.

Use the Contents field on the Redirect tab to specify how the customer will be redirected. You can specify a redirect URL, an HTML element such as a button, or a script. You can also use template variables, and you can retrieve values for the Contents field from the merchant account's custom properties.

For more information, see the Cashiering documentation in the Infor Public Sector User and Administration Library on docs.infor.com.

Cancel

When the redirect URL is generated and returned to the user successfully, Rhythm for Civics displays a popup message asking the user to confirm before proceeding to the hosted page. If the user chooses not to proceed, they will be taken to the Cancel page specified in the widget configuration. The register transaction created for this session will remain pending unless it is configured to point to the hosted return page when the Cancel button is clicked.

The Checkout page's Cancel action will take the user to the specified page and the transaction token will be canceled. The hosted return page detects the transaction token being sent by the Cancel action and will void it out eventually since the cancel action does not provide a result that the merchant account recognizes. If the Cancel page in the checkout widget is configured to any other page, the transaction will remain pending and will rely on the background batch process to clean it up.

Payments

Communication between Infor Public Sector and the payment gateway provider can be triggered by Rhythm for Civics, the Clean Up Pending Register Transactions batch task, or any custom agency workflows or background processes. Infor Public Sector sends out a web request to communicate with the payment gateway provider via IPS NetClient based on the web profile configuration found in each of these subtabs under the Payments tab.

Prepare Payment
PreAuthorize Payment
Void Payment
Authorize Payment
Inquire Payment
Reverse Payment
Inquire Reversed Payment

This table shows the detailed behavior of each payment configuration:


Payment configuration	Success	Fail	Triggers
Prepare Payment	Initialized	Declined	When the checkout page is opened
PreAuthorize Payment	Authorized	Declined	Reserved for customization
Void Payment	Completed	Failed	Reserved for customization
Authorize Payment	Approved	Declined	When the rhythm user is taken back to the hosted return page
Inquire Payment	Approved	Authorize and capture: Authorized Purchase/none: Initialized	Batch task: Clean up Pending Cashiering Register Transaction
Reverse Payment	Completed	Failed	Batch task: Clean up Pending Cashiering Register Transaction
Inquire Reversed Payment	Completed	Failed	Batch task: Clean up Pending Cashiering Register Transaction

Note: For Reverse Payment and Inquire Reversed Payment, the status is set on the voided payment server transaction.

Template variables

Template variables can be used to represent values from the Infor Public Sector database. When the web profile in each payment tab is executed, or when the redirect URL is constructed, a template utility parses the content into template tokens. Each token is parsed and replaced with the appropriate value. In the hosted page payment gateway integration, the merchant account being used by the portal register, the current drawer transaction, and its corresponding payment server transaction are passed to the template engine.

This table shows some examples of template variables:


Entry	Source	Examples
Redirect URL: Contents	oMerchantAccount oDrawerTransaction oPaymentServerTransaction ServerApplication	{{oDrawerTransaction.RegisterTransaction. RegisterTransactionNumber}} {{oDrawerTransaction.RegisterTransaction. TransactionToken}} {{oMerchantAccount. MerchantAccountCustPropToMerchantAccount. Get("variable1")}}
In all payment configurations: Host Address	oMerchantAccount oDrawerTransaction oPaymentServerTransaction ServerApplication	https://`server`/ services/v1a/shared-services/payments/ transactions/ {{oPaymentServerTransaction.CustomProperties. Get("resultId")}}
In all payment configurations: Contents	oMerchantAccount oDrawerTransaction oPaymentServerTransaction ServerApplication	{{oDrawerTransaction.RegisterTransaction. RegisterTransactionNumber}} {{oDrawerTransaction.RegisterTransaction. TransactionToken}}

Security

When configuring the payment gateway integration in the merchant account setup, you will often include API keys, user names or passwords in the requests. To securely store sensitive data in the database, you can use the merchant account's custom properties on the Account Information tab.

To enable this feature, select the Encrypt Custom Properties check box. Any new entries added to the merchant account's custom properties will be encrypted. To retrieve the data, you can use the template variable and refer to oMerchantAccount.MerchantAccountCustPropToMerchantAccount.Get("***custom prop name****") anywhere in the host address, content or formula.