Data model: wide_payment
Description
wide_payment data model is as important as wide_order. It allows Revel Data Connector users to see how customers pay for orders, how those habits change over time and other information specific to payments.
Revel Data Connector users using this data model can answer questions like:
- What is the preferred payment method of customers and how has it changed over time?
- How many orders are being paid for using multiple payments or different payment methods?
- What is the percentage of returning customers based on payment information?
- Which establishments have the most of returning/new customers?
- etc.
Data Objects
| Resource | Data type | Mode | Description | Example |
|---|---|---|---|---|
| payment_id | int4 | Required | Unique ID for a payment | 5 |
| cc_customer_identifier | varchar | ‘N\A’ | Unique identifier of a customer. This identifier is made by hashing a combination of customer’s credit card first name, last name and last 4 digits. | f9627bb25f2f9e87beb92357594ed927 |
| payment_type_name | varchar | ‘N\A’ | The way payment was made | Cash |
| card_type_name | varchar | ‘N\A’ | Type of card used in making payment | Mastercard |
| payment_amount | numeric | Required | Amount paid by customer, monetary value | 75.200000 |
| tip_amount | numeric | Required | Amount paid as tip, monetary value. | 5.000000 |
| transaction_status | varchar | ‘N\A’ | Status of the payment. E.g Pending, Accepted, Declined, Captured or Unidentified. | Pending |
| is_refund | bool | Required | Identification if payment is a refund. | False |
| payment_source_type | varchar | Required | Where payment came from. Could be Regular or House account. | Regular |
| payment_created_at | timestamp | Required | 2018-11-08 16:37:41 | |
| payment_updated_at | timestamp | Required | Payment last update date and time in UTC format. | 2018-11-08 16:45:36 |
| order_id | int4 | Required | Unique ID for an order | 3 |
| order_source | varchar | Required ‘Unknown’ | Source channel of the order or pos mode if applicable:
| Web Order |
| order_option | varchar | Required ‘Unknown’ | Identification of order option, e.g. To-Go, Eat-In, Delivery or etc.
| To Go |
| order_status | varchar | Required | Status of the order. | Closed |
| is_order_paid | bool | Required | Identification if order is paid | TRUE |
| pos_station_name | varchar | Required | POS station name. | POS1 |
| revenue_center_name | varchar | 'N/A' | Name of a revenue center a POS station is linked to. | Bar Area |
| establishment_id | int4 | Required | Establishment unique Key | 1 |
| establishment_name | varchar | Required | Establishment Name | Company-1 |
| establishment_city | varchar | Required | Establishment City | Atlanta |
| establishment_state | varchar | 'N\A' | Establishment State | GA |
| establishment_country | varchar | Required | Establishment Country | US |
| company_name | varchar | Required | Company name | Company |
| company_url | varchar | Required | Company url address | company.revelup.com |
| establishment_latitude | float | Nullable | Establishment Latitude | 34.6843294 |
| establishment_longitude | float | Nullable | Establishment Longitude | -86.4109566 |
| establishment_post_code | varchar | Required | Establishment Post Code | 30314 |
| is_establishment_active | bool | Required | Identification if establishment is active, e.g. TRUE or FALSE. | TRUE |
| establishment_group_name_list | varchar | Required | List of establishment’s group names | |Group1|Group2|Group3| |
| timezone | varchar | Required | The configured timezone of the establishment | US\Eastern |
| establishment_division | varchar | 'N/A' | Establishment division. If establishment does not belong to a division, then value is N/A. | Division - 1 |
| establishment_sub_division | varchar | 'N/A' | Establishment sub-division. If establishment does not belong to a sub-division, then value is N/A. | Sub-division - 1 |
Updated over 1 year ago