Elavon Fusebox configuration

To process a transaction without transmitting, processing or storing any credit card information, Rhythm for Civics sends the credit card numbers directly from the client's browser to Elavon in exchange for a token. The token can only be recognized and processed by the merchant. Rhythm for Civics then sends the payment information along with the token to the back office for processing. Register transactions, drawer transactions, and payment server transactions are created after the payment method is selected. No pending transactions are created in this type of integration.

To configure Fusebox you must first register with Elavon. You must then add a payment gateway provider and a merchant account. Finally, you must configure the Checkout widget in Rhythm for Civics.

First, open the Configuration Editor and select the PaymentGatewayProvider configuration. Add a new Provider node. For the ProviderName attribute specify Elavon. For the Moniker attribute specify Hansen.Cashiering.PaymentGateways.ElavonGatewayProvider.

Next, log in to Infor Public Sector and open Cashiering Setup. Add a merchant account for Elavon, specifying the host URL of the Elavon gateway and port number 7500.

Add these custom properties to the merchant account:


Property	Value
0109	Enter the terminal ID that you received from Elavon.
8002	Enter the site ID that you received from Elavon.
8006	Enter the chain code that you received from Elavon.
0050	True. Requires security code validation for credit card payments.
0700	True. Requires a ZIP code for credit card payments.
0701	True. Requires an address for credit card payments.

Finally, log in to the portal site as an administrator. Navigate to the checkout page and open the widget configuration. Specify the Elavon token host, the chain code, the location ID, and the terminal ID.

See Checkout widget.

Note: In the widget configuration, Rhythm for Civics should be provided with a different set of locator values than the ones used to set up the merchant account in Infor Public Sector. The locator values specified in the widget configuration should be used against credit card tokenization and should only be used for this purpose. Payment requests initiated with these locator values should be denied and dropped by Elavon. Failure to do so poses a security risk that users can use the information to make their own payment requests, such as refunding a payment.

To request locator values from Elavon, you need a separate site ID that is used for the SAFE-T instant tokenization process and has its own unique locator values, but is set up with the same Token Vault hierarchy as is used for the processing sites. This way they would pass up different location ID and terminal ID values for the tokenization process, versus what they use for transaction processing.