Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
merchant:existing_merchant:selfcare_system:reporting [2019/02/21 10:31]
thiago123
merchant:existing_merchant:selfcare_system:reporting [2019/02/21 11:30]
Line 1: Line 1:
-====== Reporting ====== 
  
-~~TOC~~ 
- 
-\\ 
- 
-After logging on Selfcare system, access the "​**Reporting**"​ tab for the following features. 
- 
-\\ 
-===== Open Batch =====  ​ 
- 
-All the transaction performed by your terminals which were not settled yet can be found in the open batch. 
-The **Open Batch** report provides Merchants with the ability to: 
- 
-  * **I)** Search and list the transactions processed and still not settled for a terminal, or all terminals. 
-  * **II)** Export transactions at open batch to a CSV file. 
-  * **III)** Mark a set of transactions as "​Pending"​ before they are settled. 
-  - This  will prevent them from being settled until set to "​Ready"​. 
-  - Transactions cannot be altered from "​Ready"​ to "​Pending"​ after the terminal batch time.  ​ 
-  * **IV)** Mark a set of transactions as "​Void"​ before they are settled. 
-  - This will cause them to not be settled and moved to the closed batch at the settlement time. 
-  - A transaction cannot be voided after the terminal batch time. 
-  * **V)** Mark a set of transactions as "​Ready",​ instructing the payment gateway to settle this transactions. 
-  * **VI)** View general transactions'​ data. 
-  * **VII)** View a transaction'​s details. 
-  * **VIII)** Resend a cardholder'​s receipt copy.  
-  * **IX)** Reprint the merchant'​s or the cardholder'​s receipt copy. 
-  * **X)** And, depending on the Terminal'​s Acquirer and Enabled/ Allowed Features: 
-  ** **a)** Refund a transaction 
-  ** **b)** Perform a partial capture 
-  ** **c)** Create a secure card out of the cardholder details within the transaction 
-  ** **d)** Create a subscription out of the transaction'​s details if a secure card was already generated 
-  ** **e)** Add enhanced data to the transaction before settlement 
-  ​ 
-<WRAP 100%>  ​ 
-The Open Batch list is set to 10 transactions per page.  
-If the transactions found cannot fit on one page, the list will be spread between several pages and a page navigator will appear below the transactions'​ list, on the right side. 
-</​WRAP> ​ 
- 
-**Open Batch** 
-%selfcarereportingopenbatch-general 
- 
-\\ 
-==== Open Batch Search Filter Options ==== 
- 
-To search transactions,​ you can use many different filter options. Transaction data can be combined with filter that allow you to create matches based on quantity, amount, value match, ranges, among others. 
-Explore and learn more about what you can do with the search filters. 
- 
-**Search** 
-%selfcarereportingopenbatch-search 
- 
-\\ 
-==== Export transactions at open batch to a CSV file ==== 
- 
-Based on the result of your searches, you can generate a CSV report, exporting the data you desire, depending on the data available in your transactions. 
- 
-**Export to CSV** 
-%selfcarereportingopenbatch-exportcsv 
- 
-\\ 
-==== Mark a set of transactions as "​Pending",​ "​Ready"​ or "​Void"​ ==== 
- 
-A few actions can be performed for a set of transactions. To do this, select the desired transactions then choose the action by clicking in one of the available buttons on the left bottom side of your visible transaction list. 
- 
-**Change Status of Transaction Group** 
-%selfcarereportingopenbatch-changestatusoftransactiongroup 
- 
-\\ 
-==== Transactions Inidividual Management ==== 
- 
-Each transaction has its own status and details, therefore, you might need to take a closer look at them or treat them individually. 
-Clicking anywhere on a transaction line from open batch (except the Order ID - this opens the transaction details), the table expands that line with more information. 
- 
-**Transaction Line Details** 
-%selfcarereportingopenbatch-transactionline-details 
- 
-In case you want to know the action options for that transaction,​ just click at the end of each line on the "​**...**"​ option. A list of possible actions is going to be presented. 
- 
-**Transaction Actions** 
-%selfcarereportingopenbatch-transactionline-actions 
- 
-\\ 
-Each action represents a specific feature, which might or not be available depending on: 
-  * Transaction status (specific actions can only be applied to specific statuses) 
-  * User Permissions 
-  * Terminal features and settings 
-  * Terminal'​s Acquirer settings 
- 
-<WRAP 100% info> 
-In case you don't have access to one of the following features and want to kknow more about it, contact our suppor team. 
-</​WRAP>​ 
- 
-\\ 
-Below in can see a few examples for those actions. 
- 
-**Create a Secure Card from Transaction Details** 
-%selfcarereportingopenbatch-actions-securecard 
- 
-\\ 
-**Create a Subscription ​ from Transaction Details** 
-%selfcare-reporting-openbatch-actions-subscription 
- 
-\\ 
-**Add Enhanced Data to Transaction** 
-%selfcarereportingopenbatch-actions-enhanceddata 
- 
-\\ 
-**Perform Partial Capture of Transaction Value** 
-%selfcarereportingopenbatch-actions-partialcapture 
- 
-\\ 
-**Refund Transaction** 
-%selfcarereportingopenbatch-actions-refund 
- 
-\\ 
-**Void Transaction** 
-%selfcarereportingopenbatch-actions-void 
- 
-\\ 
-**Resend Cardholder Receipt Copy by Email** 
-%selfcarereportingopenbatch-actions-resendreceiptemail 
- 
-\\ 
-**Consult Sentinel Defend Events** 
-%selfcarereportingopenbatch-actions-sentineldefend 
- 
-\\ 
-===== Closed Batch =====  ​ 
- 
-The **Closed Batch** report provides Merchants with the ability to:  
- 
-  * **I)** View closed batches by day, on a terminal or all the merchant'​s terminals. 
-  * **II)** View transactions on a closed batch with general details. 
-  * **III)** Export transactions on a closed batch to a CSV file. 
-  * **IV)** View net totals. 
-  * **V)** Search transactions in closed batches - by transaction info, card details, custom fields or other options. 
-  * **VI)** View transaction details. 
-  * **VII)** Resend the cardholder receipt copies. 
-  * **VIII)** Refund older transactions which have already been settled. 
-  * **IX)** Print merchant or cardholder receipts copies. 
- 
-You can access the **Closed Batch** by clicking on the "​**Reporting**"​ tab: 
- 
-%closed_batch 
- 
-\\ 
-You can search for **settled (i.e. closed) transactions** in the "​**Find a Transaction**"​ tab by: Order ID (it's a unique transaction number given by the merchant; i.e. order reference number), unique reference (it's a unique transaction number attributed automatically to each transaction by %CompanyName system) or by amount range (the range of the transaction value). 
- 
-%close_batchs_2 
- 
-\\ 
-You can also click on the "​**Advanced Filter**"​ tab, where you will be able to broaden the search criteria by: Transaction Date, Operator, Card Types and Transaction Result (e.g approval, referral, decline, void) 
- 
-%advanced_closed_batch 
- 
-\\ 
-In closed batch you will be able to view all settlements for the terminal. The transactions are grouped by settlement date/time and the batch will show number and value of: sales per batch, refunds, voids as well as total deposits. 
- 
-To view the Batch transaction details simply click on the date of the settlement you wish to view. The batch transaction details include the transactions Time and Date, Order ID, Operator (this is the name of the person who processed the credit card details. It can also be an automatic payment), type of transaction,​ status, name of cardholder, securely masked card number, amount, and card type.  ​ 
- 
-Below the transactions in the batch you will also see Net Total which will be the sum of all complete transactions on the current page. 
- 
-%transaction_closed_batch 
- 
-\\ 
-Click on the transaction date/time field to see the individual transaction details, as per the screenshots below: 
- 
-%details_closed_batch 
- 
-\\ 
-The option to print the **Merchant Receipt** or the **Cardholder Receipt** is available. You can also resend the receipt to the merchant from here. 
- 
-It is possible to **refund** this transaction at this stage, if needed. Click on the "​Refund"​ button in the bottom right corner. 
- 
-A completed sale transaction can be refunded only by the operator who is granted permission to perform refunds. Refund controls are not displayed if the logged-on user does not have required permissions. 
- 
-A refund reason should be provided for each refund and refunded amount can be modified, however the refund amount can’t exceed original sale transaction amount. When the refund reason is entered and the amount checked/​modified,​ clicking on the "​Refund"​ button will create a new refund transaction,​ and this transaction will appear in the terminal Open Transactions list. Refunds can be cancelled at any time up until the Settlement time by marking the transaction as "​Void"​. The refund confirmation screen will appear if the operation was successful. New refund transactions will be settled during the nearest settlement process if it is marked as "​Ready"​. 
- 
-{gateway=helpdesk.globalone.me}{gateway=testhelpdeskglobaloneme.worldnettps.com}{gateway=docs.worldnettps.com}{gateway=testdocs.worldnettps.com}{gateway=helpdesk.nuvei.com}{gateway=testhelpdesknuveicom.worldnettps.com} 
- 
-===== Scheduled Report =====  ​ 
- 
-The **Scheduled Report** feature allows merchants to create their own reports, choosing the criteria used to generate the report, the data present as the result, and the periodicity and way in which the report should be delivered. 
- 
-**List of Reports** 
- 
-Merchant can define as many reports as they desire, with different configurations,​ for different needs. 
- 
-%merchant_selfcare_reporting_scheduleReport-list 
- 
-**Creating a Report** 
- 
-To create a report, the Merchant only needs to inform the settings and at the given time, the report is going to be generated and delivered as configured. 
- 
-%merchant_selfcare_reporting_scheduleReport-create 
-\\ 
- 
-  * **Report Info**: here you are going to inform the Report Name. 
-  * **Report Schedule**: the Run Report field allows you to inform the periodicity of the report (Daily, Weekly, Monthly). 
-  * **Delivery Methods**: only two methods allowed - FTP and E-mail - and both require their specific details. 
-  * **Report Builder**: here you can choose, among a set of fields, the data to be used when filtering your report'​s desired information. 
-  * **Report Columns**: those are the possible fields to appear in your report. 
- 
-{/gateway} 
- 
-\\ 
- 
-===== Account Updater =====  ​ 
- 
-The **Account Updater** report enables you to keep track of the updated Secure Cards in your Terminals, making possible: 
- 
-  * **I)** To track the changes made to the accounts associated to your Secure Cards. 
-  * **II)** Understand changes which may be causing transaction decline (based on statuses). 
-  * **III)** Export those "​updates"​ to a CSV file. 
-  * **IV)** See the amount of changes already updated to your Secure Card. 
- 
-This features allows you to filter your search by the card details, the provider of the Account Update service or the change type, as you can see in the next two images. 
- 
-**Account Updater Report - Search By Card** 
- 
-%account_updater_report_search-by-card 
- 
-\\ 
-**Account Updater Report - Advanced Filter** 
- 
-%account_updater_report_advanced-filter 
- 
-\\ 
-**Account Updater Report - Search Result** 
- 
-Following the result of the report, when applied any search, you would be able to see the list of changes already registered by the Account Updater feature, as shown in the next image. 
-Among the data informed, you are going to find the provider or the account update service (vendor), the secure card and card details (card reference, merchant holder, terminal holder, merchant reference, card, masked card number, expiration date, cardholder),​ the card update details (las update date and status) and payment details (total and volume of sales, refunds, voids and total deposit on that secure card). 
- 
-%account_updater_report_result 
- 
-\\ 
-It's important to understand that, besides the informative function, the Merchant should understand what each status mean and if they have any impact in its future transactions. 
- 
-**Statuses for Each Registered Update** 
- 
-<​searchtable>​ 
-^ **NAME** ^ **DESCRIPTION** ^  
-| VALID | No updates performed. SC details are still valid. | 
-| UPDATE | Account number or account number, plus expiration date were updated. | 
-| EXPIRY | Just expiration date was updated. | 
-| CONTACT_CLOSED | Account was closed (Secure Card invalid). Merchant should contact the cardholder. | 
-| UNKNOWN | Account number could not be found. SC details are not valid anymore. | 
-| IN_PROCESS | The updating of this SC details is still in progress. It will change to one of the other statuses as soon as it's finished. | 
-| CONTACT | Merchant should contact the cardholder. | 
-| PARTICIPATING | No Match from participating bin issuer (not sure what merchant should do). | 
-| NON_PARTICIPATING | No Match from non-participating bin issuer (I think this card is not eligible for account updater). | 
-| UNDEFINED | VAU or ABU returned status_unknown. | 
-| ER_000101 | Error while updating: Non-numeric Account Number. The SC Details are not valid anymore. | 
-| ER_000102 | Error while updating: Account Number is not in BIN Range. The SC Details are not valid anymore. | 
-| ER_000103 | Error while updating: Invalid Expiration Date. The SC Details are not valid anymore. | 
-| ER_000104 | Error while updating: Merchant Not Registered. The SC Details are not valid anymore. | 
-| ER_000122 | Error while updating: Un-registered Sub-merchant. The SC Details are not valid anymore. | 
-| ER_UNSUPPORTED_RESPONSE_CODE | Error while updating: Unsupported response code from the updater service. The SC Details are not valid anymore. In this case, you should contact the Payment Gateway Support team to open an investigation to see what the response code is, and update possible valid responses. | 
-</​searchtable>​ 
- 
-{gateway=helpdesk.globalone.me}{gateway=testhelpdeskglobaloneme.worldnettps.com}{gateway=helpdesk.nuvei.com}{gateway=testhelpdesknuveicom.worldnettps.com} 
- 
-===== ACH ===== 
- 
-In case you are using a terminal which can perform ACH Transactions,​ a separated report option is made available under **Reporting > ACH**, with those transactions,​ as you can see at the menu on the following images. 
- 
-Each report focuses on a specific transaction state, such as: 
- 
-==== Pending Transactions ==== 
- 
-This report presents all the ACH pending transactions for the used terminal: 
-  * **I**. Grouped by **Date**. 
-  * **II**. With a link (click on the date) to show the detailed list of transactions on that date. 
-  * **III**. Detailed in five summarizing lines for the transactions performed on that date: 
-  - **a)** The first top line (aligned with the date) represents the sum of the remaining 4 lines (that'​s why its SEC Code column is always empty). 
-  - **b)** Each of the four remaining lines represents the total volumes for transactions of each one of the Sec Codes - CCD, PPD, TEL and WEB (refer **[[developer:​api_specification_ach_jh|API Specification - ACH JH]]** to know a little bit more about SEC Codes). Additionally,​ a link is also provided for each SEC Code to the list of transactions with that code on that date. 
-  - **c)** Additionally,​ each line also groups the transactions as **Sales**, **Refunds** and **Voids** by quantity, represented by the value between "​**()**",​ followed by its total resulting amount. The **Total Deposit** totalizes those three types (Sales - Refunds - Voids). 
- 
-%merchant_selfcare_report_ach_pending 
- 
-\\ 
-==== Submitted Transactions ==== 
- 
-This report presents all the ACH submitted transactions for the used terminal: 
-  * **I**. Grouped by **Date**. 
-  * **II**. With a link (click on the date) to show the detailed list of transactions on that date. 
-  * **III**. Detailed in five summarizing lines for the transactions performed on that date: 
-  - **a)** The first top line (aligned with the date) represents the sum of the remaining 4 lines (that'​s why its SEC Code column is always empty). 
-  - **b)** Each of the four remaining lines represents the total volumes for transactions of each one of the Sec Codes - CCD, PPD, TEL and WEB (refer **[[developer:​api_specification_ach_jh|API Specification - ACH JH]]** to know a little bit more about SEC Codes). Additionally,​ a link is also provided for each SEC Code to the list of transactions with that code on that date. 
-  - **c)** Additionally,​ each line also groups the transactions as **Sales**, **Refunds** and **Voids** by quantity, represented by the value between "​**()**",​ followed by its total resulting amount. The **Total Deposit** totalizes those three types (Sales - Refunds - Voids). 
- 
-%merchant_selfcare_report_ach_submitted 
- 
-\\ 
-==== Settled Transactions ==== 
- 
-This report presents all the ACH settled transactions for the used terminal: 
-  * **I**. Grouped by **Date**. 
-  * **II**. With a link (click on the date) to show the detailed list of transactions on that date. 
-  * **III**. Detailed in five summarizing lines for the transactions performed on that date: 
-  - **a)** The first top line (aligned with the date) represents the sum of the remaining 4 lines (that'​s why its SEC Code column is always empty). 
-  - **b)** Each of the four remaining lines represents the total volumes for transactions of each one of the Sec Codes - CCD, PPD, TEL and WEB (refer **[[developer:​api_specification_ach_jh|API Specification - ACH JH]]** to know a little bit more about SEC Codes). Additionally,​ a link is also provided for each SEC Code to the list of transactions with that code on that date. 
-  - **c)** Additionally,​ each line also groups the transactions as **Sales**, **Refunds** and **Voids** by quantity, represented by the value between "​**()**",​ followed by its total resulting amount. The **Total Deposit** totalizes those three types (Sales - Refunds - Voids). 
- 
-%merchant_selfcare_report_ach_settled 
- 
-\\ 
-==== Closed Transactions ==== 
- 
-This report presents all the ACH closed transactions for the used terminal: 
-  * **I**. Presenting an option to search the transaction based on a simple filter. 
-  * **II**. Grouped by **Date**. 
-  * **III**. With a link (click on the date) to show the detailed list of transactions on that date. 
-  * **IV**. Detailed in five summarizing lines for the transactions performed on that date: 
-  - **a)** The first top line (aligned with the date) represents the sum of the remaining 4 lines (that'​s why its SEC Code column is always empty). 
-  - **b)** Each of the four remaining lines represents the total volumes for transactions of each one of the Sec Codes - CCD, PPD, TEL and WEB (refer **[[developer:​api_specification_ach_jh|API Specification - ACH JH]]** to know a little bit more about SEC Codes). Additionally,​ a link is also provided for each SEC Code to the list of transactions with that code on that date. 
-  - **c)** Additionally,​ each line also groups the transactions as **Sales**, **Refunds** and **Voids** by quantity, represented by the value between "​**()**",​ followed by its total resulting amount. The **Total Deposit** totalizes those three types (Sales - Refunds - Voids). 
- 
-%merchant_selfcare_report_ach_closed 
- 
-\\ 
-In case you desire to see more details or simple look for a specific transaction from a specific data, whenever you click on a date you are going to be presented to the image below, and if you click on the date link once more, te transaction details are presented. 
- 
-%merchant_selfcare_report_ach_batchdetails 
- 
-\\ 
-==== Returned Transactions ==== 
- 
-This report presents all the ACH returned transactions for the used terminal: 
-  * **I**. Presenting two search options for transactions:​ simple and advanced - with filters. 
-  * **II**. Grouped by **Date**. 
-  * **III**. With a link (click on the date) to show the detailed list of transactions on that date. 
-  * **IV**. Detailed in five summarizing lines for the transactions performed on that date: 
-  - **a)** The first top line (aligned with the date) represents the sum of the remaining 4 lines (that'​s why its SEC Code column is always empty). 
-  - **b)** Each of the four remaining lines represents the total volumes for transactions of each one of the Sec Codes - CCD, PPD, TEL and WEB (refer **[[developer:​api_specification_ach_jh|API Specification - ACH JH]]** to know a little bit more about SEC Codes). Additionally,​ a link is also provided for each SEC Code to the list of transactions with that code on that date. 
-  - **c)** Additionally,​ each line also groups the transactions as **Sales**, **Refunds** and **Voids** by quantity, represented by the value between "​**()**",​ followed by its total resulting amount. The **Total Deposit** totalizes those three types (Sales - Refunds - Voids). 
- 
- 
-%merchant_selfcare_report_ach_returned 
- 
-\\ 
-==== Transactions'​ Re-presentations ==== 
- 
-This report presents all the ACH re-presentrations of returned transactions for the used terminal: 
-  * **I**. Grouped by **Date**. 
-  * **II**. With a link (click on the date) to show the detailed list of transactions on that date. 
-  * **III**. Detailed in five summarizing lines for the transactions performed on that date: 
-  - **a)** The first top line (aligned with the date) represents the sum of the remaining 4 lines (that'​s why its SEC Code column is always empty). 
-  - **b)** Each of the four remaining lines represents the total volumes for transactions of each one of the Sec Codes - CCD, PPD, TEL and WEB (refer **[[developer:​api_specification_ach_jh|API Specification - ACH JH]]** to know a little bit more about SEC Codes). Additionally,​ a link is also provided for each SEC Code to the list of transactions with that code on that date. 
-  - **c)** Additionally,​ each line also groups the transactions as **Re-initiation First Date** and **Re-initiation Second Date** by quantity, represented by the value between "​**()**",​ followed by its total resulting amount. 
- 
-%merchant_selfcare_report_ach_representments 
- 
-{/gateway} 
- 
-\\ 
-===== Customers ===== 
-  ​ 
-The "​**Customers**"​ section under the **Reporting** tab enables merchants to view and manage "​**Outstanding Subscriptions with Payment Due**" and "​**Expiring Secure Cards**"​. 
- 
-%reporting_customers 
-\\ 
- 
-The "​**Subscription**"​ option shows all the details related to outstanding subscriptions. ​ 
- 
-%outstanding_subscriptions 
- 
-%2outstanding_subscriptions-filters 
- 
-%3outstanding_subscriptions-csv 
- 
-It also provides the option to filter and search those subcriptions and export the details on this report to CSV. 
-\\ 
- 
-The "​**Expiring Secure Cards**"​ shows only the secure cards which are going to expire within the 2 months. This section includes the following details: Card type, Merchant Ref, Card Number, Cardholder Name and Expiry Date. You can search for expiring secure cards by "​Merchant Reference"​ or by "Month Range" for up to 12 months. 
- 
-It is possible also to export the details to CSV, if needed. 
- 
-%expiring_secure_cards 
-\\ 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International