IDI version 26.8 is now available.  Click here for details: IDI Updates.

Other Setup for Web Sales and Paymentus Payment Vendor

Prev Next

In addition to enabling starting blocks and toggling register management as described in Settings, the following setup may also be needed.

Register Policy and Location Setup in IDI Desktop Client

This setup is required to support several aspects of retail transactions. Location and Register Policy setup is covered fulling in IDI Desktop Client Online help. Below provides some quick guidelines:

  • Register Management - POS Locations and registers, including Register Policies, must be configured in the IDI Desktop Client with users assigned for them to have the ability to assign themselves to registers in the Orders web module.

  • Support for Paymentus payment vendor – This is covered in the following section.

  • Credit card tendering if you are not using Paymentus - Credit Card tender type must have payment gateway configured for Authorize.net. ACH tenders require a valid routing number.

Support for Paymentus Payment Vendor

As a prerequisite, your IDI platform must be integrated with Paymentus. This is covered in the Paymentus Integration article in the IDI Knowledge Center.

With this done, you need to configure POS locations (stores) and registers via IDI Desktop Client POS Back Office. Register Policy setup lets you select Paymentus as a tender type and then configure the Paymentus Payment Gateway details. Also, store setup lets you specify a Paymentus ID to support payments through a Paymentus peripheral device. Access to this setup is via IDI Desktop Client Applications > POS Back Office > Locations.

  • Register Policy Setup - This is required if you intend to use a Paymentus payment method or peripheral device.

    Note

    Equivalent setup is done in Customer Care > MANAGE > Paymentus Configuration. The Customer Care setup applies when tendering bill payments and E-Pay for a selected account in Care. The register policy setup in IDI Desktop Client applies when you select a specific register to tender a web sales transaction.

    To set up a register policy:

    • Right-click on a location and select Register Policy from the context menu.

    • On the Register Policies form choose to Override the global register policy if applicable, then on the Tender tab, right-click in the Tender Types Accepted area and select Choose.

    • Select the Paymentus tender type.

    • After adding the Paymentus tender type, right-click on it and choose Payment Gateway > Configure from the context menu.

    • Select Paymentus.

    • Configure the Paymentus payment gateway details.

    • User Group - Enter the User Group provided by Paymentus to grant access to functionality applicable to IDI Desktop Client and OnlineBill users.

    • Paymentus Subdomain and TLA - These values are provided by Paymentus and map Paymentus to a single IDI platform environment.

    • SSO Encryption Secrets - The Paymentus Agent Dashboard (for Customer Care) and Customer Portal (for OnlineBill) each require a different SSO Secret. These secrets are unique per IDI environment and are provided by Paymentus.

    • XOTP Username and Password - These are unique per IDI environment and are provided by Paymentus.

  • Setting Up Paymentus Location for a Store - This is required if you intend to tender transactions using a Paymentus peripheral device. The Location ID and device(s) that will be available for that location are determined though setup coordinated by your organization and Paymentus. To specify the Paymentus Location-id on a store-by-store basis:

    • Select the store in IDI Desktop Client via Applications > POS Back Office > Locations.

    • On the Add/Edit Store form, Store Info tab, enter the Paymentus location-id provided by Paymentus.

Prerequisites for Service/Installment Agreements

As a prerequisite, your IDI Desktop Client Product Catalog must have contracts and/or retail products with service agreements/installment plans available to include on web transactions.

A service agreement is associated to a contract via the Add/Edit Contract Specification form in IDI Desktop Client Product Catalog.

An installment agreement is associated to a serialized retail product by first associating an agreement to an installment plan profile in Product Management > Installment Plan Profiles.

And then associating an installment plan profile to the retail product in the IDI Desktop Client Product Catalog.

Prerequisites for Credit Checking

This topic provides a quick overview. Complete setup details are provided in the Setup for Credit Scoring and Deposits article in the IDI Knowledge Center.

  • Getting Started/Prerequisites - Establish a relationship with TransUnion and work with them to set up an account for your company. Contact your IDI Project Manager for advice on how to do this. Then submit a work order to have IDI set up credit scoring logic as described above. Include your specific requirements for an IDI specialist to assess.

  • Credit Scoring

    • Assign permissions in Admin Console Security and Web SaaS Security.

    • Configure credit scoring settings in IDI Desktop Client.

    • Configure credit classes in Admin Console > Data Management.

    • Configure one or more starting blocks in the Product Catalog web module.

  • Deposits

    • Assign permissions in Web SaaS Security.

    • Configure tables related to deposits in Admin Console > Data Management. This includes:

      • Allocation Types

      • Deposit Types

      • Waive Types

      • Interest Rates