# Cullinan Financial Transaction Services

## Revision History

| Date       | Description               |
| ---------- | ------------------------- |
| 05/09/2018 | Initial document created. |

## GLOSSARY OF TERMS

The following terms and definitions will assist the reader with understanding the content of the Feature Reference.

| Terms                                       | Definitions                                                                                                                                                                |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| MOP                                         | Method of Payment, tender type                                                                                                                                             |
| POS                                         | Point of Sale, register                                                                                                                                                    |
| Product Code/ Product ID                    | Cullinan's identifier of a product or service. The product id is any number that Cullinan uses for identifying their products. It does not fall into Commander's PLU file. |
| NAXML Product Code Conexxus Payments System | Industry standard identifier to categorize a UPC or Department.                                                                                                            |
| VPN                                         | Virtual Private Network                                                                                                                                                    |
| PII                                         | Personal Identifiable Information                                                                                                                                          |
| OTP                                         | One-Time Password                                                                                                                                                          |
| Config Client                               | Configuration Client                                                                                                                                                       |

## Overview

### Feature Description

This document provides a description of a new Commander feature that implements the ability to support financial transaction services provided by Cullinan Group. It details how the user can configure, use and find reports for transactions provided though the Cullinan Group Financial Transaction interface on the Commander POS.

The Cullinan Group Financial Transaction Interface provides access to a range of Third-Party Product Providers. A retailer can utilize a Kiosk, POS Terminal, mobile phone, browser or third party device to sell a range of financial services products such as money transfer, travel money, re-loadable debit card, and check cashing.

### Hardware Requirements

* Commander Site Controller with C18, Topaz and Ruby2
* RubyCi with Topaz and Ruby2

### Software Requirements

* Base level is B049.01

### Related topics

Use these pages for adjacent setup and transaction flows:

* [InComm](/feature-references/feature-references/incomm.md) — another third-party product integration with similar department, network, and transaction concepts.
* [MoneyOrder](/feature-references/feature-references/moneyorder.md) — dedicated money order device setup, fees, sales flow, and reporting.
* [Mobile Payments](/feature-references/feature-references/mobile-payments.md) — another hosted payment integration with similar connectivity, host configuration, and reporting patterns.

## Configuring Cullinan Financial Transaction Interface

### Prerequisites

The following requirement must be met before the interface is activated:

* Connect the POS and Cullinan host via public access or secure VPN.

### Configuring the Cullinan Financial Transaction Interface feature encompasses:

* Enter the sales mode in the User Panel Function to scan or manually enter the third party product provider information.
* Enter the sales mode in the Soft Key Function to scan or manually enter the third party product provider information.
* In Config Client (Configuration Client), under Payment Controller in the Third Party Product Configuration menu on the POS side configure the connectivity to Cullinan.
* Enabling or disabling the Third Party Product Provider feature.
* The URL populates with default data. Create a OTP (one-time password) to setup or change the URL.
* Create a custom error instruction message to print on receipts for customers.
* Create a custom error instruction message to display on the POS for the cashier.
* Configure one or more Cullinan product ID ranges along with a field to assign a department to each range. There are no reserved Conexxus Product Codes for third party products, so list all departments.
* Determine if the user can view or edit the configuration.

### Department Configuration

Departments need to be setup first for each transaction type. A department is a group of similar items. For example, a dairy department might include items like milk, butter, eggs and ice cream.

A department item is sold in one of the following ways:

* \[Department] soft key: A specific key set up for a specific department.
* \[OTHER DEPT] key: A specific key set up to accept sales to any defined department number.

The maximum number of departments that can be configured by platform:

* Ruby Ci - 9999
* Commander Site controller - 9999

### Using Department Sales

Following are the types of Department Sales:

* [Basic Department Sale](#basic-department-sale)
* [Department Sale with Fee (Money Order)](#department-sale-with-fee-money-order)
* [Department Sale with ID Check](#department-sale-with-id-check)
* [Department Sales with Fractional Quantity](#department-sales-with-fractional-quantity)
* [Department Sale with At-For Pricing](#department-sale-with-at-for-pricing)

### Basic Department Sale

1. Key \<amount> of the item
2. Do one of the following:
   * Touch department
   * Press department key
   * Press \[OTHER DEPT] and then press appropriate department in the Other Department list

### Department Sale with Fee (Money Order)

Money orders are typically sold using department keys. It is common to charge fee for each money order sold. This fee is typically configured to be added automatically.

{% hint style="info" %}
No more than five money orders can be sold during a single transaction.
{% endhint %}

{% stepper %}
{% step %}
Key the amount

Key \<amount> (for example: \[1] \[0] \[0] \[0] = $10.00)
{% endstep %}

{% step %}
Select Money Order

Touch \[MONEY ORDER] soft key or press \[OTHER DEPT] and touch Money Order in the Other Department list.
{% endstep %}

{% step %}
Enter the payee

Key \<payee> or touch \[OK] for a blank name.
{% endstep %}

{% step %}
Complete the sale

Touch \[OK] or press \[ENTER] to complete manually and add money order sale to the transaction along with any applicable configured fee.
{% endstep %}
{% endstepper %}

### Department Sale with ID Check

Departments with alcohol and tobacco products are usually set up with age verification. Purchase of these products is the same as with other departments with the exception of the age verification feature. The system displays message altering the cashier that an ID check is required.

The system rejects further entries until the date of birth is entered. Once entered, the system determines if the customer is old enough to purchase the item and either adds it to the transaction or displays a message.

{% stepper %}
{% step %}
Select the item

Touch or scan a product requiring ID checking.
{% endstep %}

{% step %}
Verify date of birth

Do one of the following:

* Key birth date (mm/dd/yy) and touch \[OK] or press \[ENTER]
* Swipe the magnetic stripe on the driver's license
* Scan the 2D bar code on the driver's license
  {% endstep %}

{% step %}
Review the result

The system either adds item to transaction or displays a message that purchase is not allowed.
{% endstep %}
{% endstepper %}

### Department Sales with Fractional Quantity

Department items can be sold in fractional quantity.

{% stepper %}
{% step %}
Enter the quantity

Key quantity to be sold (for example: \[5] \[0] = 1/2 pound).
{% endstep %}

{% step %}
Enter the department item

Press \[QTY] or enter the department item.
{% endstep %}

{% step %}
Select the item

Do one of the following:

* Key a PLU on the keyboard and press \[ENTER]
* Touch a PLU soft key
* Scan the bar code
  {% endstep %}
  {% endstepper %}

### Department Sale with At-For Pricing

Pricing for some department items is based on purchase of a particular quantity for example, 3 candy bars for $1.00. This is known as At-For Pricing (@/pricing).

{% hint style="info" %}
At-For Pricing cannot be used with items sold in fractional quantities.
{% endhint %}

{% stepper %}
{% step %}
Enter the quantity

Key quantity being sold and press \[QTY].
{% endstep %}

{% step %}
Enter the pricing basis

Key number of items on which the price is based (for example, if the item sells three for $1.00, then key \[3]).
{% endstep %}

{% step %}
Enter the base price

Press \[QTY] and key the base price (for example, key \[1]\[0]\[0]).
{% endstep %}

{% step %}
Select the department

Do one of the following:

* Touch the department
* Press \[OTHER DEPT] and then touch the department in the Other Department list
  {% endstep %}
  {% endstepper %}

Recap: To ring up one unit of item that sells 3 for $1.00 - Press \[3] \[QTY] \[3] \[QTY] \[1] \[0] \[0] this will look on screen like 3\@3/100, then department.

### Configuring Department Sales

Use Department section under Store Operations > Merchandise > Departments to define the departments.

#### Merchandise Configuration

![](/files/a6e1d5ad3325a1683a710911ca606b40260f739e)

<img src="/files/71958c6eede441f1f31471237cbad92e5aef0262" alt="" width="563">

<figure><img src="/files/VtoIaQrhs8y0JqRVbcoT" alt=""><figcaption></figcaption></figure>

![](/files/66a8e3936ea0ff634f39bab553e143e18be2e758)

![](/files/184b28cd86d7071fe9970a8bdc66bd5496994d66)

![](/files/22e302f41530cdfd4e2d20101f6e8fe913f9d92d)

![](/files/c83daf90c60799116a5d53e2658cfb8f49251cbb)

## Reporting

The Department Report reflects sales-related totals and counts on a department by department basis.

![](/files/816b34819a1b7b0037fb818bbe5f7882185480c2)

![](/files/2946f0f9283829a12c1b3f65c31949a5605ee332)

### **Report Details**

* DEPT#: Four-digit identification of the product as it appears in the Department File.
* CUST: Number of transactions that included one or more items from this department.
* ITEMS: Quantity sold of this item.
* %OF SALES: Total Sales for this department divided by Total Sales (all departments).
* GROSS: Total dollar amount collected for sales of a department.
* REFUNDS: Total dollar amount refunded for items returned in a department.
* DISCOUNTS: Total dollar amount discounted for items sold in a department. This total includes both automated and manual discount types:
  * Use of the \[DISC], \[DISC%], and \[DISC AMT] keys
  * Combo, mix 'n match, fuel, and promotional discounts
  * POP discounts
* NET SALES: Total dollar amount of items sold in a department after refunds and discounts have been applied.
* NEG DEPTS: The totals for departments marked as negative departments.
* OTHER DEPTS: The totals for other department sales are not marked as negative departments (typically, most departments fall into this group).
* TOTAL: Total department sales after negative department total is subtracted from other (standard) departments.

### Troubleshooting

![](/files/11112593f853a877a1c270f16966f0de3e7f5a5e)

![](/files/f801d03e17e3f85ab5bdab1239257805217bf6ea)

## Third Party Product Configuration

1. From the Configuration Client, go to: Payment Controller > Third Party Product Configuration.

<figure><img src="/files/Zx3tSQ2xQVtbAyUFMub5" alt=""><figcaption></figcaption></figure>

The Third Party Product Configuration window displays.

![](/files/0db66d2b08fade65c82f3edc1c0b0f535f3e91ec)

### Provider Configuration

Configure the Provider parameters.

![](/files/6b6fc6719806366d9758c33155b08adad5ad65ef)

| Value          | Description                    |
| -------------- | ------------------------------ |
| Provider       | Select \[Cullinan].            |
| Barcode Prefix | Type "CULL".                   |
| Enabled        | Enables the Provider Cullinan. |

### Map the Product ID ranges to the Departments

{% stepper %}
{% step %}
Add a department mapping

In the Department Section, select \[ADD].

<figure><img src="/files/B4yaZvyOwyErWLKjro6x" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select the department

From the Department drop-down menu, select the appropriate Department.

<figure><img src="/files/LvYcS9rNDzyrtR2qtFQx" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Enter the range start

In the Range Start field, enter the appropriate Range Start number.

{% hint style="info" %}
*The maximum length for a valid numeric value for a start or end range is 14.*
{% endhint %}

<figure><img src="/files/KjCGAide4aolglBbQutb" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Enter the range end

In the Range End field, enter the appropriate Range End number.

<figure><img src="/files/EOYxk0ulUiGLPRcBH1fk" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Repeat as needed

Repeat this procedure until all desired departments are added and all the product ID ranges are mapped to the Cullinan provider.
{% endstep %}

{% step %}
Save or cancel

To save your changes, click Save, or click Cancel to exit without saving changes.

<figure><img src="/files/N1cJ8Qzgz0WXyGrI9blH" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The maximum length for a valid numeric value for a start or end range is 14.
{% endhint %}

### EPS Network Configuration

From the Configuration Client, go to: Payment Controller > EPS Configuration > Cullinan Configuration.

<img src="/files/918d434ad6f4462e8dd848f19bc3618bf8c79e66" alt="" width="563">

The Cullinan Configuration window displays.

![](/files/18bc84382f45574d57b39f4d2a877e039d657ca4)

1. Configure the Network parameters.

![](/files/7d6602ca312563e96b190a1cfad9b5e1d45e89d2)

| Value               | Description                   |
| ------------------- | ----------------------------- |
| Network             |                               |
| FEP Enabled         | Enables the FEP.              |
| Agent ID            | Sets the Agent ID.            |
| POS Sequence Number | Sets the POS Sequence Number. |

Configure the FEP parameters.

![](/files/a15ebed48ddc5f4c0565374802794eb3386ee05f)

| Value                             | Description                                              |
| --------------------------------- | -------------------------------------------------------- |
| FEP                               |                                                          |
| Failure Message - Cashier Display | Determines the failure message displayed on the cashier. |
| Failure Message - Receipt         | Determines the failure message displayed on the receipt. |

#### One-time password (OTP)

Editing information in the Network and FEP parameters requires a one-time password.

![](/files/b29ef71d07d0bdbcce74d9ad4c43be45877bb6e0)

The One-Time Password window displays.

![](/files/6d1281fdad47351f3ee56d0946c58071d272e2c2)

{% stepper %}
{% step %}
Generate the OTP

From the One-Time Password dialog box, click Generate OTP.
{% endstep %}

{% step %}
Read the OTP

The OTP generates. Read it from the Commander Site Controller's status display.
{% endstep %}

{% step %}
Confirm the OTP

Click Ok.
{% endstep %}

{% step %}
Enter the OTP

In the One-Time Password field, enter the OTP. Click Ok.
{% endstep %}
{% endstepper %}

The Cullinan Configuration window displays and saves the edited information.

![](/files/23fe7af992978065019ca5ff2f485fb726104f7f)

### Configuring a Touchscreen button for Cullinan with Config Client

From the Configuration Client, go to: Store Operations > Touch Screen

<figure><img src="/files/XMqPhcRq0gLtNSToXwbm" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}
Select the register

From the register drop-down, select the register to edit and click Load.

<figure><img src="/files/AYUrCXsfRfndMVIeWUhj" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select the screen

From the Screen drop-down, select the screen to edit and Click Load.

<figure><img src="/files/X58u0UqzhmjJg0j5wIpX" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Open the User Panel tab

The fuel panel appears first. Select the User Panel tab.

<figure><img src="/files/huKudjINQtqsocROgiT5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Open the preview

Click Preview/Edit and a preview of the Topaz screen appears.

<figure><img src="/files/pvXxTXflmIoVOO1UoYJi" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Edit the button

On the Preview/Edit screen, Double-click the appropriate button.

<figure><img src="/files/P258GpwldreGLXQbDX99" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Set the key type

From the Key Type drop-down, select Function.

<figure><img src="/files/pXzONUt3SobGj4wbsuif" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Set the function

From the Function drop-down, select 3rd Prty Product.

<figure><img src="/files/FiLvUSQd8SCRZLrQMUB0" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Choose the button color

Select a button color for the touchscreen button.

<figure><img src="/files/4chqNn9HPIc6Bn2mHfcM" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Set the label

In Field Line 1, type Cullinan.

<figure><img src="/files/m1fUJD3hYfy7O1YNUVU4" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Apply and close

Click Apply, then Click Close.
{% endstep %}

{% step %}
Save the changes

Click Save.

<figure><img src="/files/C2EEkmG8Aq0xTVxozMx3" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

Log out and back in to the Topaz after applying and saving the changes.

{% hint style="info" %}
Reboot is only required if logging out and back in does not result in syncing.
{% endhint %}

## Using the Cullinan Financial Transaction Interface

### Sales

The customer presents the Cashier with a Cullinan Voucher barcode.

{% stepper %}
{% step %}
Scan or enter the barcode

Manually input or scan the barcode at the touchscreen.

![](/files/2fbbe3c96c226e8a2bddfb03881a91530af947e8)

Type in the barcode to manually enter the barcode from the voucher. An example of manually entering the barcode is displayed below.

![](/files/95804ea8f194465fd85393fb071fc3914658457f)
{% endstep %}

{% step %}
Verify the voucher

After scanning the voucher or after manual input, the Verifying Voucher prompt is displayed.

![](/files/e94f8c378a4a71b1c793c6dbe1cbdd63ac4d3422)
{% endstep %}

{% step %}
Review operator instructions

The request goes to the host and comes back to Viper. The response has several Operator Instructions which are displayed to the Cashier which must be verified with the customer.

![](/files/002dc4b2eb5aa86d3d7f17bd38be2ef5c941c53c)

The Operator Instructions can either be a Yes/No prompt or an Input Prompt as listed below. The input can be either be Keyboard entry or a Barcode Scan.

![](/files/f17ef49074efcf120e3eb245d85099e633354508)
{% endstep %}

{% step %}
Complete the instructions

After the Operator Instructions are successfully implemented the item(s) belonging to the Voucher are displayed on the POS. These items are received from the host.

{% hint style="info" %}
If any of the Operator Instructions fail, the transaction is canceled there only.
{% endhint %}

![](/files/a932ccc887068662185ec94a12eb67b18b90dfd2)
{% endstep %}

{% step %}
Complete payment

The payment can be completed through Cash or Network Payment. Network Payment is out of scope for Cullinan. The following Prompt is displayed after payment is done. A request goes to Cullinan to '**Finalize Voucher**' if the payment was successful.

{% hint style="info" %}
The transaction is canceled if the request fails.
{% endhint %}

![](/files/408c31474898e20c7cecced82765b82e6448204d)
{% endstep %}

{% step %}
Acknowledge the voucher

After 'Finalizing Voucher', the 'Acknowledging Voucher' prompt is displayed, here we acknowledge the completion of the transaction to the Cullinan host.

{% hint style="info" %}
The transaction is canceled if the transaction fails.
{% endhint %}

![](/files/45138493520cfc63c4906668721de6db6cbcd2eb)
{% endstep %}

{% step %}
Finish the transaction

It directs back to the Idle Screen as the transaction is now complete. The cashier gives receipt to the customer.
{% endstep %}
{% endstepper %}

## Reporting

All transaction types occurring within a reporting period are represented on Summary and Cashier Reports for that period.

### Summary Report

The Summary Report provides an overview of all sales from the beginning of the current period up to the time the report prints.

![](/files/652e77e1fa8bf9b5ab159cfd0ec30ede7352c34e)

#### Report Details

TITLE: SUMMARY REPORT

**SUMMARY**

* MOP SALES: Total sales amount by method of payment.
* NET SALES TOTAL: Total amount tendered after cancellations and refunds are deducted.
* PAYMENT OUT: Total amount of non-sales transactions that are removed from the drawer.
* PAYMENT IN: Total amount of non-sales transactions that added payment to to the drawer.
* TOTAL TO ACCOUNT FOR: Calculated using the following:
  * Net Sales Total
  * Payment Out
  * Payment In

**CASHIER DETAILS**

* MOP SALES: Summary of sales by method of payment.
  * CASH: Cash summary of sales by MOP.
  * EXACT CHANGE: Exact change summary of sales by MOP.
  * SPECIAL DISC: Special discount summary of sales by MOP.
  * TOTAL MOP SALES: Total amount of sales by MOP.

### Cashier Report

The Cashier Report calculates the sales totals for that cashier on the terminal where the cashier performed the sales.

![](/files/ee6f54a13460ebed29f69ed1382ebba16f473b88)

#### Report Details

* TITLE: CASHIER REPORT
* REG#: Register for which the Cashier Report was generated.
* CASHIER#: ID and name of the employee who used the register.
* RCPTS: Beginning and ending receipt numbers issued during the cashier period.
* TOT: Total number of receipts printed on this terminal.
* ACT: Total number of receipts used by this cashier.
* OPEN CASHIER: Date and time this cashier started using the register.
* CLOSE CASHIER: Date and time this register was closed.

**SUMMARY**

* BEGINNING CASH: Amount with which cashier started the drawer.
* MOP SALES: Total amount from the MOP SALES section.
* NET SALES TOTAL: Total amount in sales transacted for the drawer.
* TOTAL TO ACCCOUNT FOR: Total amount that should be in the closed drawer.

**CASHIER DETAILS**

* MOP SALES: Summary of sales by method of payment.
  * CASH: Cash summary of sales by MOP.
  * SPECIAL DISC: Special discount summary of sales by MOP.
  * TOTAL MOP SALES: Total amount of sales by MOP.

**MEMO ITEMS**

* \#ITEMS: Quantity of items sold.
* \#CUSTOMERS: Individual transactions.

**TOTALS**

* TOTAL MERCH SALES: Total amount of merchandise sales.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/feature-references/feature-references/cullinan-financial-transaction-services.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.