Difference between revisions of "Red Dot Payment Data Source"
Line 44: | Line 44: | ||
<!------- Details ----> | <!------- Details ----> | ||
==<div style="background: #DD597D; line-height: 0.3em; font-family:calibri; border-left: #CFCFCF solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Metadata</strong></font></div></div>== | ==<div style="background: #DD597D; line-height: 0.3em; font-family:calibri; border-left: #CFCFCF solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Metadata</strong></font></div></div>== | ||
− | + | Previously, we only have the transaction data of 2017 provided by RDP. | |
+ | Moving on, we managed to obtain transaction data of 2016 as well. | ||
<br><br> | <br><br> | ||
Below are the definitions of common terms used in their business model: | Below are the definitions of common terms used in their business model: | ||
<br><br> | <br><br> | ||
− | '' | + | '''''MERCHANT''''' - A merchant is a business, often a retailer, that operates online. Each merchant has appointed RDP to be its payment processor to handle online transactions between them and their customers. |
<br><br> | <br><br> | ||
''<b>CUSTOMER</b>'' - A customer is an entity that makes a transaction with the merchant. For a transaction to be made, a customer must make contact with a merchant and provide their payment details (e.g. Credit card number) to the merchant through RDP’s payment processing gateway. | ''<b>CUSTOMER</b>'' - A customer is an entity that makes a transaction with the merchant. For a transaction to be made, a customer must make contact with a merchant and provide their payment details (e.g. Credit card number) to the merchant through RDP’s payment processing gateway. | ||
Line 58: | Line 59: | ||
! NAME !! TYPE !! DESCRIPTION | ! NAME !! TYPE !! DESCRIPTION | ||
|- | |- | ||
− | | date_created || Date || Data and time at which the transaction was carried out between merchant and customer | + | | date_created || Date Time || Data and time at which the transaction was carried out between merchant and customer |
+ | |- | ||
+ | | period || Integer || Month of the year the transaction was carried out between merchant and customer | ||
+ | |- | ||
+ | | hour || Integer || Hour in a day the transaction was carried out between merchant and customer | ||
+ | |- | ||
+ | | day || Integer || Day of the week the transaction was carried out between merchant and customer | ||
+ | |- | ||
+ | | time || Time || Time at which the transaction was carried out between merchant and customer | ||
|- | |- | ||
| name || Alphanumeric || Name of merchant | | name || Alphanumeric || Name of merchant | ||
|- | |- | ||
− | | amount of money || Decimal || Total transaction amount | + | | amount of money || Decimal || Total transaction amount - unstandardised currency |
|- | |- | ||
| currency || CHAR(3) || Currency of the transaction amount - usually in SGD or USD | | currency || CHAR(3) || Currency of the transaction amount - usually in SGD or USD | ||
|- | |- | ||
− | | | + | | converted value || Decimal || Total transaction amount - standardised in SGD |
|- | |- | ||
− | | reason_code_description || Alphanumeric || Description of the reason for each approved or rejected transaction by customer | + | | reason_code || Alphanumeric || A unique code tagged to each reason for each approved or rejected transaction made by customer |
+ | |- | ||
+ | | reason_code_description || Alphanumeric || Description of the reason for each approved or rejected transaction made by customer | ||
|- | |- | ||
| card_data1 || Integer || First 6 digits of customer’s card number - reveals details about the issuing bank and card type | | card_data1 || Integer || First 6 digits of customer’s card number - reveals details about the issuing bank and card type | ||
Line 77: | Line 88: | ||
|- | |- | ||
| contact_ip_country || Alphanumeric || IP country of the customer | | contact_ip_country || Alphanumeric || IP country of the customer | ||
+ | |- | ||
+ | | Bin [based on log10] || Integer || Bin number each merchant belongs to | ||
|} | |} | ||
<br> | <br> | ||
<small>''*Sample dataset shown in proposal, due to sensitivity of data''</small> | <small>''*Sample dataset shown in proposal, due to sensitivity of data''</small> | ||
==<div style="background: #DD597D; line-height: 0.3em; font-family:calibri; border-left: #CFCFCF solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Data Exploration and Preparation (In Progress)</strong></font></div></div>== | ==<div style="background: #DD597D; line-height: 0.3em; font-family:calibri; border-left: #CFCFCF solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Data Exploration and Preparation (In Progress)</strong></font></div></div>== |
Revision as of 20:25, 25 February 2018
Background | Data Source | Methodology |
---|
Metadata
Previously, we only have the transaction data of 2017 provided by RDP.
Moving on, we managed to obtain transaction data of 2016 as well.
Below are the definitions of common terms used in their business model:
MERCHANT - A merchant is a business, often a retailer, that operates online. Each merchant has appointed RDP to be its payment processor to handle online transactions between them and their customers.
CUSTOMER - A customer is an entity that makes a transaction with the merchant. For a transaction to be made, a customer must make contact with a merchant and provide their payment details (e.g. Credit card number) to the merchant through RDP’s payment processing gateway.
The following table shows the list of variables in the data and their associated description:
NAME | TYPE | DESCRIPTION |
---|---|---|
date_created | Date Time | Data and time at which the transaction was carried out between merchant and customer |
period | Integer | Month of the year the transaction was carried out between merchant and customer |
hour | Integer | Hour in a day the transaction was carried out between merchant and customer |
day | Integer | Day of the week the transaction was carried out between merchant and customer |
time | Time | Time at which the transaction was carried out between merchant and customer |
name | Alphanumeric | Name of merchant |
amount of money | Decimal | Total transaction amount - unstandardised currency |
currency | CHAR(3) | Currency of the transaction amount - usually in SGD or USD |
converted value | Decimal | Total transaction amount - standardised in SGD |
reason_code | Alphanumeric | A unique code tagged to each reason for each approved or rejected transaction made by customer |
reason_code_description | Alphanumeric | Description of the reason for each approved or rejected transaction made by customer |
card_data1 | Integer | First 6 digits of customer’s card number - reveals details about the issuing bank and card type |
card_data2 | Integer | Last 4 digits of customer’s card number |
contact_ip_address | Alphanumeric | IP address of the customer |
contact_ip_country | Alphanumeric | IP country of the customer |
Bin [based on log10] | Integer | Bin number each merchant belongs to |
*Sample dataset shown in proposal, due to sensitivity of data