migrating to the new reporting platform - online … · migrating to the new reporting...

Title Page

Migrating to the New Reporting Platform

Guide for Business Center Users

August 2016

CyberSource Corporation HQ | P.O. Box 8999 | San Francisco, CA 94128-8999 | Phone: 800-530-9095

CyberSource Contact Information

For general information about our company, products, and services, go to http://www.cybersource.com.

For sales questions about any CyberSource Service, email [email protected] or call 650-432-7350 or 888-330-2300 (toll free in the United States).

For support information about any CyberSource Service, visit the Support Center at http://www.cybersource.com/support.

Copyright© 2016 CyberSource Corporation. All rights reserved. CyberSource Corporation ("CyberSource") furnishes this document and the software described in this document under the applicable agreement between the reader of this document ("You") and CyberSource ("Agreement"). You may use this document and/or software only in accordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the information contained in this document is subject to change without notice and therefore should not be interpreted in any way as a guarantee or warranty by CyberSource. CyberSource assumes no responsibility or liability for any errors that may appear in this document. The copyrighted software that accompanies this document is licensed to You for use only in strict accordance with the Agreement. You should read the Agreement carefully before using the software. Except as permitted by the Agreement, You may not reproduce any part of this document, store this document in a retrieval system, or transmit this document, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written consent of CyberSource.

Restricted Rights LegendsFor Government or defense agencies. Use, duplication, or disclosure by the Government or defense agencies is subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and in similar clauses in the FAR and NASA FAR Supplement.

For civilian agencies. Use, reproduction, or disclosure is subject to restrictions set forth in subparagraphs (a) through (d) of the Commercial Computer Software Restricted Rights clause at 52.227-19 and the limitations set forth in CyberSource Corporation's standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States.

TrademarksCyberSource, The Power of Payment, CyberSource Payment Manager, CyberSource Risk Manager, CyberSource Decision Manager, CyberSource Connect, Authorize.Net, and eCheck.net are trademarks and/or service marks of CyberSource Corporation. All other brands and product names are trademarks or registered trademarks of their respective owners.

2

http://www.cybersource.com

mailto:[email protected]

http://www.cybersource.com/support/

CO

NT

EN

TS

Contents

Recent Revisions to This Document 5

About This Guide 6

Audience and Scope 6

Conventions 6

Note and Important Statements 6

Text and Command Conventions 7

Customer Support 7

Chapter 1 Introduction 8

Reporting Terms 8

Frequently Asked Questions 9

General 9

Chapter 2 Analytics 14

Authorizations 15


Captures 15


Settlements 16

Chargebacks 16

Funding 17

Net Funding 17

Chapter 3 Reports 18

Report Comparisons 19

Report Generation Times 23


Retired Reports 26

Migrating to the New Reporting Platform | August 2016 3

Contents

Using Reports 27

One-Time Reports 29

Creating a Report 29

Downloading Reports 30

Editing Reports 31

Deleting Reports 31

Managing Groups 32

Appendix A Report Field Mappings 33

Chargeback Detail Report 33

Detail Deposit Report 34

Summary of Fees Report 35

Subscription Payment Exception Report 36

Invoice Summary Report 38

Appendix B Report Field Definitions 39

Appendix C Report Fields Available 47

Transaction Request Report 48

Payment Batch Detail Report 51

Transaction Exception Detail Report 54

Processor Events Detail Report 57

Invoice Summary Report 59

Processor Settlement Detail Report 60

Funding Detail Report 63

Aging Detail Report 66

Chargeback and Retrieval Detail Report 69

Deposit Detail Report 71

Fee Detail Report 72


RE

VIS

ION

S

Recent Revisions to This Document

Release Changes

August 2016 This revision contains only editorial changes and no technical updates.

July 2016 Added report field definitions.

Added tables that show which fields are available in each report.

Added report mapping information.

May 2016 Added information for creating one-time reports.

Added Appendix with mapping tables for report field names.

April 2016 Updated information on Payment Batch Summary Report.

March 2016 Updated release dates for reports.

February 2016 Updated release dates for reports.

January 2016 Initial release of document.


AB

OU

T G

UID

E

About This Guide

Audience and Scope

This guide is written for reporting users of the Business Center. This guide describes how to use the new analytics and reports in the upcoming release of a new Business Center and reporting engine. This migration guide will also describe the differences between the original Business Center reports and the new Business Center reports.

Conventions

Note and Important Statements

Note

A Note contains helpful suggestions or references to material not contained in the document.

Important

An Important statement contains information essential to successfully completing a task or learning a concept.


About This Guide

Text and Command Conventions

Customer Support

For support information about any CyberSource service, visit the Support Center:

http://www.cybersource.com/support

Convention Usage

bold Field and service names in text; for example:

Include the ics_applications field.

Items that you are instructed to act upon; for example:

Click Save.

monospace XML elements.

Code examples and samples.

Text that you enter in an API environment; for example:

Set the davService_run field to true.


http://www.cybersource.com/support/

Migrating to the New Reporting Platform | August 2016

HA

PT

ER

C

1
Introduction
This migration guide is designed to help merchants who are affected by the July 2016 report migration of a subset of Business Center reports from the original Business Center to the new Business Center. Specifically, it will answer questions about the differences between the original reports and the new reports. This guide covers reports affected by the July 2016 migration, in addition to reports that are not affected by the migration, including Capture Analytics, the Transaction Detail Report, and the Payment Batch Detail Report.

Reporting Terms

The following reporting terms are used in this guide:

Note

None of the reports in the Downloadable Reports section of the Business Center will change. Only the reports listed in this guide will be changing. Examples of reports in the Downloadable Reports section are the Transaction Detail Report and the Payment Batch Detail Report.

Important

By early August, Account level users will be able to create their own reports that combine data across all the merchants in their account. Account level users will be able to create reports for themselves only; they will not be able to create reports for their merchants.

Table 1 Reporting Terms

Term Definition

Group A group is a named group of MIDs that can be used to aggregate data in the Analysis screens. Account-level users may create groups. Groups are meant to be a more flexible replacement for the original Business Center Hierarchy feature. For each original hierarchy, we have created a group on behalf of users in the new Business Center. Account level users may use groups to segregate data in the analytics screens.

8

Chapter 1 Introduction

Frequently Asked Questions

GeneralThe questions below cover general questions about the new reporting interface and migration.

Can partners use the new Business Center?As of today, the new Business Center does not support partners. The Reporting teams are working on extending the Custom Reports and Analytics features to support the partner use case.

When will the new Business Center be localized?The New Business Center will be localized prior to sunset of today's Business Center.

How can I access the new features?Users will see two new links in the Reports section of the Business Center:

New Analytics

New Reports

These links will open the new Business Center in a new window, and the user will be automatically signed in.

Custom Detail Report Subscription

A custom detail report is a report subscription that users can create to run at particular intervals (daily, weekly, or monthly). The report defined by the subscription will be generated at the specified intervals until the user deletes the subscription. Users may download their reports in the reports module. The fields in the detail reports can be customized. The reports are available in XML or CSV format. Merchants and Account levels users can create detail reports. All original Business Center roles and permissions apply to the new Business Center reporting.

One-Time Custom Detail Report

A one-time custom detail report is similar to a custom detail report, except that it will run one time, covering a period of time in the past. A one-time report may cover a period of time of up to 31 days. One-Time custom detail reports are available for download in the Available Reports screen after they have been generated.

Analysis Screen An analysis screen is an on-demand report that contains some summary data and some analytical content, such as trends by payment method or currency.

Table 1 Reporting Terms

Term Definition



Which original Business Center reporting features are not yet available?Beginning with the late May 2016 release, the following features are not available:

Users cannot drill down from the Payment Activity Summary to the Purchase and Refund Details (PRD) report because the PRD remains in the original Business Center for the time being.

Some of the reports that were available on-demand are now available only as scheduled detail reports. To receive these reports, you must create a detail report subscription.

Which browsers are supported?Chrome, Internet Explorer 10, and Firefox are currently supported.

What do the new screens look like?Figure 1 Authorizations Analytics Screen



Figure 2 Captures Analytics Screen



Figure 3 Net Expected Funding Screen

Figure 4 Available Reports Screen



Figure 5 Create Report Screen



HA

PT

ER

C

2
Analytics
Analytics screens display the following data:

Gateway data:

Authorizations

Captures

Reconciliation data (for acquiring merchants only):

Processor settlements

Chargebacks

Funding

Net Expected Funding

All of the Analytics data covers midnight to midnight Coordinated Universal Time (UTC) in the selected date range. Data in the Analytics screen is available for download in XML, CSV, or JSON format. As of July 2016, the Analytics screens contain between four and six months of data.

Merchants and account level users (SSO) can use the Analytics feature. Merchants can access data related to their particular MID. Account level users (SSO) can access data related to one of their MIDs, or all of their MIDs. Account level users may also create Groups, and then access data by Group.

Users with View Reports permissions can use the Analytics feature.

Important

Analytics data is only available for the previous day and earlier. Same-day data is not available at this time.

14

Chapter 2 Analytics

Authorizations

The Authorizations panel shows authorizations in a given period. An authorization, provided by the customer's card issuing bank, confirms the cardholder's ability to pay. This data is available to all users with the appropriate permissions.

The Authorizations panel includes the following types of services:

ics_auth


Does the Authorizations panel include authorization reversals?No, it does not include authorization reversals.

Does the Authorizations panel include zero dollar or one dollar authorizations?Yes, the authorizations screen currently includes zero and one dollar authorizations.

Can I see my raw (203, 204) authorization decline codes in the Authorizations panel?No, this information is not available today in the Authorizations panel. The raw decline codes will be available in the Custom Reports feature.

What about Payer Authorizations?The Authorizations panel does not include payer authorization data.

What if I want to distinguish between my ics_auth transactions, and my ics_auth/ics_bill transactions?The Authorizations panel is not currently capable of distinguishing between these types of transactions.

Captures

The Capture panel displays captures and refunds for a given period. A capture (sometimes known as settlement) request instructs your processor to initiate a funds transfer between the customer's credit card account and your checking account. A capture can be a sale or a refund. This data is available to all users with appropriate permissions.

Captures are the following types of services:


Chapter 2 Analytics

ics_bill

ics_sale

ics_refund

Types of transactions that will be included in the Capture screen:

Credit and debit

Checking, savings, corporate checking, etc

AliPay transactions

Online bank transfers


Why are you using the term "capture" instead of "settlement"?The term capture is used here to distinguish it as gateway data, which is a transaction sent through the CyberSource gateway initiated by the merchant. We use the term settlement to refer reconciliation data, which is a transaction that the processor has indicated that it plans to settle. The capture screen includes all sales and refunds, whether or not they have been batched.

Settlements

The Settlements panel displays transactions received by a processor on behalf of the merchant that the consumer's bank has agreed to fund. Settlement data is only available to merchants using a processor from which Cybersource receives financial data (currently, this is GPN and AliPay).

In the case of GPN, it is expected that settlement and funding data will always be the same. As data from other processors is available in this screen, that will not always be the case.

Chargebacks

The Chargebacks panel displays chargebacks reported by the processor in a given time period. Chargeback data is only available to merchants using a processor from which Cybersource receives financial data (currently, this is GPN).


Chapter 2 Analytics

Funding

The Funding panel displays transactions the processor plans to fund. Funding data is only available to merchants using a processor from which Cybersource receives financial data (currently, this is GPN and AliPay).

Net Funding

The Net Funding panel acts like a merchant statement and recaps all purchases and refunds, as well as fees and adjustments processed for a merchant entity during a particular date range, resulting in an expected funding amount. Fees will show on this report for the date on which they are assessed (daily or monthly), which may or may not be the same date that the transactions were processed. Please refer to your CyberSource merchant processing agreement for specific details regarding the timing of your merchant fees.

Net funding data is only available to merchants using a processor from which Cybersource receives financial data (currently, this is GPN and AliPay).



HA

PT

ER

C

3
Reports
Custom Report subscriptions enable users to create and manage their own reports.

A report subscription is like a template that describes the attributes of a report:

Report name

Report type

Start time

Frequency

Format

Fields

The following reports are available today to all users with report download permissions.

Transaction Request Report - Gateway (CyberSource) data for all transaction requested in the given interval.

Payment Batch Detail Report - All transactions that were batched to the processor in the given interval.

Transaction Exception Detail Report - All gateway and processor exceptions in the given interval.

Invoice Summary Report - List of billable services provided by CyberSource to a merchant.

The following reports are available only to acquiring users (as of May 2016, this is GPN and AliPay):

Processor Settlement Detail Report - All transactions that settled with the processor. This can include positive (capture) and negative (credit) submissions.

Funding Detail Report - All transactions that were funded in the given interval.

Aging Detail Report - All settled transactions that have not been funded, listed by age.

Chargeback And Retrieval Detail Report - All chargeback and retrieval transactions that have been reported from the processor.

Deposit Detail Report - All funds transfers posted to the bank account.

18

Chapter 3 Reports

Report Comparisons

The table below compares the reports in the current Business Center to the reports in the new Business Center. You can use this table to determine which new reports to subscribe to.

Table 2

Business Center Report

New Business Center Report

Available Formats

Notes

Online Reports

Subscription Payment Exception Report

Transaction Exception Detail Report

Downloadable via XML, CSV

The user can create a Transaction Exception Detail Report in the Reports module of the New Business Center and add subscription exception related fields. See "Creating a Report," page 29 for information on how to create a report.

Invoice Summary Report



The user can create an Invoice Summary Report in the Reports module of the New Business Center. See "Creating a Report," page 29 for information on how to create a report.

Payment Batch Summary Report

N/A N/A Remains in the Business Center, but not longer available in XLS, PDF, and XML

Merchant Account Reports

Payment Activity Summary

Analytics: Net Funding screen

Available in the UI, or downloadable in XML, CSV, or JSON

Transfer Log Custom Reports: Deposit Detail Report


The user can create an Deposit Detail Report in the Reports module of the New Business Center. See "Creating a Report," page 29 for information on how to create a report.


Chapter 3 Reports

Summary of Fees No exact replacement; transaction level fees can be found in Fee Detail Report


The user can create an Fee Detail Report in the Reports module of the New Business Center. See "Creating a Report," page 29 for information on how to create a report.

For a summary of fees, the user may view the Net Funding screen in the Analytics module.

Chargeback and Representment Summary

Custom Reports: Chargeback and Retrieval Detail Report

Analytics: Chargebacks screen


For a summary of chargebacks, the user may view the Net Funding screen in the Analytics module.

Chargeback and Representment Details



The user can create an Chargeback and Retrieval Detail Report in the Reports module of the New Business Center. See "Creating a Report," page 29 for information on how to create a report.

Chargeback and Representment Financial Details




Retrieval Request Details




Table 2



Available Formats

Notes


Chapter 3 Reports

Authorization Analysis

Analytics: Authorization screen


Chargeback Analysis

Analytics: Chargebacks screen


Capture Detail Report

As announced in September 2015, CyberSource officially discontinued support for the Capture Detail report in March 2016.

The suggested is the new Capture Detail Report, which is found in the Downloadable Reports section of the new Business Center.

If the user would like to see a summary of captured transactions by payment type and currency, this information can also be found in the Analytics module of the New Business Center, in the Captures panel. See "Captures," page 15.

Table 2



Available Formats

Notes


Chapter 3 Reports

Authorization Detail Report

As announced in September 2015, CyberSource officially discontinued support for the Capture Detail report in March 2016.

The suggested is the new Authorization Detail Report, which is found in the Downloadable Reports section of the new Business Center.

If the user would like to see a summary of authorized transactions by payment type and currency, this information can also be found in the Analytics module of the New Business Center, in the Captures panel. See "Authorizations," page 15.

Table 2



Available Formats

Notes


Chapter 3 Reports

Report Generation Times

The table below shows the times and time zones for report generation in the new Business Center.


Who can use custom reports?Merchant and Account level users can use the Custom Reports feature to download reports, and to create, edit, or delete subscriptions. Account level users (SSO) may also download the reports that their MIDs have created. Users with View/Download Reports permissions can use the Custom Reports feature.

What date range do the reports cover?With the July 2016 release, the Analysis and Detail Reports will provide access to at least four months of historical data, including:

Gateway data such as transactions and capture

Financial reconciliation data for merchants using GPN for processing

What is the difference between report date, batch date, and request date?The report date is the day the report was generated. The batch date time stamp indicates when batching services processed captures and refunds. The request date time stamp indicates when ICS services processed captures and refunds. Time stamp representation

Table 3

Report Type Time and Time Zone of Data Consumption

Time and Time Zone Period Covered

Report Available By Time and Time Zone

Reconciliation Analytics 07:00:00 - 19:30:00 Pacific

00:00:00 - 23:59:59 GMT

Shortly after data consumption

Custom Gateway Reports 24/7 Customizable 6 hours after report start time

Custom Reconciliation Reports

07:00:00 - 19:30:00 Pacific

00:00:00 - 23:59:59 Pacific

6 hours after report start time

Note

Account level users may not create reports on behalf of their merchants. This is a feature that will be delivered in the future.


Chapter 3 Reports

is ISO 8601 compliant, and follows the YYYY-MM-DDThh:mm:ssZ format. The default time zone is GMT.

Which reports are discussed in this guide?To ensure a smooth transition between the original reporting interface and the new reporting interface, we compare reports from the two interfaces in this guide. The following reports are covered in this guide:

Gateway reports

Payment Batch Summary Report

Invoice Summary

Authorization Analysis

Subscription Payment Exception

Merchant Account reports

Payment Activity Summary

Transfer Log

Chargeback and Representment Detail

Summary of Fees

Chargeback and Representment Summary

Chargeback Analysis

Retrieval Request Detail

Which original reporting features are not yet available?As of the July 2016 release, the following features are not available:

Users cannot drill down from the Payment Activity Summary to the Purchase and Refund Details (PRD) report because the PRD remains in the original Business Center for the time being.

Some of the reports that were available on-demand are now available only as scheduled detail reports. To receive these reports, you must create a detail report subscription. These reports are:

Transfer log

Chargeback and Representment Detail Report

Summary of Fees

Retrieval Request Detail Report



What report fields can I add to a custom report?Please refer to "Report Fields Available," page 47, which contains a list of available fields in each report.


Chapter 3 Reports

Where can I find field report descriptions?Please refer to "Report Field Definitions," page 39 for field descriptions.

Can an account level user create a report?No. This functionality is not currently available. This feature will be available to account level users by early August.

Can custom reports be downloaded programmaticly?At this time, the reports cannot be downloaded programmaticly. This feature will be added at a later date.

Can I filter a custom report, to show, for example, only authorizations that were "card declined"?No. This functionality is not currently available. This feature will be added in the future.

Is there a limit to the size of a generated report?The report can be any size, but may take more time if the file is very large.

How soon will my generated report be ready?The generated report will be available within 6 hours of the report start time.

If I schedule a daily report to begin at midnight Pacific time, exactly which transactions will be included in the report?The report will contain transactions in the 24 hour period between midnight and midnight Pacific time.

Can the rows of a detail report be summed up for me?No. This functionality is not currently available. This feature will be added in the future.

Can I see the card product used for a transaction – for example, credit, debit, gift?No. This functionality is not currently available.

Can merchants be auto-subscribed to reports when they are onboarded?No. This functionality is not currently available. This feature will be added in the future.

Can partners or account level users do mass report subscriptions for their child entities?No. This functionality is not currently available. This feature will be added in the future.

Can I see the raw issuer decline codes in my reports?No. This functionality is not currently available. This feature will be added in the future.


Chapter 3 Reports

Can I see BIN data in my reports?No. This functionality is not currently available.

Can I change the timezone in which my transactions are reported?No. This functionality is not currently available. This feature will be added in the future.

Can I clone a report and make a new report by modifying the cloned report?No. This functionality is not currently available.

Is there an audit trail so that I can see which user has modified a report and how?No. This functionality is not currently available.

How can I identify declined authorizations in my reports?In the Transaction Request Report, authorizations will be recorded in the ApplicationName field as "ics_auth". If the auth was declined, the value in the RCode field will be "0". Additional information related to the decline can be found in the RFlag and the RMsg fields.

How to interpret the rFlag for an auth?See https://www.cybersource.com/developers/other_resources/quick_references/reply_flags/ for more information.

Retired Reports

Table 12 below lists the reports that will not be available in the new Enterprise Business Center.

Table 4 Retired Reports

Report ID Report Name

4 Payment Transaction Analysis Report

5 Payment Order Analysis Report

6 Risk Score Distribution Report

Note This report will be removed from the Online Reports section, but can still be found under Decision Manager.

18 Payment Amount Distribution Report

19 Payment Volume Distribution Report (by Date)


https://www.cybersource.com/developers/other_resources/quick_references/reply_flags/

https://www.cybersource.com/developers/other_resources/quick_references/reply_flags/

Chapter 3 Reports

Using Reports

Reports provide information on your transactions and can be customized by adding fields in addition to those that are required in the report. Reports run at an established frequency and can be downloaded. The following base reports are available:

Transaction Request Report—Gateway (CYBS) data for all transactions requests in the given interval. Merchants will use this report to audit their logs and enrich their Analytics data.

20 Payment Volume Distribution Report (by Hour)

30 Profile Performance Report

33 Order Conversion Summary Report

34 Profile Performance Comparison Report

35 Replay Results Report

36 Queue Distribution Report

37 Queue Age Report

38 Queue Activity Report

39 Queue Conversion Summary Report (Queue performance statistics can be found in the Queue Statistics Report under Decision Manager)

48 Profile-Rule Performance Report

51 Funding Statement Report

53 Batch Files Daily Summary Report (batch upload)

55 Deposit Summary Report (Domestic)

56 Deposit Detail Report (Domestic)

57 Chargeback Detail Report

58 Retrieval Request Report

60 Chargeback Statistics Report

61 Interchange Statistics Report

62 Retrieval Request Statistics Report

83 Interchange Qualification Analysis

85 Payment Exception Details Report

86 Pinless Debit Returns Detail Report

87 Merchant Status Report

Table 4 Retired Reports (Continued)

Report ID Report Name


Chapter 3 Reports

Batch Detail Report—All transactions that were batched to the processor in the given interval. Merchants will use this report to monitor the batch submission process and help predict their cash flow/funding timing.

Payment Exception Detail Report—All gateway and processor exceptions in the given interval. This report will be used by merchants to identify any exception errors or data mismatches across Gateway and Processor submissions.

Processor Settlement Detail Report—All transactions that settled with the processor. This can include positive (capture) and negative (credit) submissions. Merchants will use this report to manage their entitlement/commerce/CSR systems, including product fulfillment.

Processor Events Detail Report—All events provided by the processor regarding the transaction life cycle. This report is only available to merchants who use Global Payments as their processor, and who use the Merchant Account Reports in the original Business Center. Merchants will use this report to manage their entitlement/commerce/CSR systems to keep the latest information regarding the transaction status.

Funding Detail Report—All transactions that were funded in the given interval. This report is only available to merchants who use Global Payments as their processor, and who use the Merchant Account Reports in the original Business Center. Merchants will use this report to reconcile the transactions activity with the funding deposits from the processor.

Processor Fee Detail Report—All Processor Fee details from the processor funding details. Merchants will reconcile this with their processor contract pricing and funding detail reports.

Aging Detail Report—All settled transactions that have not been funded to be reported by age. This report is only available to merchants who use Global Payments as their processor, and who use the Merchant Account Reports in the original Business Center. Merchants require this information to ensure they can track those transactions they are expecting payment.

Chargeback And Retrieval Detail Report—All chargeback and retrieval transactions that have been reported from the processor. This report is only available to merchants who use Global Payments as their processor, and who use the Merchant Account Reports in the original Business Center. Merchants will use this report to manage chargeback and retrievals and measure their risk performance metrics.

Deposit Detail Report—The deposit detail report will list all funds transfers posted to the bank account. This report is only available to merchants who use Global Payments as their processor, and who use the Merchant Account Reports in the original Business Center.

Invoice Summary Report—List of billable services provided by CyberSource to a merchant.


Chapter 3 Reports

One-Time ReportsA one-time custom detail report is similar to a custom detail report, except that it will run one time, covering a period of time in the past. A one-time report may cover a period of time of up to 31 days. One-Time custom detail reports are available for download in the Available Reports screen after they have been generated. One Time reports will be given a report date of the most recent date the report covers. For example, a Transaction Request Report that covers from 4.1.2016 to 4.15.2016 will be given a report date of 4.15.2016. To find a one-time report, you can use the keyword search for Available Reports or sort by frequency.

Creating a ReportWhen you select a report type, required fields are automatically included. You can add fields to the report as necessary.

To create a report:

Step 1 On the Business Center home page, click Reports.

Step 2 Enter a report name.

Step 3 From the Frequency drop-down menu, choose the interval at which the report is to be generated. The options are:

One-Time

Daily

Weekly

Monthly

Step 4 From the Report Type drop-down menu, choose a report.

Step 5 From the Report Start Time drop-down menus, choose the time of day for the reports to be generated, and choose the time zone. If you are creating a one-time report, select a date range in the past for which you want data.

Step 6 Choose a report format: XML or CSV.

Step 7 Under Available Fields, select the additional fields that you want to include in the report, and click Add to move them to Selected Fields. To select multiple fields, press the CTRL key while selecting the fields.

Note

the start time for reconciliation reports (Chargebacks, Fees, Settlements, Funding, and Deposits) cannot be customized.


Chapter 3 Reports

Step 8 Click Save.

To create a report as an Account level user:

Step 1 Log in as an Account level user.


Step 3 Enter a report name.

Step 4 From the Frequency drop-down menu, choose the interval at which the report is to be generated. The options are:

One-Time

Daily

Weekly

Monthly

Step 5 From the Report Type drop-down menu, choose a report.

Step 6 From the Report Start Time drop-down menus, choose the time of day for the reports to be generated, and choose the time zone. If you are creating a one-time report, select a date range in the past for which you want data.

Step 7 Choose a report format: XML or CSV.

Step 8 Under Available Fields, select the additional fields that you want to include in the report, and click Add to move them to Selected Fields. To select multiple fields, press the CTRL key while selecting the fields.

Step 9 Click Save.

Downloading Reports

To download a report:

Step 1 On the Business Center home page, click Reports. A list of all available reports appears on the main reports page.

Step 2 From the Frequency drop-down menu, choose an interval.

Step 3 Choose a date range.

Step 4 Click the CSV or XML icon for the report you want to download.


Chapter 3 Reports

To download a report as an Account level user:


Step 2 On the Business Center home page, click Reports. A list of all available reports appears on the main reports page.

Step 3 From the Frequency drop-down menu, choose an interval.

Step 4 Choose a date range.

Step 5 Click the CSV or XML icon for the report you want to download.

Editing Reports

To edit a report:


Step 2 On the Reports page, click Manage Reports.

Step 3 Choose the report that you want to edit.

Step 4 Make the necessary changes to the report.

Step 5 Click Save.

To edit a report as an Account level user:




Step 4 Choose the report that you want to edit.

Step 5 Make the necessary changes to the report.

Step 6 Click Save.

Deleting Reports

To delete a report



Step 3 Choose the report that you want to delete.


Chapter 3 Reports

Step 4 Click Delete.

To delete a report as an Account level user:




Step 4 Choose the report that you want to delete.

Step 5 Click Delete.

Managing GroupsAccount level users can use the Group Management feature to create and manage groups of MIDs. Groups are useful for aggregating data across a set of MIDs. You can view analytics reports for your groups.

To access to the Group Management screen:

Step 1 Click on the user icon at the bottom left of the screen.

Step 2 Choose Settings.

To create a new group:

Step 1 In the Create Group content area, enter a group name and an optional description.

Step 2 Add one or more MIDs to your group.

Step 3 Click Save.

To edit a group:

Step 1 Click on a group name from the Group List area of the page.

Step 2 Edit the description or the members of an existing group, as necessary.

Step 3 Click Save.



PP

EN

DIX

A

A
Report Field Mappings
Chargeback Detail Report

The Chargeback and Representment Details Report, Chargeback and Representment Financial Details Report, and Retrieval Request Report have been replaced by the Chargeback Detail Report in the new Business Center. Refer to the table below for field comparisons.

Table 5 Field Mapping in the Chargeback Detail Report

Original Business Center Fields

New Business Center Fields Required/Optional

orig_capture_request_id RequestID Optional

cybs_mid MerchantID Required

processor_mid N/A

hierarchy_id Not supported

cybs_exception_id N/A

processor_case_id CaseNumber Required

case_amount ChargebackAmount Required

case_amount_currency ChargebackCurrency Required

cb_reason_code ChargebackReasonCode Optional

cb_reason_description ChargebackReasonCodeDescription

Optional

financial_impact_type FinancialImpactType Optional

orig_capture_trans_ref_number TransactionRefNumber Optional

case_type_description CaseType Required

cb_initiated_date ChargebackTime Required

response_date ResponseByDate Optional

status_description CaseIdentifier Optional

arn ARN Optional

event_posting_date CaseTime Required

orig_capture_amount RequestedAmount Optional

orig_capture_currency RequestedAmountCurrencyCode Optional

33

Appendix A Report Field Mappings

Detail Deposit Report

The Transfer Log Report has been replaced by the Detail Deposit Report in the new Business Center. Refer to the table below for field comparisons.

payment_method cardType Optional

account_suffix AccountSuffix Optional

orig_capture_sub_date TransactionDate Optional

orig_transaction_type TransactionType Required

orig_merchant_ref_number MerchantReferenceNumber Optional

orig_auth_trans_ref_number TransactionRefNumber Optional

orig_auth_date TransactionDate Required

cb_exception_fee_amount FeeAmount Optional

cb_exception_fee_currency FeeCurrency Optional

issuer_message_text ChargebackMessage Optional

funding_currency_case_amount ChargebackAmount Required

funding_currency ChargebackCurrency Required

first_name FirstName Optional

last_name LastName Optional

N/A DocumentIndicator Optional

N/A FinancialImpact Required

N/A MerchantCategoryCode Optional

N/A PartialIndicator Optional

N/A ResolutionTime Optional

N/A ResolvedToIndicator Optional

Table 6 Field Mapping in the Deposit Detail Report



transfer_ref_no Identifier Required

origination_date Time Required

processor_mid N/A N/A

cybs_mid MerchantID Required

effective_date N//A N/A

Table 5 Field Mapping in the Chargeback Detail Report (Continued)





Summary of Fees Report

The Summary of Fees Report has been replaced by the Fee Detail Report in the new Business Center. Refer to the table below for field comparisons.

amount Amount Required

currency_code Currency Required

type_description Type Required

hierarchy_id Not Supported Optional

masked_dda MerchantBankAcctLast4 Optional

routing_number MerchantBankCode Optional

transfer_method Method Required

acquirer N/A N/A

N/A Category Optional

N/A ExchangeRate Optional

N/A ExchangeRateDescription Optional

N/A Identifier Required

N/A MerchantBankAcctName Optional

N/A MerchantBankCountry Optional

N/A MerchantBankName Optional

N/A Status Required

N/A TransferMessage Optional

Table 7 Field Mapping in the Fee Detail Report



fee_type N/A N/A

transaction_type N/A N/A

payment_method N/A N/A

card_type N/A N/A

fee_description N//A N/A

per_item_fee N/A N/A

Table 6 Field Mapping in the Deposit Detail Report (Continued)






The Subscription Payment Exception Report has been replaced by the Transaction Exception Detail Report in the new Business Center. Refer to the table below for field comparisons.

transaction_amount N/A N/A

percentage_fee N/A N/A

total_fee_amount N/A N/A

count N/A N/A

N/A AssessmentCurrency Required

N/A BillingType Required

N/A DiscountAmount Required

N/A DiscountCurrency Required

N/A InterchangeAmount Required

N/A InterchangeCurrency Required

N/A SettlementAmount Required

N/A SettlementCurrency Required

N/A SettlementTime Required

N/A SettlmentTimeZone Required

N/A TotalFeeAmount Required

N/A TotalFeeCurrency Required

N/A Request Required

N/A MerchantID Required

N/A RequestID Required

N/A TransactionDate Required

Table 8 Field Mapping in the Transaction Exception Detail Report



SubscriptionID SubscriptionID Required

Table 7 Field Mapping in the Fee Detail Report (Continued)





OrderNumber MerchantReferenceNumber Required

Amount PaymentData.RequestedAmount Required

Currency RequestedAmountCurrency Required

CustomerName BillTo.FirstName and BillTo.Lastname

Required

PaymentType PaymentMethod.CardType Required

PaymentNumber PaymentNumber Required

LastAction LastActionDate Required

Status Application.RMsg Required

Retries Retries Required

NextAction NextActionDate Required

N/A Action Required

N/A CYBSExceptionID Optional

N/A ExceptionAmount Optional

N/A ExceptionAmountCurrency Optional

N/A ExceptionCategory Required

N/A ExceptionDate Optional

N/A ExceptionMessage Required

N/A ExceptionReasonDescription Optional

N/A ExceptionStatus Optional

N/A ExceptionType Required

N/A FinancialStatus Optional

N/A OriginalTransactionSubmissionDate

Optional

N/A ProcessorCaseID Optional

N/A ProcessorResponseCode Required

N/A ReasonCode Required

N/A Request Optional

N/A MerchantID Required

N/A B25 Optional

N/A TransactionDate Required

Table 8 Field Mapping in the Transaction Exception Detail Report (Continued)






The Invoice Summary Report has been replaced by the Invoice Summary Report in the new Business Center. Refer to the table below for field comparisons.

Table 9 Field Mapping in the Invoice Summary Report



BillingGroupDescription BillingGroupDescription Required

MerchantID MerchantID Required

NotProcessed NotProcessed Required

PerformedServices PerformedServices Required

Processed Processed Required

Total Total Required

N/A BillingDescription Required

N/A Application Required

N/A InvoiceCount Required



PP

EN

DIX

A

B
Report Field Definitions
Table 10 Report Field Definitions

Field Name Definition

Application.Name Name of application used.

Application.Rcode One-digit code that indicates whether the entire request was successful.

Application.Rflag One-word description of the result of the entire request.

Application.Rmsg Message that explains the <ics_flag> value.

Batch.BatchDate Date when the batch was sent to the processor.

Batch.BatchID CyberSource batch in which the transaction was sent.

Batch.Status Status of batch file.

Batch.SuccessFlag Indicates whether batch file processing was successful.

BillTo.Address1 First line of the billing street address as it appears on the credit card issuer’s records.

BillTo.Address2 Additional address information.

BillTo.City City of the billing address.

BillTo.CompanyName Name of the customer’s company.

BillTo.Country Country of the billing address.

BillTo.CustomerID Your identifier for the customer.

BillTo.Email Customer’s email address, including the full domain name.

BillTo.FirstName First name of the billed customer.

BillTo.HostName DNS resolved hostname from billTo_ipAddress.

BillTo.IPAddress Customer’s IP address.

BillTo.LastName Last name of the billed customer.

BillTo.MiddleName Middle name of the billed customer.

BillTo.NameSuffix Suffix of billed customer.

BillTo.Phone Customer’s phone number.

BillTo.State State or province of the billing address.

BillTo.Title Title of the billed customer.

39

Appendix B Report Field Definitions

BillTo.UserName Customer's user name.

BillTo.Zip Postal code for the billing address. The postal code must consist of 5 to 9 digits.

Event.Amount Amount for the event.

Event.CurrencyCode Currency code for the event.

Event.Event Type of event that occurred for the transaction.

Event.EventDate Date in GMT format that the event occurred. This field can be null for some event types, such as Declined.

Event.ProcessorMessage Additional information from the processor about the event, such as an error message or explanation.

Exception.Action Brief description of the action.

Exception.ExceptionAmount Amount specified in the exception.

Exception.ExceptionAmountCurrency

Exception currency represented in ISO 4217:2008 alpha-3.

Exception.ExceptionCategory Type of exception.

Exception.ExceptionMessage Description of the exception.

Exception.ExceptionReasonCode Reason code for the error that occurred. This reason code is the same one that you receive in the reply or transaction receipt.

Exception.ExceptionType Type of exception.

Exception.OriginalTransactionSubmissionDate

Date on which the transaction was submitted.

Exception.ProcessorResponseCode Code returned directly from the processor for the exception that occurred.

Exception.ReasonCode Reason code for the exception that occurred.

Exception.SettlementProcessor Name of settlement processor.

Funding.CurrencyExchangeDescription

Exchange rate description from the processor.

Funding.CurrencyExchangeRate Exchange rate for converting from transaction currency to funding currency.

Funding.FeeAmount Fee for the transaction.

Funding.FeeCurrency Fee currency represented in ISO 4217:2008 alpha-3.

Funding.FeeDescription Fee description from the processor.

Funding.FundingAccountSuffix Last 4 digits of funding account.

Funding.FundingAmount Funding amount of the transaction.

Funding.FundingBankCode Bank code of the funding bank.

Funding.FundingBankCountry Bank country of the funding bank represented in ISO 3166-1 alpha-3.

Table 10 Report Field Definitions (Continued)




Funding.FundingBankName Name of bank funding the transaction.

Funding.FundingCurrency Funding currency represented in ISO 4217:2008 alpha-3.

Funding.FundingDate Funding date of the transaction.

Funding.FundingIdentificationNumber

Funding identification for the funding of the transaction.

Funding.FundingProcessorMessage Funding response message from the processor.

Funding.FundingTransferMessage Funding transfer message provided by the processor.

Funding.ProcessorResponseCode Funding response code from the processor.

Funding.Status Funding status indicating success ("S"), Pending ("P"), Failed("F").

LineItems.FulfillmentType Information about the product code used for the line item.

LineItems.InvoiceNumber Invoice number for order.

LineItems.MerchantProductSku Identification code for the product.

LineItems.Number Number of the line item in an order.

LineItems.ProductCode Type of product. This value is used to determine the category that the product is in: electronic, handling, physical, service, or shipping.

LineItems.ProductName Name of product.

LineItems.Quantity Quantity of product.

LineItems.TaxAmount Total tax to apply to the product.

LineItems.UnitPrice Per-item price of the product.

MerchantDefinedData.Field1 - MerchantDefinedData.Field20

Fields that you can use to store information.

PaymentData.AAV_CAVV Optional authentication data that you can receive after the customer is authenticated.

PaymentData.ACHVerificationResult Raw result of the ACH Verification service.

PaymentData.ACHVerificationResultMapped

Mapped result of the ACH Verification service.

PaymentData.Amount Grand total for the order.

PaymentData.AuthorizationCode Authorization code for the payment.

PaymentData.AuthorizationType Authorization type of the payment.

PaymentData.AVSResult Raw code for Address Verification Service result for the payment.

PaymentData.AVSResultMapped Address Verification Service result for the payment.

PaymentData.BalanceAmount Remaining balance on the account.





PaymentData.BalanceCurrencyCode

Currency of the remaining balance on the account.

PaymentData.BankAccountName Name of account holder.

PaymentData.BankCode Bank code or sort code for the account if a bank account was used for the transaction.

PaymentData.BinNumber Bank identification number.

PaymentData.CurrencyCode Currency code for the payment.

PaymentData.CVResult CVN result code.

PaymentData.DCCIndicator Flag that indicates whether DCC is being used for the transaction.

PaymentData.ECI Optional information that you can receive if you use the Payer Authentication service.

PaymentData.EVEmail Mapped Electronic Verification response code for the customer’s email address.

PaymentData.EVEmailRaw Raw Electronic Verification response code from the processor for the customer’s email address.

PaymentData.EventType Type of event that occurred for the transaction.

PaymentData.EVName Mapped Electronic Verification response code for the customer’s name.

PaymentData.EVNameRaw Raw Electronic Verification response code from the processor for the customer’s last name.

PaymentData.EVPhoneNumber Mapped Electronic Verification response code for the customer’s phone number.

PaymentData.EVPhoneNumberRaw Raw Electronic Verification response code from the processor for the customer’s phone number.

PaymentData.EVPostalCode Mapped Electronic Verification response code for the customer’s postal code.

PaymentData.EVPostalCodeRaw Raw Electronic Verification response code from the processor for the customer’s postal code.

PaymentData.EVStreet Mapped Electronic Verification response code for the customer’s street address.

PaymentData.EVStreetRaw Raw Electronic Verification response code from the processor for the customer’s street address.

PaymentData.ExchangeRate Exchange rate.

PaymentData.ExchangeRateDate Time stamp for the exchange rate.

PaymentData.GrandTotal Grand total amount for the order, including tax, for requests that do not contain payment information

PaymentData.NumberOfInstallments Total number of installments when making payments in installments.

PaymentData.PaymentProcessor Name of payment processor.





PaymentData.PaymentRequestID Original request ID for the purchase.

PaymentData.ProcessorResponseCode

The error message sent directly from the bank.

PaymentData.RequestedAmount Amount requested to be authorized.

PaymentData.RequestedAmountCurrencyCode

Currency for the amount requested to be authorized.

PaymentData.TargetAmount Converted amount.

PaymentData.TargetCurrency Billing currency.

PaymentData.TotalTaxAmount Total tax amount for all of the line items in the transaction.

PaymentData.XID Optional transaction identifier generated by Payer Authentication that you can receive when the customer is enrolled and when validation is successful.

PaymentMethod.AccountSuffix Last four digits of the customer’s payment account number.

PaymentMethod.BoletoNumber Boleto Bancário payment number.

PaymentMethod.CardCategory Type of card used.

PaymentMethod.CardCategoryCode Code for card type used.

PaymentMethod.CardType Type of card to authorize.

PaymentMethod.CheckNumber Check number.

PaymentMethod.ExpirationMonth Two-digit month in which the credit card expires.

PaymentMethod.ExpirationYear Four-digit year in which the credit card expires.

PaymentMethod.IssueNumber Number of times a Maestro (UK Domestic) card has been issued to the account holder.

PaymentMethod.MandateId Identification reference for the direct debit mandate.

PaymentMethod.MandateType Type of mandate.

PaymentMethod.StartMonth Month of the start of the Maestro (UK Domestic) card validity period.

PaymentMethod.StartYear Year of the start of the Maestro (UK Domestic) card validity period.

PaymentMethod.WalletType Type of wallet.

Profile.Name Name of the profile.

Profile.ProfileDecision Decision returned by the profile.

Profile.ProfileMode Activity mode of the profile.

Profile.RuleDecision Decision returned by the rule.

Profile.RuleName Name of the rule.

Request.Comments Optional comments that you can make about the subscription or customer profile.





Request.eCommerceIndicator Type of transaction.

Request.MerchantID CyberSource merchant ID used for the transactions.

Request.MerchantReferenceNumber

Merchant-generated order reference or tracking number.

Request.RequestID Identifier for the transaction request.

Request.Source Source of request.

Request.SubscriptionID Identifier for the customer profile.

Request.TransactionDate Date on which the transaction took place.

Request.TransactionRefNumber Identifier for the transaction.

Request.User Information about a user.

Risk.AppliedCategoryGift Importance of billing and shipping addresses in assessing the order. If you do not specify a value in your request, the server uses the default value for your merchant ID.

Risk.AppliedCategoryTime Importance of time of day in assessing the order. If you do not specify a value in your request, the server uses the default value for your merchant ID.

Risk.AppliedHostHedge Importance of email and IP addresses of the customer in assessing the order. If you\ do not specify a value in your request, the server uses the default value for your merchant ID.

Risk.AppliedThreshold Score threshold applied to the order.

Risk.AppliedTimeHedge Importance of time of day in assessing the order. If you do not specify a value in your request, the server uses the default value for your merchant ID.

Risk.AppliedVelocityHedge Importance of the number of orders from the customer in a specific time period in assessing the order. If you do not specify a value in your request, the server uses the default value for your merchant ID.

Risk.BinAccountType Type of customer.

Risk.BinCountry Country (two-digit country code) associated with the BIN of the customer’s card used for the payment.

Risk.BinIssuer Name of the bank or entity that issued the card account.

Risk.BinScheme Subtype of card account.

Risk.CodeType Category of information code returned for an order.

Risk.CodeValue Description of the information code returned in the <CodeType> element.

Risk.ConsumerLoyalty Indicates whether a loyalty program is used or the number of the loyalty reward account that is used.





Risk.CookiesEnabled Indicates whether cookies are enabled in the customer’s browser.

Risk.DeviceFingerPrint Indicates if Device Fingerprint is used.

Risk.Factors Information that affected the score of the order.

Risk.FlashEnabled Indicates whether Flash is enabled in the customer’s browser.

Risk.HostSeverity Risk associated with the customer's email domain.

Risk.ImagesEnabled Indicates whether images are enabled in the customer’s browser.

Risk.IPCity Name of the city decoded from the IP address used directly or indirectly by the customer to send the order.

Risk.IPCountry Name of the country decoded from the IP address used directly or indirectly by the customer to send the order.

Risk.IPRoutingMethod Routing method decoded from the IP address used directly or indirectly by the customer to send the order.

Risk.IPState Name of the state decoded from the IP address used directly or indirectly by the customer to send the order.

Risk.JavascriptEnabled Indicates whether JavaScript is enabled in the customer’s browser.

Risk.ProxyIPAddress IP address of the proxy if it is available.

Risk.ProxyIPAddressActivities Actions associated with the proxy IP address.

Risk.ProxyIPAddressAttributes Characteristics associated with the proxy IP address.

Risk.ProxyServerType Type of proxy server based on the HTTP header.

Risk.Score Total score calculated for the order.

Risk.TimeLocal Local time of order.

Risk.TrueIPAddress Customer’s true IP address detected by the application.

Risk.TrueIPaddressActivities Actions associated with the true IP address.

Risk.TrueIPAddressAttributes Characteristics associated with the true IP address.

Risk.TrueIPAddressCity City associated with the true IP address.

Risk.TrueIPAddressCountry Country associated with the true IP address.

Settlement.SettlementAmount Settlement amount of the transaction.

Settlement.SettlementCurrencyCode

Settlement currency represented in ISO 4217:2008 alpha-3.

Settlement.SettlementDate Settlement date of the transaction.

Settlement.SourceResponseCode Settlement response code from the processor.

Settlement.SourceResponseMessage

Settlement response message from the processor.





Settlement.Status Settlement status indicating success ("S"), Pending ("P"), Failed("F").

Shipping.Carrier Carrier used to ship product.

Shipping.Method Shipping method for the product.

ShipTo.Address1 First line of the address to ship the product to.

ShipTo.Address2 Second line of the address to ship the product to.

ShipTo.City City to ship the product to.

ShipTo.Country Country to ship the product to.

ShipTo.FirstName First name of the person receiving the product.

ShipTo.LastName Last name of the person receiving the product.

ShipTo.Phone Phone number of the customer to whom the order is shipped.

ShipTo.State State or province of the address to ship the product to.

ShipTo.Zip Postal code for the shipping address. The postal code must consist of 5 to 9 digits.

Travel.CompleteRoute Concatenation of individual travel legs.

Travel.DepartureDateTime Departure date and time of the first leg of the trip.

Travel.JourneyType Type of travel.

Travel.Number Offer level or rank of the passenger in the order.

Travel.PassengerFirstName Passenger’s first name.

Travel.PassengerEmail Passenger's email address, including the complete domain name.

Travel.PassengerId ID of the passenger to whom the ticket was issued.

Travel.PassengerLastName Passenger’s last name.

Travel.PassengerPhone Passenger's phone number.

Travel.PassengerStatus Your company's passenger classification, such as with a frequent flyer program.

Travel.PassengerType Passenger classification associated with the price of the ticket.




Actuate Reporting Migration Guide for Wells Fargo | August 2016

PP

EN

DIX

A

C
Report Fields Available
The tables below list which fields are available in each report. Fields automatically included in the report are designated by “(*)”.

47

Appendix C Report Fields Available

Transaction Request Report

Table 11 Fields available in the Transaction Request Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields

Address1 Address2 City

CompanyName Country CustomerID

Email FirstName HostName

IPAddress LastName MiddleName

NameSuffix PersonalID Phone

State Title UserName

Zip

LineItems Fields

FulfillmentType InvoiceNumber MerchantProductSku

Number ProductCode ProductName

Quantity TaxAmount UnitPrice

MerchantDefinedData Fields

Field1 - Field20

PaymentData Fields

AAV_CAVV ACHVerificationResult ACHVerificationResultMapped

AVSResult AVSResultMapped Amount

AuthorizationCode AuthorizationType BalanceAmount

BalanceCurrencyCode BankAccountName BankCode

BinNumber BoletoBarCodeNumber CVResult

CurrencyCode DCCIndicator ECI

EVEmail EVEmailRaw EVName

EVNameRaw EVPhoneNumber EVPhoneNumberRaw

EVPostalCode EVPostalCodeRaw EVStreet

EVStreetRaw EventType ExchangeRate

ExchangeRateDate GrandTotal NetworkTransactionID

NumberOfInstallments PaymentProcessor PaymentRequestID

ProcessorResponseCode ProcessorResponseID ProcessorTID

RequestedAmount RequestedAmountCurrencyCode

TargetAmount

Actuate Reporting Migration Guide for Wells Fargo | August 2016 48


TargetCurrency TotalTaxAmount XID

PaymentMethod Fields

AccountSuffix BoletoNumber CardCategory

CardCategoryCode CardType CheckNumber

ExpirationMonth ExpirationYear IssueNumber

MandateId MandateType SignatureDate

StartMonth StartYear WalletType

Profile Fields

Name ProfileDecision ProfileMode

RuleDecision RuleName

Request Fields

Comments MerchantID (*) MerchantReferenceNumber

RequestID (*) Source SubscriptionID

TransactionDate (*) TransactionRefNumber User

eCommerceIndicator

Risk Fields

AppliedAVS AppliedCV AppliedCategoryGift

AppliedCategoryTime AppliedHostHedge AppliedThreshold

AppliedTimeHedge AppliedVelocityHedge BinAccountType

BinCountry BinIssuer BinScheme

CodeType CodeValue ConsumerLoyalty

ConsumerPasswordProvided ConsumerPromotions CookiesAccepted

CookiesEnabled DeviceFingerPrint Factors

FlashEnabled GiftWrap HostSeverity

IPCity IPCountry IPRoutingMethod

IPState ImagesEnabled JavascriptEnabled

LostPassword ProductRisk ProxyIPAddress

ProxyIPAddressActivities ProxyIPAddressAttributes ProxyServerType

RepeatCustomer ReturnsAccepted Score

TimeLocal TrueIPAddress TrueIPAddressAttributes

TrueIPAddressCity TrueIPAddressCountry TrueIPaddressActivities

ShipTo Fields


Country FirstName LastName

Phone State Zip

Shipping Fields

Table 11 Fields available in the Transaction Request Report (Continued)



Carrier Method

Travel Fields

CompleteRoute DepartureDateTime JourneyType

Number PassengerEmail PassengerFirstName

PassengerId PassengerLastName PassengerPhone

PassengerStatus PassengerType

Table 11 Fields available in the Transaction Request Report (Continued)



Payment Batch Detail Report

Table 12 Fields available in the Payment Batch Detail Report

Application Fields

Name Rcode Rflag

Rmsg

Batch Fields

BatchDate (*) BatchID (*) Status (*)

SuccessFlag

BillTo Fields







Zip

LineItems Fields





Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields
















ShipTo Fields


Table 12 Fields available in the Payment Batch Detail Report (Continued)




Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 12 Fields available in the Payment Batch Detail Report (Continued)



Transaction Exception Detail Report

Table 13 Fields available in the Transaction Exception Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

Exception Fields

Action (*) CYBSExceptionID ExceptionAmount

ExceptionAmountCurrency ExceptionCategory (*) ExceptionDate

ExceptionMessage (*) ExceptionReasonDescription ExceptionStatus

ExceptionType (*) FinancialStatus OriginalTransactionSubmissionDate

ProcessorCaseID ProcessorResponseCode (*) ReasonCode (*)

LineItems Fields





Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields













Table 13 Fields available in the Transaction Exception Detail Report (Continued)






ShipTo Fields



Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 13 Fields available in the Transaction Exception Detail Report (Continued)



Processor Events Detail Report

Table 14 Fields available in the Processor Events Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

Event Fields

Amount CurrencyCode Event (*)

EventDate (*) ProcessorMessage (*)

LineItems Fields





Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields
















ShipTo Fields


Table 14 Fields available in the Processor Events Detail Report (Continued)





Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 15 Fields available in the Invoice Summary Report

Invoice Fields

BillingGroupDescription (*) MerchantID (*) NotProcessed (*)

PerformedServices (*) Processed (*) Total (*)

Table 14 Fields available in the Processor Events Detail Report (Continued)



Processor Settlement Detail Report

Table 16 Fields available in the Processor Settlement Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

LineItems Fields





Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields
















Settlement Fields

SettlementAmount (*) SettlementCurrencyCode (*) SettlementDate (*)

SourceResponseCode SourceResponseMessage Status

Table 16 Fields available in the Processor Settlement Detail Report (Continued)



ShipTo Fields



Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 16 Fields available in the Processor Settlement Detail Report (Continued)



Funding Detail Report

Table 17 Fields available in the Funding Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

Funding Fields

CurrencyExchangeDescription

CurrencyExchangeRate FeeAmount

FeeCurrency FeeDescription FundingAmount (*)

FundingCurrency (*) FundingDate (*) FundingProcessorMessage

ProcessorResponseCode Status

LineItems Fields





Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields















Table 17 Fields available in the Funding Detail Report (Continued)




ShipTo Fields



Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 17 Fields available in the Funding Detail Report (Continued)



Aging Detail Report

Table 18 Fields available in the Aging Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

LineItems Fields





Field1 - Field20

PaymentData Fields















TargetAmount










Profile Fields



Request Fields




eCommerceIndicator

Risk Fields
















Settlement Fields

SettlementAge (*) SettlementAmount (*) SettlementCurrencyCode (*)

SettlementDate (*) SourceResponseCode SourceResponseMessage

Status

ShipTo Fields

Table 18 Fields available in the Aging Detail Report (Continued)





Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 18 Fields available in the Aging Detail Report (Continued)



Chargeback and Retrieval Detail Report

Table 19 Fields available in the Chargeback and Retrieval Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

ChargebackAndRetrieval Fields

ARN AdjustmentAmount AdjustmentCurrency

CaseIdentifier CaseNumber (*) CaseTime (*)

CaseType (*) ChargebackAmount (*) ChargebackCurrency (*)

ChargebackMessage ChargebackReasonCode ChargebackReasonCodeDescription

ChargebackTime (*) DocumentIndicator FeeAmount

FeeCurrency FinancialImpact (*) FinancialImpactType

MerchantCategoryCode PartialIndicator ResolutionTime

ResolvedToIndicator RespondByDate TransactionType (*)

LineItems Fields





Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields













Deposit Detail Report







ShipTo Fields



Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 20 Fields available in the Deposit Detail Report

Deposit Fields

Amount (*) Category (*) Currency (*)

Identifier (*) MerchantID (*) Method (*)

Status (*) Time (*) Type (*)




Fee Detail Report

Table 21 Fields available in the Fee Detail Report

Application Fields

Name Rcode Rflag

Rmsg

BillTo Fields







Zip

Fee Fields

AssessmentAmount (*) AssessmentCurrency (*) BillingCycle

BillingType (*) ClearedInterchangeLevel DiscountAmount (*)

DiscountCurrency (*) DiscountRate DowngradeReasonCode

InterchangeAmount (*) InterchangeCurrency (*) InterchangeRate

PerItemFeeAmount PerItemFeeCurrency PricedInterchangeLevel

SettlementAmount (*) SettlementCurrency (*) SettlementTime (*)

SettlementTimeZone (*) SourceDescriptor TotalFeeAmount (*)

TotalFeeCurrency (*)


Field1 - Field20

PaymentData Fields

















TargetAmount








Profile Fields



Request Fields




eCommerceIndicator

Risk Fields
















Table 21 Fields available in the Fee Detail Report (Continued)



ShipTo Fields



Phone State Zip

Shipping Fields

Carrier Method

Travel Fields





Table 21 Fields available in the Fee Detail Report (Continued)


migrating to the new reporting platform - online … · migrating to the new reporting...

Documents