Reporting Manual

Adyen provides a number of reports at company and merchant account level. Click Reports on the navigation sidebar on the left to access your reports.

Reports are grouped in categories to help you reach the report you are looking for.

Expanding the categories gives you a wide number of reports with options to Download to a maximum of them.

You can subscribe to the Scheduled reports, generated periodically, if you have an active subscription.

You can reach the Adyen Customer Area (CA) by following these URLs:

To request assistance or if you have any questions about the Adyen Customer Area (CA), contact the Adyen Support Team or your Account Manager. 

After successfully logging in to the CA, you see a screen similar to the one below:

Activate a subscription

To activate a subscription to a scheduled report, do the following:

  • In the Adyen Customer Area (CA), click Reports on the navigation sidebar on the left to access your reports.
  • Under Scheduled Reports, browse to the desired report.
  • Click Subscribe to enable subscription for the specified report.
  • In the popup dialog window, select the preferred download format from the drop-down menu. Depending on the report, the available download formats are XLS, PDF, CSV or XML.
  • After selecting your download format, click the Save button to store your settings.

You are now subscribed to the selected scheduled report.

Audience

This manual targets merchants who want to use the Adyen payment services to efficiently and safely process their business transactions.

Feedback

We strive to provide you with clear, concise, and complete documentation. We are committed to improving it continuously to make it accessible and easy to understand.

We appreciate your comments, and we'd love to hear your voice: drop us a line and share your thoughts with us!

  Adyen Support Team

Reporting last update

Version Date Changes
4.5 2016-06-15 Added Optimization report.

Version

Date

Changes

4.5 2016-06-15 Added Optimization report.
4.4.2 2016-01-20

Added new columns to Dispute report.

4.4.1 2015-11-26

Added new journal types in Settlement detail report journal types and Payment balance sheet.

4.4.0

2015-09-23

New: Instalment payment flow and reporting

4.3.0 2015-09-22
4.2.0 2015-09-10

New: three new journal type entries added to Settlement detail report journal types:

  • SettledBulk
  • RefundedBulk
  • BulkSettlement

These entries apply to Visa and Mastercard only.
To ensure backward compatibility, the Settlement Detail Report is not affected.
Therefore, this change does not impact processes that consume this report
(for example by automatically loading it to an ERP system or a Data Warehouse).

4.1 2015-09-02

Received payment detail report: position 43 now holds the raw acquirer response, where available.

4.0 2015-05-13
  • Documentation migration from PDF to web-based online deliverable as main distributable asset.
  • Versioning: version reset and adoption of semantic versioning as per v. 4.0.0.

2.2.5

2015-04-07

  • Added description of extra column in Settlement Detail Report

  • Added tables with the description of journal types

  • Updated screenshots

2.2.4

2015-03-18

  • Added Notification of Fraud columns in the Daily Dispute Report

2.2.3

2014-11-05

  • Added new Types to Appendix A and Appendix B

2.2.2

2014-05-05

  • Added new Type AuthorisationSchemeFee to Appendix A

  • Corrected file naming convention for the External Settlement Detail Report

  • Updated “type” field definition in Appendix B

  • Updated file format for Appendix B

  • Updated file format for Appendix C

  • Updated shopper PAN description in Appendix E

2.2.1

2014-01-29

  • Corrected typo in Type field for Appendix A

  • Added note to Appendix A for changing data types per Type

  • Added Modification Merchant Reference to Appendix A

2.2

2013-12-11

  • Manual updated to conform to Adyen brand guidelines

2.1.7

2013-09-16

  • Added Payment Accounting Report / Dispute Report / Received Payment Detail Report to Appendix

  • Reworked field specifications in Appendices A-D

2.1.6

2013-06-11

  • Updated example line items to reflect latest file format

  • Added Settlement Report and External Settlement Report to Appendix

2.1.5

2012-06-26

  • Added Dispute Report

2.1.4

2011-12-23

  • Added Deposit and Invoice correction lines to the Settlement Report explanation

2.1.3

2011-03-22

  • Added information on multi-currency transactions in settlement report

2.1.2

2010-08-13

  • Changed screenshots to reflect current default skin look & feel

2.1.1

2010-08-10

  • Added changelog and audience sections

  • Manual reviewed for English and layout consistency

Optimization

Optimization Explorer (OE) is a reporting tool that gives you unique insights into your data. It highlights and identifies opportunities to improve your authorization rates (the percent of received transactions that are approved).

OE consists of two components:

  • Tree builder - used to create the structure of the report
  • Explorer - used to view the report.

Each component is a separate report available in the reporting section of the Adyen Customer Area (CA).

Tree builder

Tree builder is used in conjunction with the optimization explorer and allows users to build their own unique views on their data. Using this you can manage existing trees and/or to create new trees.

Creating a new tree is a 3 step process:

Go to Reports -> Optimization Explorer Tree Builder.

Step1: Select tree

Select an existing tree from the drop down, or select a new one.

Step 2: Edit tree

When creating a tree, only a baseline node with 2 drop down boxes is available.

  1. Select a dimension to split the data (card type, issuer country, merchant account, etc.) There are 26 dimensions available.
  2. After a dimension has been selected, specify the values to be used. Every selected value becomes a child node. Transactions that do not belong in one of the selected nodes are assigned to the Other node.

    Advanced - It is also possible to group multiple dimension values to visualize them into a single node. To do this, select all dimension values you wish to group then click New Group and enter a name.

  3. Repeat the above steps breaking down the data along which ever dimensions you want until you're satisfied with the tree. Save the tree and then proceed to step 3.

On the left of the screen the tree can be (re)named and saved.

Step 3: Schedule tree

After creating the tree structure, enter the payment data. Select the period in the past to view the specific data in the report. 

Scheduling usually takes about 1 hour but depending on the specified period it can take longer.

After completing scheduling, you receive an email notification and the tree is visible in the explorer. 

Explorer

Using the explorer report, you can see multiple breakdowns of your transaction data.

The report consists of 3 sections:

  • A date picker
  • The baseline breakdown report 
  • Node details report

On the top left of the baseline breakdown report, from a dropdown menu select the tree to view. If no report is available for viewing, some default templates are available to start. 

You can build your own specific report using the tree builder.

The baseline breakdown report is a hierarchical report that breaks down a merchant's transactions along specific dimensions. Each subset is called a node, with the top node being the baseline node, which consists of all received transactions over the period specified in the date picker (You can define your data based on Months, Weeks, or days).

Within each node, numerous data points are available:

  • The number of transactions in that node (top left).
  • The total euro amount of received transactions in the node (middle left).
  • The percent of transactions that were authorized (bottom left).
  • And the percent of transactions in the node with respect to the baseline (top right).

At the top right of the baseline breakdown report are several action buttons, these do the following things, from left to right:

  • Download the data seen in the baseline breakdown report as a csv.
  • Take a screenshot.
  • Change the orientation of the report.
  • Zoom in and out.
  • Reset the zoom.

Click a node for more detailed information available in the Node details report

The Node details report contains:

  • Top left graph - Daily authorization rate (green line) with 7 day moving average (black line).
  • Bottom left graph - Daily number of received transactions.
  • Right graph - Monthly aggregates (only available if selected time period is more than 1 month).

Report download

Scheduled reports with active subscriptions are typically generated overnight (CET time zone), so that they are available on the scheduled available day.
You can access the reports you have active subscriptions to through either a URL, or the Adyen Customer Area (CA).

Access scheduled reports via a URL

You can download the generated reports from the URLs below.

[yourMerchantAccountName] and  [yourCompanyAccountName] are placeholders: replace them with your Adyen merchant account and company account user names, respectively.

You can retrieve your company and merchant account user names on the upper part of the Adyen Customer Area (CA) screen: the top-level name displayed here corresponds to your company account user name, whereas any names beneath it are your merchant account user names.

The Adyen system sends notification messages with URLs pointing at specific reports.

For example: https://ca-live.adyen.com/reports/download/MerchantAccount/TestMerchant/settlement_detail_report_batch_121.csv

Access scheduled reports via the CA

To retrieve scheduled reports in the CA:

  • On the navigation sidebar on the left, click Reports.
  • On the report page, browse the report categories for the desired report.
  • Click Download.
  • In the popup dialog window:
    • Set any report-specific settings like start or ending dates, merchant reference, and so on.
    • Choose a download format from the drop-down menu.
    • Click Generate.
  • Browse to the folder you want to save the generated report file to, then click Save.

Automate report retrieval

The URLs above require basic authentication. You can use them to configure automated report retrieval.

The user name you need to authenticate is in the format report@Company.[yourcompanyaccountname]:

  • report@Company.: the first part of the user name remains as is, you do not need to change it.
  • [yourcompanyaccountname]: this is a placeholder. Replace it with your Adyen company account user name.

To set a password for your Adyen user account, go to the the Adyen Customer Area (CA), then select Settings | Users.

If the " @" character is not allowed in the user name, you can use the " %" character instead.

You can use the command line to easily automate report retrieval with wget:

$ wget --http-user=report%Company.YCA --http-password=PWD --quiet --no-check-certificate https://ca-live.adyen.com/reports/download/MerchantAccount/YMA/REP

Where:
YCA = your company account 
YMA = your merchant account 
PWD = the password 
REP = the report name e.g. payment_report_batch_18.csv

When new reports are published, you receive a notification to your notification server via HTTPS POST, JSON or SOAP, just in the same way as you receive standard payment notifications.

The status code is REPORT_AVAILABLE and the full download URL is included in the notification.

Report RSS feed

If you need up-to-the-minute, real-time information on your payment traffic, refusal rate and fraud scores, you can subscribe to a reporting RSS feed. You can the access the RSS feed content from any RSS-capable application like an email client, a web browsers or a dedicated RSS reader.

You can create a separate user to consume the RSS report. For this user the Merchant Rss feed role needs to be active.

RSS feed fetching

You can fetch the reporting RSS feed from the URLs below.

[yourMerchantAccountName] and  [yourCompanyAccountName] are placeholders: replace them with your Adyen merchant account and company account user names, respectively.

If you use the company account, the RSS feed fetches all transactions aggregated at company level. RSS feeds are available in the Customer Area as well: when you see the RSS icon , click it to import the RSS feed directly into your browser.

Currently, Adyen offers two reporting RSS feeds:

RSS feed Description

lasttxrss

Number of payments (authorised, refused and total) per hour during the past 24 hours.

authorisedtxrss

Yesterday and the day before yesterday total amount of authorised payments per currency, transaction amount, and average transaction value.

Report timing

The report time of the received payment detail and the payment accounting reports corresponds to the time zone information for each transaction included in the report.

The settlement detail report is generated when Adyen initiates a payout to your bank account(s).

For all other reports, the report generation process is initiated at 04:00 CET; this setting cannot be changed.

Reading your invoice

Invoicing typically runs at company account level; however, if you prefer it can also run at merchant account level. Your monthly invoice contains a full specification of the costs of payment processing for the given month.

How to read your invoice

Each regular transaction can include two cost types:

  • Adyen's transaction fees (per transaction).
  • The bank or card scheme commissions, which can be a percentage and/or a fixed fee. In some cases, these fees also decrease as volume increases.

Funds settlement

Adyen typically settles funds to your bank account twice a week.

Funds settlement = transaction amounts - refunds and/or chargebacks (if any/if applicable)

Adyen uses net settlement; therefore, any applicable fees and commissions are already deducted from your settlement batch. The accompanying settlement reports contain a detailed calculation and justification.

Because the actual fees per transaction depend on the total volume processed during a given month, the intermediary amounts deducted from the settlements can vary slightly from the actual amounts due. Only at the end of the month are we able to calculate the final amounts. Therefore, an invoice always contains two totals:

  • The already deducted amount, and
  • The final calculated amounts.

The resulting difference is settled with your next batch using the invoice correction line.

Invoice layout

Your invoice typically consists of at least two pages:

  • A header page summarising the previous month's transaction fees and commissions.
  • A detail page with tables for calculated and already deducted amounts.
  • Optionally, you may choose to break down tour invoice details by merchant account; in this case, your invoice includes additional pages, organized by merchant account.

Invoice summary page

The Still Due amount may be positive or negative. In the payment instructions section you can find further information on the follow-up steps you need to make to balance any existing differences. In either case, differences are rectified in the following settlement batch.

Some causes for differences in calculated and collected fees can be:

  • Tiered pricing: during the month you will be charged with the lowest tier.
  • For transactions occurring during the last few days of the month, the transaction fee is charged in the current month, whereas commission fees may be charged in the following month.
  • Any price changes introduced during the month.

Invoice detail page

The second page contains a table showing how the totals on the summary page are calculated. The resulting amount in the bottom-right cell equals the invoice total, VAT excluded.

The already deducted table on the invoice contains the total charges already deducted from earlier settlements. These amounts are in the settlement reports as well, so you can verify the charges.

Dynamic currency conversion reporting

Merchants can decide to offer shoppers Dynamic Currency Conversion (DCC) to convert the merchant's currency and amount to the shopper's native currency, when they make a payment abroad (Visa, Mastercard).

This feature has proved to be appreciated in environments handling multi-currency transactions, for example airport shops, where customers often prefer to complete a transaction using a currency they're familiar with, rather than the local one.

Activate DCC reporting

When DCC is turned on in a POS integration, you can optionally include DCC information in your reports.
Besides the markup information related to dynamic currency conversion, DCC reporting provides valuable insight into the feature popularity among your shoppers.

This functionality is not enabled by default, as it requires additional configuration on Adyen's end. Contact the  Adyen Support Team to request enabling it for you.

Alternatively, you can request activating this feature by contacting the Adyen POS Support Team.

DCC information in reports

When the feature is turned on, DCC information is included  in the following reports:

  • Received payment detail report
  • Settlement detail report

Each report is augmented with an additional column.

Received payment detail report

When DCC is turned on, this report is enhanced with the following data:

Column position Header Values
Position 44
(AR column)
DCC
  • DCC accepted:
    during a POS transaction, the shopper is asked whether they'd like to use DCC.
    They accept, and complete the transaction in the shopper's currency.
  • DCC declined:
    during a POS transaction, the shopper is asked whether they'd like to use DCC.
    They refuse, and complete the transaction in the merchant's currency.
  • DCC not offered:
    when shopper and merchant both share the same currency, DCC is not necessary.

Settlement detail report

When DCC is turned on, this report is enhanced with the following data:

Column position Header Values

Position 23
(W column)

DCC Markup (NC)
Numeric value showing the DCC markup.
The currency corresponds to the settlement currency.
A negative amount indicates a credit in favour of the merchant.

Examples

As a reference, you can find here examples of a received payment detail and a settlement detail reports with the additional DCC markup columns. The standard file format for these reports is .csv.
You can download a .zip archive containing the report samples.

Received payment detail  report

File name received_payments_report_2015_05_18
File format .csv

Acquirer Reference Payment Method Variant Raw acquirer response DCC Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved9 Reserved10
8PP0LJS6O1Q mc AUTHORISED DCC accepted
8PP0LJS5QNJ visa AUTHORISED DCC accepted
8PP0LJS5766 mcpro AUTHORISED DCC accepted
8PP0LJS4JKG mcpro AUTHORISED DCC accepted

Settlement detail report

File name settlement_detail_report_batch_2
File format .csv

Markup (NC) Scheme Fees (NC) Interchange (NC) DCC Markup (NC) Payment Method Variant Modification Merchant Reference Batch Number Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved9 Reserved10
0.02 0.02 0.04 -0.03 visa <auto> 2
0.85 0.85 2.26 -1.52 mc <auto> 2

Installment payments

Installments are a popular form of payment; they are common especially in Latin America.

When a shopper finalizes a transaction and they choose to pay in installments, the total payable amount is split up into a number of partial amounts, distributed over a period of time.
The shopper needs to honour each partial payment, i.e. each installment, within the given time frame, and until the total amount due has been reached.

On one hand, installments make it more appealing for shoppers to purchase goods and services: they can access the goods or services as soon as possible or even immediately after finalizing the purchase, whereas they can dilute and distribute the total cost over a set period of time.
On the other hand, they make it harder to reconcile and settle payments because they add complexity to the process.

This section covers installment payments from a business-oriented perspective; therefore, its main focus is the installment payment process.

To learn more about the technical implementation of installments using our payment API, refer to the  installments object in the  authorise API call.

Installments in a nutshell

When you set up a process to support payments in installments, keep these guidelines into account:

  • Define the maximum number of installments a shopper can choose to fully pay for their purchase.
  • Define a time frame to spread the installments over.
    For example, 3, 6, 12, or 24 months.
  • Set the amount due per installment.
  • Set the interest rate to charge the shopper with for choosing installments as a payment method.
     Adyen does not calculate interest. Therefore, you should always send us the amount including the interest.
  • Usually, installments are due on a monthly basis, at the beginning or at the end of each month.
    Issuers control installment due dates.
    Merchants receive installment every 30 days from the corresponding payment capture day.

To learn more about the technical implementation of installments using our payment API, refer to the  installments object in the  authorise API call.

Installment types

Installments need to be funded. Typically, there are two standard types of installments:

  • Issuer-funded installments, and
  • Merchant-funded installments.

Adyen supports merchant-funded installments.

Installment payments in Brazil

Adyen makes installment payments available in Brazil through the following financial institutions:

  • Cielo (Adyen carries out reconciliation for S-level merchants.)
  • Rede (formerly Redecard; Adyen does not carry out reconciliation)
  • Banco Santander (Adyen carries out reconciliation and provides settlement reports)

Installment payment statuses

These high-level diagrams offer an overview of the key payment statuses you may want to look for when monitoring instalment transactions.

Settlement in instalments

The payment statuses in the diagram highlight key payment statuses in a standard instalments payment transaction.

 

Refund in instalments

The payment statuses in the diagram highlight key payment statuses in a standard refund in instalments.

 

One-off vs installment flow

One-off payment flow

A standard, basic payment transaction normally follows this flow:

Authorisation | Capture | Settlement

Transaction report:
  • Time frame: D+1
  • Reported by the acquirer.

It provides the following information:

  • Overview of captures and refunds.
  • Details about estimated payment dates, commissions, and so on.

Settlement report:

  • Time frame: D+30
  • For M-level merchants: we provide settlement reports, and we check bank statements to confirm the funds are duly received.
    For S-level merchants: we provide settlement reports, and we rely on the information we receive from acquirers.
  • Bank statement notifying that the deposit needs to be made available.

Instalment payment flow

A payment in instalments adds some steps to the process:

Authorisation | Capture | Instalments 1, 2, 3, ...| Settlement 1, 2, 3, ...

Transaction report:
  • Time frame: D+1
  • Reported by the acquirer.

It provides the following information:

  • Overview of captures and refunds.
  • Details about estimated payment dates, commissions, and so on.

Settlement report:

  • Time frame: D+30
  • For M-level merchants: we provide settlement reports, and we check bank statements to confirm the funds are duly received.
    For S-level merchants: we provide settlement reports, and we rely on the information we receive from acquirers.
  • Bank statement notifying that the deposit needs to be made available.

Installment reconciliation

The one-off and the installment flows affect reporting capabilities, and they impact the corresponding reconciliation processes.

During the account creation procedure, it is possible to define the type of flow you want to enable for the account.

  One-off Installment
Supports installments. (error) (tick)
Supports advancements. (error) (tick)
Forecast reports available. (error) (tick)

To correctly complete a transaction flow, you need to reconcile settlement and refund requests, where applicable.

Settlement reconciliation

Reconciliation is a crucial step in a transaction.
When you reconcile a payment, you verify that the authorised and captured amounts for the payment match the corresponding settlement.

Reports help you keep track of the process.
You can follow the transaction progress by checking journal entries and payment statuses.

Settlement journal entries

The reconciliation flow for a transaction where the merchant collects the shopper's payments in a set number of installments follows these steps:

  • The payment is authorised.
  • The payment is captured.
  • SentForSettle journal entry is created.
  • If the shopper chooses to pay in installments, a SettledInInstallments journal entry is created.
    Regardless of the number of installments the total payable amount is split up into, a payment can have only one SettledInInstallments journal entry.
  • The SentForSettle journal entry is balanced against SettledInInstallments.
    This occurs as soon as we receive information about the installment due dates.
    The standard time frame for this operation is usually D+1.
  • An OpenInstallment journal entry is created for each installment referring to the payment.
  • When an installment is settled, a SettledInstallment journal entry is created.
  • The OpenInstallment journal entry is balanced against its corresponding SettledInstallment entry.

Except for payment authorisation and capture, these steps are repeated for each installment in the transaction.

 

 

Refund reconciliation

Reconciling a refund is very similar to reconciling a settlement.

Refund journal entries

The reconciliation flow for active transactions where the merchant collects the shopper's payments in a set number of installments, and a refund needs to be issued, follows these steps:

  • The payment is authorised.
  • The payment is captured.
  • If the shopper requests a refund, a SentForRefund journal entry is created.
  • RefundedInInstallments journal entry is created.
    Regardless of the number of installments the total amount is split up into, a payment can have only one RefundedInInstallments journal entry.
  • The SentForRefund journal entry is balanced against RefundedInInstallments.
    This occurs as soon as we receive information about the installment due dates.
    The standard time frame for this operation is usually D+1.
  • An OpenInstallment journal entry is created for each installment referring to the payment.

    Cielo normally handles a refund request in one installment.

  • When an installment is settled/deducted/refunded, a RefundedInstallment journal entry is created.
  • The OpenInstallment journal entry is balanced against its corresponding RefundedInstallment entry.

Except for payment authorisation and capture, these steps are repeated for each installment in the transaction.

 

 

Installment reports

The report types outlined here provide you with insightful information on installment payments.

Forecast report

  • It provides information about cash flow provisioning.
    Currently, amounts in the report are gross, and dates indicate when Adyen is going to receive the funds.
    Forecasts are based on a report Adyen receives from the acquirer.
    Time frame to obtain the report: D+1.
  • It is a snapshot of the moment when the acquirer settles the funds.
    Depending on your agreement with Adyen, this moment can correspond to the time when either the funds are deposited, or when Adyen receives the funds.
    Usually, Adyen pays out merchants within two business days.

Settlement detail report

The settlement detail report provides an overview that helps you match settlements with the corresponding authorised and captured payments.

This is a crucial step to reconcile payments, and therefore to correctly finalize a transaction.

Daily/Monthly finance report in installments

  • It is an incremental version of the standard daily/monthly finance report that includes also balance information on installment accounts.
  • For convenience, the extra fields are yellow-highlighted.
  • Journal entries like SettledInInstallments, RefundedInInstallments, OpenInstallment, SettledInstallment, and RefundedInstallment provide information about open and settled installments.
  • After a payment is authorised, the balance goes through the following statuses (happy flow):
    Captured | Installments | Payable

Finance report file definition

Overview sheet

This worksheet displays an overview of the finance report.

Field name

Description

Account Type

Indicates the reporting level: either at merchant account, or company account level.
Typical values are:

  • MerchantAccount, Merchant for merchant account level reports.
  • CompanyAccountCompany for company account level reports.

Account Code

Indicates the specific company or merchant account the report has been requested for.

Adyen Settlement

Indicates the settled amount, in the primary settlement currency, for transactions where Adyen is in the money flow.

External Settlement

Indicates the settled amount, in the primary settlement currency, for transactions where Adyen is not in the money flow.

Total in [primary settlement currency]

Indicates the total amount for the line item, in the primary settlement currency.

Row name

 Description

Payments received on/in [period]

Total value of the payment requests received by the Adyen platform.

Payments authorised on/in [period]

Total value of the authorised payments for the reporting period.

Amount sent for settle on/in [period]

Total value of the transactions with a SentForSettle status during the reporting period.
By the end of the period some of these transactions may change their status to Settled, SentForSettle or CaptureFailed.

Amount sent for refund on/in [period]

Value of the transactions with a SentForRefund status during the reporting period.
By the end of the period some of these transactions may change their status to Refunded or RefundFailed.

Total amount paid out on/in [period]

Total amount of the transactions that were settled to your bank account during the reporting period.

Total receivables from Adyen at end of [period]

Total amount of Open captured balance, Open payable balance, and Deposit.

Open captured balance (gross)

Total value of the transactions with a SentForSettle status at the end of the reporting period.
This is the gross amount.

Open payable balance

Total value of the transactions where Adyen has received the funds from the bank, and where Adyen is holding the funds until the next settlement batch.
This is the net amount, minus commission fees.

Deposit

The amount withheld by Adyen.

Payment balance sheet

The payment balance sheet gives a snapshot of the end of the reporting period. It provides you with the exact value of the transactions, ordered by status.
The table groups the line items for the reporting period, and the Year To Date (YTD)/Month To Date (MTD) up to and including the reporting period.
All amounts are converted to your primary settlement currency.

Due to exchange rate fluctuations, the Opening Balance may not match the Closing Balance/End Balance from the previous period.

Field name

Description

Count

The number of transactions that make up the line item

[Primary settlement currency]

The three-character ISO code representing the primary settlement currency.
All amounts in this column are converted to this currency.

Check

Exchange rates in the report are end of month, mid rates. You can review them on the ExchangeRates worksheet in the report file.
Multi-currency transactions are converted to the primary settlement currency using end of month rates.
Due to exchange rate fluctuations over time, there may be some valuation differences; in this case, they are reported in this column.
Amounts in this column do not represent gains or losses due to currency conversion.

 

Row name

Description

Received – Opening Balance

Shows the End Balance carried over from the previous period.

Received – Received

Payments received by the Adyen platform.

Received – Refused

Payments that resulted in a refusal, either by the Adyen fraud tool or by the acquirer.

Received – Error

Payments that resulted in an error.

Received – Authorised

Payments that resulted in a successful authorisation.

Received – ReceivedPayout

Payout received by the Adyen platform.

Received – RefusedPayout

Payout that resulted in a refusal, either by the Adyen fraud tool or by the acquirer.

Received – PayoutError

Payout that resulted in an error.

Received – PayoutAuthorised

Payout that resulted in a successful authorization.

Received – End Balance

Payments whose latest status for the reporting period is Received.

Authorised – Opening Balance

Shows the End Balance carried over from the previous period.

Authorised – Authorised

Payments that resulted in a successful authorisation.

Authorised –Cancelled

Payments that were cancelled following up on a merchant's request.

Authorised – Expired

Payments whose capture request was never received.
The system flags these transactions as Expired.

Authorised – SentForSettle

Payments whose capture request was successfully received.
Transactions where Adyen is in the money flow are included here.

Authorised – SentForSettleExternally

Payments for which the Capture request was received.
Transactions where Adyen is not in the money flow are included here.

Authorised – PayoutAuthotised

Payouts that resulted in a successful authorization.

Authorised – SentForPayout

Payouts whose payout request is successfully sent to the acquirer by the Adyen platform. Payouts where Adyen is in the money flow are included here.

Authorised – SentForPayoutExternally

Payouts whose payout request is successfully sent to the acquirer the Adyen platform. Payouts where Adyen is not in the money flow are included here.

Authorised – End Balance

Payments whose latest status for the reporting period is Authorised.

Captured – Opening Balance

Shows the End Balance carried over from the previous period.

Captured – SentForSettle

Payments whose capture request was sent to the acquirer.

Captured – Settled

Payments whose capture request was sent to the acquirer, and whose funds have been received by Adyen.

Captured – CaptureFailed

Payments whose capture request was declined by the acquirer.

Captured – SentForRefund

Payments whose refund request was sent to the acquirer.

Captured – Refunded

Payments whose refund request was confirmed and successfully executed by the acquirer.

Captured – RefundFailed

Payments whose refund request was declined by the acquirer.

Captured – SentForPayout

Payouts whose payout request was sent to the acquirer.

Captured – PaidOut

Payouts whose payout request was confirmed and successfully processed by the acquirer.

Captured – PayoutFailed

Payouts whose payout request was returned by the acquirer.

Captured – End Balance

Payments whose latest status for the reporting period is SentForSettle.

Captured Externally – Opening Balance

Shows the End Balance carried over from the previous period.

Captured Externally – SentForSettle

Payments whose capture request was sent to the acquirer.

Captured Externally – SettledExternally

Payments whose capture request was sent to the acquirer, and where Adyen is not in the money flow.

Captured Externally – CaptureFailed

Payments whose capture request was declined by the acquirer.

Captured Externally – SentForRefund

Payments whose refund request was sent to the acquirer.

Captured Externally – RefundedExternally

Payments whose refund request was confirmed and successfully executed by the acquirer.

Captured Externally – RefundFailed

Payments whose refund request was declined by the acquirer.

Captured Externally – SentForPayout

Payout whose payout request was sent to the acquirer.

Captured Externally – PaidOutExternally

Payouts whose payout request was confirmed and successfully processed by the acquirer.

Captured Externally – PayoutFailed

Payouts whose payout request was returned by the acquirer.

Captured Externally – End Balance

Payments whose latest status for the reporting period is SentForSettle.

Payable – Opening Balance

Shows the End Balance carried over from the previous period.

Payable – Settled

Payments whose capture request was sent to the acquirer, and whose funds have been received by Adyen.

Payable – Refunded

Payments whose refund request was confirmed and successfully executed by the acquirer.

Payable – Fee already charged

Transaction fee that Adyen deducted from the settlements for the relevant period.

Payable – Chargeback

Payments whose final transaction status is Chargeback.

Payable – ChargebackReversed

Payments whose final transaction status is ChargebackReversed.

Payable – RefundedReversed

Payments where the issuer was unable to provide the refunded funds to the account holder, and the funds were returned to Adyen.

Payable – DepositCorrection

Required amount to adjust the deposit.

Payable – InvoiceDeduction

Total amount of invoiced fees deducted from your settlement for the reporting period.

Payable – MerchantPayout

Total amount of funds settled to your bank account.

Payable – MerchantPayoutFailed

Total amount of failed settlements to your bank for the month.

Payable – ManualCorrected

Total amount of manually corrected funds, for example discounts, if any.

Payable – PaidOut

Payouts whose payout request was confirmed and successfully executed by the acquirer.

Payable – PaidOutReversed

Payouts where the issuer was unable to pay out the funds to the account holder, and the funds were returned to Adyen.

Payable – Other

Any miscellaneous bookings that were placed in your Payable batch.

Payable – End Balance

Payments whose latest status for the reporting period is Settled, and whose funds are being held until the next settlement batch.

Deposit – Opening Balance

Shows the End Balance carried over from the previous period.

Deposit – End Balance

Shows the updated deposit amount.

Commission – Settled

Total payment method commission charged on Settled for the month.

Commission – Refunded

Total payment method commission charged on Refunded for the month.

Commission – Chargeback

Total payment method commission charged on Chargebacked for the month.

Commission – ChargebackReversed

Total payment method commission charged on ChargebackReversed for the month.

Commission – ManualCorrected

Total payment method commission charged on ManualCorrecteds for the month.

Commission – PaidOut

Total payment method commission charged on PaidOut for the month.

Commission – PaidOutReversed

Total payment  method commission charged on PaidOutReversed for the month.

Commission – Total commission

Total amount of all commissions.

Fee – Total Calculated

Total Adyen transaction fee for the month.
You can calculate this amount yourself in the following way:

(Received + SentForRefund ) * your Adyen transaction fee

Check sum / multicurrency difference

Exchange rates in the report are end of month, mid rates. You can review them on the ExchangeRates worksheet in the report file.
Multi-currency transactions are converted to the primary settlement currency using end of month rates.
Due to exchange rate fluctuations over time, there may be some valuation differences; in this case, they are reported in this column.
Amounts in this column do not represent gains or losses due to currency conversion.

Merchant payout details sheet

The Merchant payout details sheet provides details of settlement batches, which had booked payments or had a merchant payout executed during the reporting period. This sheet shows an overview of items booked to the batch, including the net settled amount and cost, as well as the amount paid out to the merchant.

The following fields are included into each detail row on this sheet:

Field name Description
Account Code Indicates the merchant account.
Batch The numeric number of the settlement batch.
Begin Date The start date, from which transactions are booked into the batch (CET time zone).
End Date The end date, until which transactions are booked into the batch (CET time zone).
Payout Date

The date on which the merchant payout was booked (CET time zone).

Note that this value is empty if the batch did not result in a payout, for example in cases of a transfer to a subsequent batch to process negative payable/capture balances.

Month The month, in which the batch was closed.
[unnamed column] The three-character ISO code representing the primary settlement currency.
Payout Amount The payout amount.
Net & Cost fields

Available for Settled, PaidOut, Refunded, Bulk Settlement, Chargeback, Chargeback Reversed, PaidOut Reversed, and RefundedReversed.

Summary of payment-level mutations during the month:

  • Net – the net credit or debit amount;
  • Cost – the cost withheld/credited from the settlement (i.e. Commission, Markup, Interchange & Scheme fees, corresponds to fields 17-20 of the settlement detail report).
Payment Cost Additional costs, which could not be directly addressed to a specific transaction (mainly R-level).
Balance Transfer BalanceTransfer to/from subsequent payable batches in order to process negative payable/capture balances or for batches that could not have been paid out.
Fee Adyen transaction fees for Received / SentForRefund / RefundedBulk transactions booked during the specified batch period.
Invoice Deduction Representing a monthly invoice that is credited/deducted from the account.
Deposit Correction Funds being withheld from/released to the account due to a change in the required security deposit (coverage of the exposure on the account).
Other Any other journal types booked to/from the settlement batch and not covered by the previous columns.
Rate The exchange rate from settlement currency to report currency.
Payout Amount Base Payout amount converted to report currency.

Settlement detail report

The settlement detail report provides an overview that helps you match settlements with the corresponding authorised and captured payments.

This is a crucial step to reconcile payments, and therefore to correctly finalize a transaction.

Payments are settled periodically to your bank account. On your bank statement, they are reported in the following way:

28-24-2013

By

1323.94.782

ADYEN

Add

EUR

1842.21

 

 

 

TX4313726XT batch 4, [yourMerchantAccountName]

 

 

 

The fields have the following meaning:

  • 1323.94.782 is Adyen's Dutch settlement bank account. Depending on the country and currency of settlement this number may be different.
  • The payment originates from ADYEN, the Adyen Client Management Foundation that receives and settles your payments.
  • TX4313726XT is the internal Adyen reference code; you can disregard this piece of information, as it is not relevant to you.
  • The batch number, batch 4 in the example, is the settlement sequence number. It starts at 1 to flag the first settlement, and it increases incrementally by one unit with each subsequent settlement.
  • 1842.21 is the total amount of the settlement. This sum matches the payout amount in the settlement detail report.

The batch number in the settlement to your bank corresponds to the batch number in the settlement detail report.
For example: https://ca-live.adyen.com/reports/download/MerchantAccount/[yourMerchantAccountName]/settlement_report_batch_4.csv

The settlement detail report itself consists of five sections:

1

Column headers/descriptions
(one line)

Company Account,Merchant Account,Psp Reference,Merchant Reference,Payment Method,Creation Date,TimeZone,Type,Modification Reference,Gross Currency,Gross Debit (GC),Gross Credit (GC),Exchange Rate,Net Currency,Net Debit (NC),Net Credit (NC),Commission (NC),Markup (NC),Scheme Fees (NC),Interchange (NC),Payment Method Variant,Modification Merchant Reference,Batch Number,Reserved4,Reserved5,Reserved6,Reserved7,Reserved8,Reserved9,Reserved10

2

Transaction details
(multiple lines)

TestCompany,TestMerchant,1813702551707653,3vpzf7,visa,2013-06-03 11:26:49,BST,Settled,1713702551795048,GBP,,5.00,1,GBP,,4.88,,0.04,0.01,0.07,visaclassic,<auto>,4,,,,,,,
[...]

3

Transaction fees
(one or multiple lines)

TestCompany,TestMerchant,,,,2013-06-11 04:55:40,BST,Fee,Transaction Fees May 2013,EUR,,,,GBP,1.46,,,,,,,,4,,,,,,,

4

Corrections
(one or multiple lines)

TestCompany,TestMerchant,,,,2012-05-10 05:37:03,CEST,DepositCorrection,DepositCorrection,EUR,,,,EUR,,78.93,,,,,,DepositCorrection,4,,,,,,,

5

Merchant payout
(one or multiple lines)

TestCompany,TestMerchant,,,,2013-06-11 04:55:40,BST,MerchantPayout,"TX977148886XT batch 4, TestMerchant batch 4, TestMerchant",EUR,,,,GBP,22.50,,,,,,,,4,,,,,,,

Multi-currency transactions 

  • If you have multiple settlement currencies, the settlement detail report contains a merchant payout line for each applicable settlement currency.
  • If a settlement batch contains transactions with processing currencies other than the settlement currency, then these gross amounts are converted to the net amount in the settlement currency.
    For example, if your settlement currency is EUR, and if you also process payments in SEK, you see both currencies and amounts in the reports, including the exchange rate used to convert the processing amount (SEK) to the settlement amount (EUR).
    To check the exchange rate used for the currency conversion, refer to the relevant Adyen's
    daily Exchange Rate Report.

Match settlements to transactions

Depending on your implementation, you can store one or more keys per transaction.
For example, you can configure your implementation to store the merchant transaction identifier generated by your system, and then passed on to Adyen via the reference or the merchantReference fields. Alternatively, you can store the Adyen-generated pspReference.
Adyen reports include both references, so you can easily tie the report line items back to the individual transactions in your system.

We recommend automating the matching process. The following basic guidelines can get you jump-started.

  • Check your bank statements against the settlement records:
    • Identify the line item in your bank statement that contains the TX...XT description and the batch number.
    • Identify the corresponding settlement detail report
    • Verify that the deposit amount matches the amount indicated in the settlement detail report.
  • Using the settlement detail report line items, update each transaction in your system with the appropriate status, as indicated in the report. For example: settled, refunded or chargeback.
  • Optional:
    • You can add a batch number field to your transaction table to look up which batch the transaction was paid out.
    • You can store the settled amount, so you can keep track of the costs per transaction.

A fully automated system leaves no room for errors, and it contributes to making your bookkeeping system correct, as far as Adyen transactions are concerned.

Report line examples

 

Settlement detail report transaction lines

Each transaction is represented by an entry. Each entry is on a separate line in the report. Each transaction line in the report describes the status of the transaction, and the reason why it was included in the settlement batch. For example: Settled or Refunded.

TestCompany,TestMerchant,1813702551707653,3vpzf7,visa,2013-06-03 11:26:49,CET,Settled,1713702551795048,GBP,,5.00,1,GBP,,4.88,,0.04,0.01,0.07,visaclassic,,,,,,,,,
TestCompany,TestMerchant,1313642467023511,324959451,visa,2013-03-26 22:37:26,CET,Chargeback,2313642467170922,EUR,349.99,,1,EUR,357.49,,7.5,,,,visaclassic,,,,,,,,,

Settlement detail report transaction fees

A transaction fee line is an entry in the report providing information on chargeable fees. A settlement report includes a transaction fee line for each month that has transactions in the settlement batch.

TestCompany,TestMerchant,,,,2013-06-11 04:55:40,CET,Fee,Transaction Fees May 2013,EUR,,,,GBP,1.46,,,,,,,,,,,,,,,

Settlement detail report deposit correction line

In the cases when Adyen may require a deposit, this is filled by withholding settlements until the deposit amount is met.

The deposit is a variable amount that may increase or decrease periodically, due to changing risk figures. In this situation, a DepositCorrection line item is included in the settlement report. This line can have a credit or a debit amount to reflect the appropriate change in the deposit amount.

TestCompany,TestMerchant,,,,2012-05-10 05:37:03,CET,DepositCorrection,Deposit Correction,EUR,,,,EUR,78.93,,,,,,,,,,,,,,,


Settlement detail report invoice correction line

At the end of each month, Adyen calculates the final invoice amount. Sometimes, it may happen that we either charged you too much, or too little. For example, this scenario can occur if you apply tiered pricing. To balance it, we book an InvoiceDeduction line item in the settlement report, when necessary.

In this example, Invoice 201111000553 refers to the invoice number mentioned in the invoice of the given month. The amount may appear with debit or credit columns.

TestCompany,TestMerchant,,,,2013-05-10 12:59:53,CET,InvoiceDeduction,Invoice 201111000553,EUR,,,,EUR,,250.22,,,,,,,4,,,,,,,

Settlement detail report transfer line

A transfer line in a settlement detail report is an entry documenting a funds transfer to your bank account. The net debit/merchant payout field holds the total amount paid out to your account, followed by the currency.

In this example, Adyen paid out 1842.21 EUR to the TestMerchant merchant account. TX4313726XT batch 4, TestMerchant is the message included in the the bank statement.

TestCompany,TestMerchant,,,,2013-06-11 04:55:40,CET ,MerchantPayout,"TX4313726XT batch 4, TestMerchant batch 4, TestMerchant",EUR,,,,EUR,1842.21,,,,,,,,,,,,,,,

Settlement detail report structure

Position

Column

Data type

Description

1

Company Account

C X80

The static name of your company account as registered in the Adyen system.

2

Merchant Account

C X80

The static name of the merchant account used to process the original payment request.
The report may contain line items for multiple merchant accounts.

3

Psp Reference

N 16

Adyen's 16-digit unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with us about this request.


It holds the PSP reference for the original authorisation response.
Character length restriction: max. 16 characters.

4

Merchant Reference

C X80

The reference number provided when initiating the payment request.

5

Payment Method

C X30

The payment method type of the payment which was processed.
For example: visa, mc, amex.

6

Creation Date

D+" "+T

The timestamp indicating when the capture was received by Adyen.
Format: YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.

7

TimeZone

A 4

The time zone the creation date in the previous column refers to.
ISO code for the configured time zone for your company account.
To check it and edit it, go to:
Customer Area | Settings | Company Settings | Time Zone (BST, CET, CEST, etc.)

8

Type *

A X50

The type of record included in a report. Allowed values:

  • Fee *
  • MiscCosts *
  • MerchantPayout *
  • Refunded
  • Settled
  • Chargeback
  • ChargebackReversed
  • RefundedReversed
  • DepositCorrection *
  • InvoiceDeduction *
  • MatchedStatement
  • ManualCorrected
  • AuthorisationSchemeFee *
  • BankInstructionReturned
  • InternalCompanyPayout
  • EpaPaid
  • BalanceTransfer
  • PaymentCost
  • SettleCost

( * ) This record type takes a C X80 data type instead of A X50.

9

Modification Reference *

N 16
C X80 *

This is Adyen's unique 16 digit code child reference that is associated with the modification request (capture, refund, chargebacks, etc).
This will be returned to you via the direct soap response of the modification request and the notification server.
For the transfer line item (type = AcquirerPayout) this field will contain the unique acquirer settlement batch number.
You also find this on your bank statement for the deposit into your bank account.

10

Gross Currency *

A 3
C X80 *

This is the three character ISO code for the currency which was used for processing the payment (transaction currency).

11

Gross Debit *

F
C X80 *

The gross debit amount; this is the amount submitted in the transaction request.
For example: 100.00.

12

Gross Credit *

F
C X80 *

The gross credit amount; this is the amount submitted in the transaction request.
For example: 100.00.

13

Exchange rate

FL

The exchange rate used for converting the gross amount into the net amount.
This will be 1 if you process and settle in the same currency.

14

Net Currency

A 3

The three character ISO code for the currency which was used for processing the payment (settlement currency).

15

Net Debit

F

The net debit amount; this is the amount submitted in the transaction request minus Acquirer fees.
For example: 100.00.

16

Net Credit

F

The net credit amount; this is the amount submitted in the transaction request minus Acquirer fees.
For example: 100.00.

17

Commission

F

The commission fee that was withheld by the acquirer. This should be the difference between the gross and net amounts.
If the Acquirer provides the transaction information at interchange level Adyen, splits the commission into:

  • Markup
  • Scheme Fees
  • Interchange.

In this case, column 17 is empty and columns 18, 19, and 20 are populated.

If the Acquirer does not provide the transaction information at interchange level, Adyen populates the total commission in column 17.
In this case, columns 18, 19, and 20 are empty.

18

Markup

F

The fee charged by the Acquiring bank.
This field will be empty if Acquirer does not provide the transaction information at the interchange level.

19

Scheme Fees

F

The fee which is charged by Visa / MC.
This field will be empty if Acquirer does not provide the transaction information at the interchange level.

20

Interchange

F

The fee charged by the Issuing bank.
This field will be empty if Acquirer does not provide the transaction information at the interchange level.

21

Payment Method Variant

C X30

The sub-brand of the payment method (if applicable)
For example: visaclassic, visadebit, mccorporate.

22

Modification Merchant Reference

C X80

This is the reference number that was provided when initiating the modification request.

23

Batch Number

I

The sequence number of the settlement.

24

DCC Markup

F

Dynamic Currency Conversion markup: a negative amount indicates a credit in favour of the merchant.

This information is available only when DCC is configured for a POS integration.
If DCC is not activated, this columns reads Reserved 4.

25

Reserved5

Reserved for future enhancements.

26

Reserved6

Reserved for future enhancements.

27

Reserved7

Reserved for future enhancements.

28

Reserved8

Reserved for future enhancements.

29

Reserved9

Reserved for future enhancements.

30

Reserved10

Reserved for future enhancements.

Journal types

Journal Type

Occurrence

Description

Fee

Debit

Adyen transaction fees for Received and SentForRefund transactions booked during the specified batch period.

MiscCosts

Debit/Credit

Costs that could not be matched with any specific transactions (for R-level).

MerchantPayout

Debit

Amount that is paid for a settlement currency from the payable batch to the merchants bank account.

Refunded


Debit

Debit for a payment that was SentForRefund.

Settled

Credit

Credit for a payment that was SentForSettle.

Chargeback

Debit

Debit for a payment that is reversed by the bank/scheme/consumer.

ChargebackReversed

Credit

Previous chargeback that is credited to the merchant after a payment is successfully defended, or after the shopper re-pays the funds.

RefundedReversed

Credit

A refund that is returned to our account as it can not be credited to the shopper by the scheme/bank or is returned by the shopper.

DepositCorrection

Debit/Credit

Funds being withheld from/release to the account due to a change in the required security deposit (coverage of the exposure on the account).

InvoiceDeduction

Debit/Credit

Representing a monthly invoice that is credited/deducted from the account

MatchedStatement

Debit/Credit

Wire transfer from merchant booked in the account.

ManualCorrected

Debit/Credit

Manual booking/adjustment by Adyen.

AuthorisationSchemeFee

Debit

Separate fees being charged for authorisations.

BankInstructionReturned

Credit

Credit for previous MerchantPayout which have not been processed successfully or which have been returned to Adyen.

InternalCompanyPayout

Debit/Credit

Internal payout related to SplitSettlements being booked from the account.

EpaPaid

Debit/Credit

Electronic Payment Advice (EPA) from the acquirer (R-level) that was confirmed by the acquirer but not settled via Adyen.

BalanceTransfer

Debit/Credit

BalanceTransfer to/from subsequent payable batches in order to process negative payable/capture balances or for batches that could not have been paid out.

PaymentCost

Debit/Credit

Additional costs which could be directly addressed to a specific transaction (mainly R-level).

SettleCost

Debit/Credit

Costs being deducted for settlement to the merchant.

PaidOut Debit

Net Debit for a payout that was SentForPayout.

PaidOutReversed

Credit

Payout returned to Adyen's account as it could not be credited to the shopper by the scheme/bank or is returned by the shopper.

Legend

Reports are generated using UTF-8 encoding.
Type Code Description

Numeric types

I Integer (whole number.
FL Floating point number.
F Fixed point number (for amounts, precision is based on the currency exponent).

Character types

A Text field (alpha characters only)
N Text field (numeric characters only, treat as text)
AN Text field (alphanumeric characters only)
C Text field (unicode character set)

Other types

D Date field (Format: YYYY-MM-DD)
T Time field (format: HH:MM:SS)
  • Optionally a number following the type indicates the length of the field.
  • A length indication preceded by "X" indicates there is no hard limit imposed on the length of the field and that the value should be taken as a practical guideline.

For fields with *

The Data Type changes depending upon the record Type. Where the Type is one of the following values ('Fee', 'MiscCosts', 'MerchantPayout', 'InvoiceDeduction', 'DepositCorrection') the Data Type changes to C X80.

External settlement detail report structure

Position

Column Name

Data Type

Description

1

Company Account

C X80

The static name of your company account within the Adyen system.

2

Merchant Account

C X80

The static name of the merchant account that was used to process the original payment request. The report may contain line items for multiple merchant accounts.

3

Psp Reference

N

In most instances, this is Adyen's 16 digit unique reference number for the payment; it denotes the PSP reference for the original authorisation request.
For Unmatched transactions, this field may be populated with a reference from the Acquiring bank and the Data Type format may vary to match the format of the Acquiring bank.
For the transfer line item (Type = 'AcquirerPayout') this field will contain the unique Acquirer settlement batch number, you will also find this on your bank statement for the deposit into your bank account.

4

Merchant Reference

C X80

This is the reference number that was provided when initiating the payment request.

5

Payment Method

C X30

The payment method type of the payment which was processed. For example: visa, mc, amex.

6

Creation Date

D+" "+T

The timestamp of when the payment was received by the Adyen system. The format is YYYY-MM-DD HH:MM:SS, for example: 2012-07-26 19:58:55.

7

TimeZone

A 4

The time zone of the previous column. This is the ISO Code for the timezone which is set up on your company account:
Customer Area >> Settings >> Company Settings >> Time Zone (BST, CET, CEST etc)

8

Type

C X50

The possible values are (see description of journal types):

  • AcquirerPayout
  • AdjustmentExternallyWithInfo
  • SettledExternallyWithInfo
  • ChargebackExternallyWithInfo
  • ChargebackReversedExternallyWithInfo
  • RefundedExternallyWithInfo
  • SettledInstallmentExternallyWithInfo
  • RefundedInstallmentExternallyWithInfo
  • AdvancementCommissionExternallyWithInfo
  • UnmatchedRefundedExternallyWithInfo
  • UnmatchedSettledExternallyWithInfo
  • UnmatchedChargebackExternallyWithInfo
  • UnmatchedChargebackReversedExternallyWithInfo
  • UnmatchedBatchExternallyWithInfo

9

Modification Reference

N

In most instances, this is Adyen's unique 16 digit code child reference that is associated with the modification request (capture, refund, chargebacks, etc). This will be returned to you via the direct soap response of the modification request and the notification server.
For Unmatched transactions, this field may be populated with a reference from the Acquiring bank and the Data Type format may vary to match the format of the Acquiring bank.

10

Gross Currency

A 3

This is the three character ISO code for the currency which was used for processing the payment (transaction currency).

11

Gross Debit

F

The gross debit amount; this is the amount submitted in the transaction request. For example, 100.00.

12

Gross Credit

F

The gross credit amount; this is the amount submitted in the transaction request. For example, 100.00.

13

Exchange rate

F

The exchange rate used for converting the gross amount into the net amount. This will be 1 if you process and settle in the same currency.

14

Net Currency

A 3

The three character ISO code for the currency which was used for processing the payment (settlement currency).

15

Net Debit

F

The net debit amount; this is the amount submitted in the transaction request minus Acquirer fees. For example, 100.00.

16

Net Credit

F

The net credit amount; this is the amount submitted in the transaction request minus Acquirer fees. For example, 100.00.

17

Commission

F

The commission fee that was withheld by the acquirer. This should be the difference between the gross and net amounts.
If the Acquirer provides the transaction information at the interchange level Adyen will split the commission into the Markup, Scheme Fees and Interchange. In this scenario column 17 will be empty and columns 18, 19, and 20 will be populated.
If the Acquirer does not provide the transaction information at the interchange level Adyen will populate the total commission in column 17 and columns 18, 19, and 20 will be empty.

18

Markup

F

The fee charged by the Acquiring bank. This field will be empty if Acquirer does not provide the transaction information at the interchange level.

19

Scheme Fees

F

The fee which is charged by Visa / MC. This field will be empty if Acquirer does not provide the transaction information at the interchange level.

20

Interchange

F

The fee charged by the Issuing bank. This field will be empty if Acquirer does not provide the transaction information at the interchange level.

21

Payment Method Variant

C X30

The payment method sub-type of the payment which was processed. For example: visa classic, mc, amex.

22

Acquirer

C X80

The name of the Acquirer that processed the original payment. For example: Cielo, Redecard.

23

MID

C X50

The merchant ID from the Acquirer that was used for processing the payment.

24

ARN

C X50

Acquirer Reference Number, a unique number that tags a credit card transaction when it goes from the merchant's bank (The Acquiring Bank) through to the card scheme at the cardholder's bank (The Issuer).

25

Acquirer Reference

C X80

The Acquirer's unique ID for the payment (if provided).

26

Modification Merchant Reference

C X80

For modifications like capture or refund, the (optional) modification reference supplied by the merchant.

27

Reserved7/Installments

Where installment transactions are applicable, this field will show the installment that this line item pertains to. For example, 6/9 to indicate that this is the 6th of 9 installments.
For all other scenarios this field is reserved for future enhancements

28

Reserved8

Reserved for future enhancements

29

Reserved9

Reserved for future enhancements

30

Reserved10

Reserved for future enhancements

Report journal types

Journal Type

Occurrence

Description

AcquirerPayout

Debit/Credit

Amount that is paid by the acquirer directly to the merchant.

AdjustmentExternallyWithInfo

Debit/Credit

Unknown settlement from the acquirer that could not be matched with a payment.

SettledExternallyWithInfo

Credit

Credit from the acquirer for a payment that was SentForSettle.

ChargebackExternallyWithInfo

Debit

Debit from the acquirer for a payment that is reversed by the bank/scheme/consumer.

ChargebackReversedExternallyWithInfo

Credit

Previous chargeback that is credited as a payment was defended successfully or the shopper re-paid the funds.

RefundedExternallyWithInfo

Debit

Debit from the acquirer for a payment that was SentForRefund.

SettledInstallmentExternallyWithInfo

Credit

Credit from the acquirer for an installment that was SentForSettle.

RefundedInstallmentExternallyWithInfo

Debit

Debit from the acquirer for an installment that was SentForRefund.

AdvancementCommissionExternallyWithInfo

Debit

Commission for Advancements deducted by the acquirer.

UnmatchedRefundedExternallyWithInfo

Debit

Refund from the acquirer that could not be matched/installment.

UnmatchedSettledExternallyWithInfo

Credit

Settlement from the acquirer that could not be matched with a payment/installment.

UnmatchedChargebackExternallyWithInfo

Debit

Chargeback from the acquirer that could not be match with a payment/installment.

UnmatchedChargebackReversedExternallyWithInfo

Credit

ChargebackReversed from the acquirer that could not be match with a payment/installment.

UnmatchedBatchExternallyWithInfo

Debit/Credit

Installments from the acquirer that could not be matched.

Report legend

Reports are generated using UTF-8 encoding.
Type Code Description

Numeric types

I Integer (whole number.
FL Floating point number.
F Fixed point number (for amounts, precision is based on the currency exponent).

Character types

A Text field (alpha characters only)
N Text field (numeric characters only, treat as text)
AN Text field (alphanumeric characters only)
C Text field (unicode character set)

Other types

D Date field (Format: YYYY-MM-DD)
T Time field (format: HH:MM:SS)
  • Optionally a number following the type indicates the length of the field.
  • A length indication preceded by "X" indicates there is no hard limit imposed on the length of the field and that the value should be taken as a practical guideline.

For fields with *

The Data Type changes depending upon the record Type. Where the Type is one of the following values ('Fee', 'MiscCosts', 'MerchantPayout', 'InvoiceDeduction', 'DepositCorrection') the Data Type changes to C X80.

Dispute report structure

Position

Column Name

Data Type

Description

1

Company Account

C X80

The static name of your company account within the Adyen system.

2

Merchant Account

C X80

The static name of the merchant account that was used to process the original payment request. The report may contain line items for multiple merchant accounts.

3

Psp Reference

N 16

This is Adyen's 16 digit unique reference number for the payment; it denotes the PSP reference for the original authorisation request.

4

Merchant Reference

C X80

This is the reference number that was provided when initiating the payment request.

5

Payment Method

C X30

The payment method type of the payment which was processed. For example: visa, mc, amex.

6

Record Date

D+" "+T

The timestamp of when the dispute event took place as entered into Adyen's accounting system. The format is YYYY-MM-DD HH:MM:SS, for example: 2012-07-26 19:58:55.

7

Record Date TimeZone

A 4

The time zone of the previous column. This is the ISO Code for the timezone which is set up on your company account:
Customer Area >> Settings >> Company Settings >> Time Zone (BST, CET, CEST etc).

8

Dispute Currency

A 3

Disputes don't have to be in the original transaction currency, but can be in the currency of the card holder. Also disputes can be of a lower value than the original transaction. This is the three character ISO code for the dispute amount currency.

9

Dispute Amount

N 16

The dispute amount; for an explanation, see previous record. For example, 100.00.

10

Record Type

C X50

The dispute accounting record type, e.g.:
RequestForInformationNotificationOfChargebackChargeback InformationSuppliedChargebackReversed NotificationOfFraud

11

Dispute PSP Reference

N 16

This is Adyen's 16 digit unique reference number for the dispute.

12

Dispute Reason

C X256

The dispute reason (free format) provided by the bank or payment method.

13

RFI Scheme Code

C X30

The payment method scheme/institution which issued the code in the following column. E.g.:
visamcamex

14

RFI Reason Code

C X30

The Request for Information reason code as provided by the bank or payment method. The mapping is defined by the scheme/institution (see previous column). This is blank if no RFI was issued.

15

CB Scheme Code

C X30

The payment method scheme/institution which issued the code in the following column. E.g.:
visamcamex

16

CB Reason Code

C X30

The Chargeback reason code as provided by the bank or payment method. The mapping is defined by the scheme/institution (see previous column). This may be blank if there is not formal coding for reasons (e.g. Some direct debits), in which case the "Dispute Reason" column should be consulted.

17

Notification of Fraud Scheme Code

C X30

The payment method scheme/institution which issued the code in the following column. E.g.:
visamcamex

18

Notification of Fraud Reason Code

C X30

The Notification of Fraud reason code as provided by the bank or payment method. The mapping is defined by the scheme/institution (see previous column).

19

Payment Date

D+" "+T

The date of the original payment (authorisation).

20

Payment Date TimeZone

A 4

The time zone of the previous column. This is the ISO Code for the timezone which is set up on your company account:
Customer Area >> Settings >> Company Settings >> Time Zone (BST, CET, CEST etc).

21

Payment Currency

A 3

The three character ISO code for the currency which was used for processing the payment. (may differ from the dispute currency in rare cases).

22

Payment Amount

F

The amount of the original payment (authorisation amount).

23

Dispute Date

D+" "+T

The date the dispute was first entered into the system. This can be the date of the RFI.

24

Dispute Date TimeZone

A 4

The time zone of the previous column. This is the ISO Code for the timezone which is set up on your company account:
Customer Area >> Settings >> Company Settings >> Time Zone (BST, CET, CEST etc).

25

Dispute ARN

C X50

Acquirer Reference Number, a unique number that tags a dispute when it goes from the merchant's bank (The Acquiring Bank).

26

User Name

C X80

The user (interactive or webservice user) who performed the action resulting in the accounting record. If the record was created by an automated internal process the value "system" is used.

27

Risk Scoring

I

The total risk scoring value of the original payment.

28

Shopper Interaction

A 30

The transaction type (values: Ecommerce, ContAuth, POS, Moto).

29

Shopper Name

C X80

The name of the shopper/consumer as provided during the original transaction (if available).

30

Shopper Email

C X256

The email address of the shopper/consumer as provided during the original transaction (if available).

31

Shopper Reference

C X256

The supplied customer id/reference as supplied in the original transaction.

32

Shopper PAN

AN X80

The account number of the shopper/consumer. In case of card payments, the last four digits of the card number.

33

IBAN

AN X80

The shopper full IBAN number.

34

BIC

AN X80

The shopper full BIC number.

35

Shopper IP

C X50

The IP address (IPV4 or IPV6) of the shopper/consumer as provided during the original transaction (if available)

36

Shopper Country

A 2

The ISO country code of the shopper (if available).

37

Issuer Country

A 2

The ISO country code of the issuer (if available).

38

Issuer ID

AN 30

The unique identifier of the issuer. In case of card payments this will be the issuer BIN (first 6 digits of the card number).

39

3D Directory Response

A 1

For payments which were processed using 3D Secure (Secure Code / Verified by Visa), the directory response (values: Y,N,U,E).

40

3D Authentication Response

A 1

For payments which were processed using 3D Secure (Secure Code / Verified by Visa) and had directory response 'Y', the authentication response (values: Y,N,U,A,E).

41

CVC2 Response

N 1

The result passed back by the issuer after verifying the CVC2 (or CVV2/CID in case of Visa/Amex).

42

AVS Response

N 2

If AVS (Address Verification) was performed, the result of the AVS check.

43

Auto Defense

A 4

Set to 'true', if chargeback was auto-defended by Adyen. Empty if it was not.

44

Dispute End Date

D+" "+T

Date and time of day when dispute defense period ended.

45

Dispute End Date TimeZone

A 4

The time zone of the previous column. This is the ISO Code for the timezone which is set up on your company account:
Customer Area >> Settings >> Company Settings >> Time Zone (BST, CET, CEST etc).

46

Reserved 4

Reserved for future enhancements.

47

Reserved 5

Reserved for future enhancements.

Dispute report legend

Reports are generated using UTF-8 encoding.
Type Code Description

Numeric types

I Integer (whole number.
FL Floating point number.
F Fixed point number (for amounts, precision is based on the currency exponent).

Character types

A Text field (alpha characters only)
N Text field (numeric characters only, treat as text)
AN Text field (alphanumeric characters only)
C Text field (unicode character set)

Other types

D Date field (Format: YYYY-MM-DD)
T Time field (format: HH:MM:SS)
  • Optionally a number following the type indicates the length of the field.
  • A length indication preceded by "X" indicates there is no hard limit imposed on the length of the field and that the value should be taken as a practical guideline.

For fields with *

The Data Type changes depending upon the record Type. Where the Type is one of the following values ('Fee', 'MiscCosts', 'MerchantPayout', 'InvoiceDeduction', 'DepositCorrection') the Data Type changes to C X80.

Payment accounting report structure

Position

Column Name

Data Type

Description

1

Company Account

C X80

The static name of your company account within the Adyen system.

2

Merchant Account

C X80

The static name of the merchant account that was used to process the original payment request. The report may contain line items for multiple merchant accounts.

3

Psp Reference

N 16

This is Adyen's 16 digit unique reference number for the payment; it denotes the PSP reference for the original authorisation request.

4

Merchant Reference

C X80

This is the reference number that was provided when initiating the payment request.

5

Payment Method

C X30

The payment method type of the payment which was processed. For example: visa, mc, amex.

6

Booking Date

D+" "+T

The timestamp of when the event took place as entered into Adyen's accounting system. The format is YYYY-MM-DD HH:MM:SS, for example: 2012-07-26 19:58:55.

7

TimeZone

A 4

The time zone of the previous column. This is the ISO Code for the timezone which is set up on your company account:
Customer Area >> Settings >> Company Settings >> Time Zone (BST, CET, CEST etc)

8

Main Currency

A 3

While the accounting record may move funds on multiple account "registers", each record type has a primary register which can be seen as a summary of the record. We refer to this as the main amount. This is the three character ISO code for the main amount currency.

9

Main Amount

N 16

The main amount; for an explanation, see previous record. For example, 100.00.

10

Record Type

C X50

The accounting record type, e.g.:
ReceivedAuthorisedRefusedSentForSettleSettledSentForRefundRefunded

11

Payment Currency

A 3

The three character ISO code for the currency which was used for processing the payment.

12

Received (PC)

F

The amount (in Payment Currency) debited or credited on the Received accounting register.

13

Authorised (PC)

F

The amount (in Payment Currency) debited or credited on the Authorised accounting register.

14

Captured (PC)

F

The amount (in Payment Currency) debited or credited on the Captured accounting register.

15

Settlement Currency

A 3

The three character ISO code for the currency which was used when settling the payment.

16

Payable (SC)

F

The amount (in Settlement Currency) debited or credited on the Payable accounting register (i.e. funds which will be paid out to your bank account).

17

Commission (SC)

F

The commission fee that was withheld by the acquirer (in Settlement Currency)
If the Acquirer provides the transaction information at the interchange level Adyen will split the commission into the Markup, Scheme Fees and Interchange registers instead.

18

Markup (SC)

F

The fee charged by the Acquiring bank (in Settlement Currency).

19

Scheme Fees (SC)

F

The fee which is charged by e.g. Visa / MC (in Settlement Currency).

20

Interchange (SC)

F

The fee charged by the Issuing bank (in Settlement Currency).

21

Processing Fee Currency

A 3

The currency in which the processing (or gateway) fee is charged.

22

Processing Fee (FC)

F

The amount (in Processing Fee Currency) charged on the Processing Fee accounting register.

23

User Name

C X80

The user (interactive or webservice user) who performed the action resulting in the accounting record. If the record was created by an automated internal process the value "system" is used.

24

Payment Method Variant

C X30

The subbrand of the payment method (if applicable) For example: visaclassic, visadebit, mccorporate.

25

Modification Merchant Reference

C X80

For modifications like capture or refund, the (optional) modification reference supplied by the merchant.

26

Reserved3

Reserved for future enhancements

27

Reserved4

Reserved for future enhancements

28

Reserved5

Reserved for future enhancements

29

Reserved6

Reserved for future enhancements

30

Reserved7

Reserved for future enhancements

31

Reserved8

Reserved for future enhancements

32

Reserved9

Reserved for future enhancements

33

Reserved10

Reserved for future enhancements

Payment accounting report legend

Reports are generated using UTF-8 encoding.
Type Code Description

Numeric types

I Integer (whole number.
FL Floating point number.
F Fixed point number (for amounts, precision is based on the currency exponent).

Character types

A Text field (alpha characters only)
N Text field (numeric characters only, treat as text)
AN Text field (alphanumeric characters only)
C Text field (unicode character set)

Other types

D Date field (Format: YYYY-MM-DD)
T Time field (format: HH:MM:SS)
  • Optionally a number following the type indicates the length of the field.
  • A length indication preceded by "X" indicates there is no hard limit imposed on the length of the field and that the value should be taken as a practical guideline.

For fields with *

The Data Type changes depending upon the record Type. Where the Type is one of the following values ('Fee', 'MiscCosts', 'MerchantPayout', 'InvoiceDeduction', 'DepositCorrection') the Data Type changes to C X80.

Received payment detail report structure

Position

Column name

Data type

Description

1

Company Account

C X80

The static name of your company account within the Adyen system.

2

Merchant Account

C X80

The static name of the merchant account that was used to process the original payment request.
The report may contain line items for multiple merchant accounts.

3

Psp Reference

N 16

Adyen's 16-digit unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with us about this request.

4

Merchant Reference

C X80

This is the reference number that was provided when initiating the payment request.

5

Payment Method

C X30

The payment method type of the payment which was processed. For example: visa, mc, amex.

6

Creation Date

D+" "+T

The timestamp indicating when the payment was created, as entered into Adyen's system.
Format: YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.

7

TimeZone

A 4

The creation date time zone.
This is the ISO code for the time zone which is set up on your company account.
In the Adyen Customer Area (CA), go to Settings | Company Settings | Time Zone (BST, CET, CEST etc).

8

Currency

A 3

The three-character ISO currency code.

9

Amount

N 16

The amount of the payment (authorisation amount).

10

Type

C X50

The record type.
For this report, the corresponding value is always Payment.

11

Risk Scoring

I

The total risk scoring value of the payment.

12

Shopper Interaction

A 30

The transaction type.
Allowed values:

  • Ecommerce
  • ContAuth
  • POS
  • Moto

13

Shopper Name

C X80

The name of the shopper/consumer, as provided with the transaction, if available.

14

Shopper PAN

AN X80

The account number of the shopper/consumer.
In case of card payments, the last four digits of the card number.
For SEPA, this field shows the IBAN and BIC in the following format: IBAN/BIC.

15

Shopper IP

C X50

The IP address (IPV4 or IPV6) of the shopper/consumer as provided during the original transaction, if available.

16

Shopper Country

A 2

The ISO country code of the shopper (if available, otherwise computed based on the shopper's IP address).

17

Issuer Name

C X256

The name of the issuing bank, if available.

18

Issuer ID

AN 30

The unique identifier of the issuer.
In case of card payments this will be the issuer BIN (first 6 digits of the card number).

19

Issuer City

C X80

The city of the issuer (if available).

20

Issuer Country

A 2

The ISO country code of the issuer.

21

Acquirer Response

A X30

The normalised response from the acquirer.
Not necessarily the final status of the payment.

22

Authorisation Code

C X50

If the payment was not declined, the authorisation code.

23

Shopper Email

C X256

The email address of the shopper/consumer, as provided during the original transaction (if available).

24

Shopper Reference

C X256

The supplied customer id/reference as supplied in the original transaction.

25

3D Directory Response

A 1

For payments which were processed using 3D Secure (Secure Code / Verified by Visa), the directory response
(values: Y,N,U,E).

26

3D Authentication Response

A 1

For payments processed with 3D Secure (Secure Code / Verified by Visa) and directory response Y, this holds the authentication response
(values: Y,N,U,A,E).

27

CVC2 Response

N 1

The result passed back by the issuer after verifying the CVC2 (or CVV2/CID in case of Visa/Amex).

28

AVS Response

N 2

If AVS (Address Verification) was performed, the result of the AVS check.

29

Billing Street

C X256

The street part of the billing address.

30

Billing House Number / Name

C X256

The house number or name part of the billing address.

31

Billing City

C X256

The city part of the billing address.

32

Billing Postal Code / Zip Code

C X30

The zip code or postal code part of the billing address.

33

Billing State / Province

C X256

The state or province of the billing address.

34

Billing Country

A 2

The ISO country code of the of the billing address.

35

Delivery Street

C X256

The street part of the delivery address.

36

Delivery House Number / Name

C X256

The house number or name part of the delivery address.

37

Delivery City

C X256

The city part of the delivery address.

38

Delivery Postal Code / Zip Code

C X30

The zip code or postal code part of the delivery address.

39

Delivery State / Province

C X256

The state or province of the delivery address.

40

Delivery Country

A 2

The ISO country code of the of the delivery address.

41

Acquirer Reference

C X256

Reference number for the transaction provided by the acquirer.

42

Payment Method Variant

C X30

The payment method sub-brand, or the main payment method if not available (e.g. mccredit or visagold).

43

Raw acquirer response

C X256

The raw response we receive from the acquirer, where available.

44

DCC

C X30

Dynamic Currency Conversion: indicates whether DCC was used or not during a transaction.

This information is available only when DCC is configured for a POS integration.
If DCC is not activated, this columns reads Reserved 4.

45

Reserved 5

Reserved for future enhancements

46

Reserved 6

Reserved for future enhancements

47

Reserved 7

Reserved for future enhancements

48

Reserved 8

Reserved for future enhancements

49

Reserved 9

Reserved for future enhancements

50

Reserved 10

Reserved for future enhancements

  

Received payment detail report legend

Reports are generated using UTF-8 encoding.
Type Code Description

Numeric types

I Integer (whole number.
FL Floating point number.
F Fixed point number (for amounts, precision is based on the currency exponent).

Character types

A Text field (alpha characters only)
N Text field (numeric characters only, treat as text)
AN Text field (alphanumeric characters only)
C Text field (unicode character set)

Other types

D Date field (Format: YYYY-MM-DD)
T Time field (format: HH:MM:SS)
  • Optionally a number following the type indicates the length of the field.
  • A length indication preceded by "X" indicates there is no hard limit imposed on the length of the field and that the value should be taken as a practical guideline.

For fields with *

The Data Type changes depending upon the record Type. Where the Type is one of the following values ('Fee', 'MiscCosts', 'MerchantPayout', 'InvoiceDeduction', 'DepositCorrection') the Data Type changes to C X80.

Report samples

As a reference, you can find here some samples of common reports like settlement detail report, monthly finance report, daily finance report, and so on.
Standard file formats for the reports are .ods and .csv.
You can download a ZIP archive containing the whole report sample batch.

Daily finance report

File name SAMPLE_daily_finance_report_2013_09_09
File format .ods

Monthly finance report

File name SAMPLE_Monthly_finance_report
File format .xls

Payments accounting report

File name SAMPLE_payments_accounting_report_2017_02_03
File format .csv


Company Account Merchant Account Psp Reference Merchant Reference Payment Method Creation Date TimeZone Type Modification Reference Gross Currency Gross Debit (GC) Gross Credit (GC) Exchange Rate Net Currency Net Debit (NC) Net Credit (NC) Commission (NC) Markup (NC) Scheme Fees (NC) Interchange (NC) Payment Method Variant Acquirer MID ARN Acquirer Reference Reserved6 Reserved7 Reserved8 Reserved9 Reserved10
ExampleCompany CoMobile 1234567891011121 COABN3W-277688 amex_applepay 2016-06-19 23:24:22 BST SentForSettle 2300000000000000 GBP 43 1 GBP 0 amex_applepay Amex 9000000007 12ABCD345EF
ExampleCompany CoMobile 1234567891011122 COBF2QS-277712 amex_applepay 2016-06-19 23:24:49 BST SentForSettle 2300000000000001 GBP 21.98 1 GBP 0 amex_applepay Amex 9600000000 12ABCD345EF
ExampleCompany CoMobile 1234567891011123 COA1RQP-278525 amex_applepay 2016-06-19 23:44:43 BST SentForSettle 2300000000000002 EUR 152.99 1 EUR 0 amex_applepay Amex 9500000000 12ABCD345EF
ExampleCompany CoMobile 1234567891011124 COA1RW5-278675 amex_applepay 2016-06-19 23:48:44 BST SentForSettle 2300000000000003 EUR 118.65 1 EUR 0 amex_applepay Amex 9500000000 12ABCD345EF
ExampleCompany CoMobile 1234567891011125 COA1S2B-278821 amex_applepay 2016-06-19 23:53:10 BST SentForSettle 2300000000000004 EUR 119.66 1 EUR 0 amex_applepay Amex 9500000000 12ABCD345EF
ExampleCompany CoWeb 1234567891011126 COA1S8R-279026 mc 2016-06-19 23:59:51 BST SentForSettle 2300000000000005 GBP 149.96 1 GBP 0 mcdebit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011127 COA1S8W-279028 visa 2016-06-20 00:00:05 BST SentForSettle 2300000000000010 GBP 204.93 1 GBP 0 visadebit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011128 CORANM1-278987 mc 2016-06-19 23:58:51 BST SentForRefund 2300000000000011 EUR 119.18 1 EUR 0 mccredit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011129 COA1CKZ-267009 visa 2016-06-19 21:09:09 BST SentForRefund 2300000000000012 GBP 114.2 1 GBP 0 visadebit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011130 COB1DFG-238646 visa 2016-06-19 16:41:01 BST SentForRefund 2300000000000013 EUR 48.6 1 EUR 0 visadebit EuroConex ExampleCompany 12ABCD345EF
ExampleCompany CoWeb 1234567891011131 COA15PL-261215 visa 2016-06-19 20:13:59 BST SentForRefund 2300000000000014 CHF 76.92 1 CHF 0 visadebit EuroConex ExampleCompany 12ABCD345EF
ExampleCompany CoB2B 1234567891011132 COBZP9C-232714 visa 2016-06-09 22:36:10 BST SentForRefund 2300000000000015 GBP 59.99 1 GBP 0 visadebit Lloyds 500000000000000
ExampleCompany CoB2B 1234567891011133 COA1GMD-269880 amex 2016-06-19 21:37:08 BST SentForRefund 2300000000000020 GBP 108.2 1 GBP 0 amex Amex 9500000000 12ABCD345EF
ExampleCompany CoB2B 1234567891011134 COA1JLT-271739 mc 2016-06-19 21:56:11 BST SentForRefund 2300000000000021 EUR 62.6 1 EUR 0 mccredit Lloyds 500000000000000
ExampleCompany CoB2B 1234567891011135 COA1GMD-269880 amex 2016-06-19 21:37:08 BST SentForRefund 2300000000000022 GBP 108.2 1 GBP 0 amex Amex 9500000000 12ABCD345EF
ExampleCompany CoB2B 1234567891011136 COA1JLT-271739 mc 2016-06-19 21:56:11 BST SentForRefund 2300000000000023 EUR 62.6 1 EUR 0 mccredit Lloyds 500000000000000
ExampleCompany CoB2B 1234567891011137 COA1JRF-271921 visa 2016-06-19 21:58:27 BST SentForRefund 2300000000000024 USD 312.18 1 USD 0 visaclassic Lloyds 500000000000000
ExampleCompany CoB2B 1234567891011139 COA1JRF-271921 visa 2016-06-19 21:58:27 BST SentForRefund 2300000000000025 USD 312.18 1 USD 0 visaclassic Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011140 COS3JCW-212151 visa 2016-06-19 11:48:30 BST SentForRefund 2300000000000026 GBP 75.42 1 GBP 0 visadebit EuroConex ExampleCompany 123456789101
ExampleCompany CoWeb 1234567891011141 COA1BRH-266223 mc 2016-06-19 21:01:43 BST SentForRefund 2300000000000027 CHF 11.93 1 CHF 0 mccredit EuroConex ExampleCompany 123456789101

Received payments report

File name SAMPLE_received_payments_report_2017_Feb_6
File format .csv

Company Account Merchant Account Psp Reference Merchant Reference Payment Method Creation Date TimeZone Currency Amount Type Risk Scoring Shopper Interaction Shopper Name Shopper PAN Shopper IP Shopper Country Issuer Name Issuer Id Issuer City Issuer Country Acquirer Response Authorisation Code Shopper Email Shopper Reference 3D Directory Response 3D Authentication Response CVC2 Response AVS Response Billing Street Billing House Number / Name Billing City Billing Postal Code / ZIP Billing State / Province Billing Country Delivery Street Delivery House Number / Name Delivery City Delivery Postal Code / ZIP Delivery State / Province Delivery Country Acquirer Reference Payment Method Variant Reserved3 Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved9 Reserved10
TestCompany TestMerchant 4713726295724230 326078880 mc 2017-01-30 11:03:40 CEST EUR 55.97 Payment 0 Ecommerce John Doe 2010 83.53.51.61 ES 544958 ES DECLINED johndoe@gmail.com 12518961 2 0 mccredit
TestCompany TestMerchant 1313726295631970 326078963 mc 2017-01-30 11:03:40 CEST EUR 49.95 Payment 40 Ecommerce John Doe 6176 92.109.130.254 NL 541592 GB APPROVED 1294 johndoe@gmail.com 16331379 1 0 mccredit
TestCompany TestMerchant 1713726294849740 326078919 paypal 2017-01-30 11:03:40 CEST EUR 49.95 Payment 0 Ecommerce John Doe 92.201.7.29 DE APPROVED johndoe@gmail.com 24238610 0 0 paypal
TestCompany TestMerchant 4413726294187150 326078827 paypal 2017-01-30 11:03:40 CEST EUR 49.95 Payment 40 Ecommerce John Doe 151.21.6.225 IT APPROVED johndoe@gmail.com 32776577 0 0 paypal
TestCompany TestMerchant 4813726290089330 326078818 visa 2017-01-30 11:03:40 CEST EUR 52.47 Payment 0 Ecommerce John Doe 1007 91.117.17.232 ES 490943 ES APPROVED 476113 johndoe@gmail.com 28316598 1 0 visagold
TestCompany TestMerchant 1313726289709080 326078820 paypal 2017-01-30 11:03:40 CEST NOK 572.09 Payment 0 Ecommerce John Doe 79.161.246.9 NO APPROVED johndoe@gmail.com 25787718 0 0 paypal
TestCompany TestMerchant 4313726289972770 326078816 visa 2017-01-30 11:03:40 CEST DKK 524.95 Payment 0 Ecommerce John Doe 958 188.181.224.119 DK 457175 DK APPROVED 235006 johndoe@gmail.com 22866801 1 0 visadankort
TestCompany TestMerchant 4413726289793410 326078817 mc 2017-01-30 11:03:40 CEST EUR 29.95 Payment 40 Ecommerce John Doe 3038 94.162.46.47 IT 550075 IT APPROVED T04736 johndoe@gmail.com 27156014 1 0 mccredit
TestCompany TestMerchant 4713726289782120 326078819 visa 2017-01-30 11:03:40 CEST EUR 39.95 Payment 40 Ecommerce John Doe 9389 79.30.103.250 IT 405785 IT APPROVED 85779 johndoe@gmail.com 35985150 1 0 visaclassic
TestCompany TestMerchant 1313726289337330 326078794 visa 2017-01-30 11:03:40 CEST SEK 534.95 Payment 0 Ecommerce John Doe 8213 78.73.245.93 SE 458109 SE APPROVED 153438 johndoe@gmail.com 15940405 1 0 visadebit
TestCompany TestMerchant 1713726289180440 326078862 visa 2017-01-30 11:03:40 CEST PLN 66.67 Payment 0 Ecommerce John Doe 5742 89.70.131.115 PL 430542 PL APPROVED 98191 johndoe@gmail.com 27647836 1 0 visadebit
TestCompany TestMerchant 4313726288744460 326078790 paypal 2017-01-30 11:03:40 CEST EUR 55.97 Payment 40 Ecommerce John Doe 82.246.107.19 FR APPROVED johndoe@gmail.com 45646603 0 0 paypal
TestCompany TestMerchant 4313726288382800 326078903 paypal 2017-01-30 11:03:40 CEST NOK 399 Payment 0 Ecommerce John Doe 84.52.200.64 NO APPROVED johndoe@gmail.com 32905709 0 0 paypal
TestCompany TestMerchant 1313726288533200 326078900 mc 2017-01-30 11:03:40 CEST EUR 29.95 Payment 0 Ecommerce John Doe 502 79.156.170.55 ES 548912 ES APPROVED 854080 johndoe@gmail.com 22549069 1 0 mccredit
TestCompany TestMerchant 1313726287989980 326078791 paypal 2017-01-30 11:03:40 CEST EUR 55.97 Payment 0 Ecommerce John Doe 81.39.61.2 ES APPROVED johndoe@gmail.com 40213737 0 0 paypal
TestCompany TestMerchant 4713726288152060 326078809 paypal 2017-01-30 11:03:40 CEST EUR 44.96 Payment 40 Ecommerce John Doe 88.166.19.91 FR APPROVED johndoe@gmail.com 16299917 0 0 paypal
TestCompany TestMerchant 1313726288321810 326078646 visa 2017-01-30 11:03:40 CEST EUR 55.97 Payment 1 Ecommerce John Doe 9373 81.164.243.224 BE 489108 BE APPROVED 85632 johndoe@gmail.com 1650761 1 0 visaclassic
TestCompany TestMerchant 1313726288120690 326078807 visa 2017-01-30 11:03:40 CEST EUR 49.95 Payment 40 Ecommerce John Doe 7770 89.226.124.6 FR 497641 FR APPROVED 354241 johndoe@gmail.com 39270206 1 0 visadebit
TestCompany TestMerchant 4813726288046200 326078788 mc 2017-01-30 11:03:40 CEST EUR 38.47 Payment 40 Ecommerce John Doe 6496 86.216.42.127 FR 513141 FR APPROVED 332622 johndoe@gmail.com 29398844 1 0 mccredit
TestCompany TestMerchant 4813726288036070 326078697 visa 2017-01-30 11:03:40 CEST EUR 59.95 Payment 0 Ecommerce John Doe 3019 79.157.98.235 ES 496626 ES APPROVED 766263 johndoe@gmail.com 32071417 1 0 visagold
TestCompany TestMerchant 4813726287975500 326078808 visa 2017-01-30 11:03:40 CEST EUR 55.97 Payment 0 Ecommerce John Doe 1672 91.153.93.98 FI 492019 FI APPROVED 545004 johndoe@gmail.com 23236809 1 0 visaclassic
TestCompany TestMerchant 4313726287093970 326078857 paypal 2017-01-30 11:03:40 CEST NOK 349.95 Payment 0 Ecommerce John Doe 89.10.243.82 NO APPROVED johndoe@gmail.com 20576170 0 0 paypal
TestCompany TestMerchant 4413726287357620 326078691 mc 2017-01-30 11:03:40 CEST EUR 44.95 Payment 40 Ecommerce John Doe 4447 190.45.96.129 CL 510207 CH APPROVED 493661 johndoe@gmail.com 10519214 1 0 mccredit
TestCompany TestMerchant 4713726287346190 326078852 amex 2017-01-30 11:03:40 CEST EUR 55.97 Payment 1 Ecommerce John Doe 4003 84.120.73.97 ES 375692 ES APPROVED 292875 johndoe@gmail.com 10929539 1 6 1596496437274 amex
TestCompany TestMerchant 4313726286661880 326078856 paypal 2017-01-30 11:03:40 CEST EUR 49.95 Payment 40 Ecommerce John Doe 77.193.132.54 FR APPROVED johndoe@gmail.com 38417608 0 0 paypal
TestCompany TestMerchant 4313726287124150 326078854 mc 2017-01-30 11:03:40 CEST NOK 309.95 Payment 0 Ecommerce John Doe 7849 80.212.215.90 NO 526792 NO APPROVED 926995 johndoe@gmail.com 19583019 1 0 mccredit
TestCompany TestMerchant 1713726263555940 326078507 paypal 2017-01-30 11:03:40 CEST EUR 44.95 Payment 0 Ecommerce John Doe 83.84.81.244 NL APPROVED johndoe@gmail.com 19061001 0 0 paypal
TestCompany TestMerchant 1413726223992920 326077527 paypal 2017-01-30 11:03:40 CEST EUR 52.47 Payment 0 Ecommerce John Doe 91.5.185.138 DE APPROVED johndoe@gmail.com 21577751 0 0 paypal
TestCompany TestMerchant 1713726222760480 326077557 ideal 2017-01-30 11:03:40 CEST EUR 74.95 Payment 0 Ecommerce John Doe 123456789 82.171.204.220 NL NOT PROVIDED NL APPROVED johndoe@gmail.com 46354602 0 0 idealrabobank
TestCompany TestMerchant 1713726224533770 326077530 mc 2017-01-30 11:03:40 CEST EUR 49.95 Payment 0 Ecommerce John Doe 2284 31.151.72.195 NL 524886 NL APPROVED 79254 johndoe@gmail.com 15711488 1 0 mccredit
TestCompany TestMerchant 4713726223474260 326077601 ideal 2017-01-30 11:03:40 CEST EUR 49.95 Payment 0 Ecommerce John Doe 123456789 94.212.57.25 NL NOT PROVIDED NL APPROVED johndoe@gmail.com 39137113 0 0 idealrabobank
TestCompany TestMerchant 4713726224411540 326077564 mc 2017-01-30 11:03:40 CEST SEK 496.97 Payment 0 Ecommerce John Doe 6167 81.233.155.7 SE 541256 SE APPROVED 787014 johndoe@gmail.com 46354346 1 0 mccredit
TestCompany TestMerchant 1413726223872170 326077490 paypal 2017-01-30 11:03:40 CEST EUR 49.95 Payment 0 Ecommerce John Doe 79.233.5.129 DE APPROVED johndoe@gmail.com 14979703 0 0 paypal
TestCompany TestMerchant 4313726224209420 326077487 directdebit_NL 2017-01-30 11:03:40 CEST EUR 55.97 Payment 0 Ecommerce John Doe 123456789 77.170.216.163 NL ING Bank NL UNKNOWN johndoe@gmail.com 46354842 0 0 directdebit_NL
TestCompany TestMerchant 1813726224142280 326077604 mc 2017-01-30 11:03:40 CEST NOK 300.96 Payment 0 Ecommerce John Doe 9571 81.167.104.59 NO 540022 NO APPROVED 858633 johndoe@gmail.com 12734725 1 0 mccredit
TestCompany TestMerchant 1713726223716600 326077488 paypal 2017-01-30 11:03:40 CEST CHF 64.95 Payment 0 Ecommerce John Doe 82.192.241.139 CH APPROVED johndoe@gmail.com 46353551 0 0 paypal
TestCompany TestMerchant 1713726223947930 326077446 elv 2017-01-30 11:03:40 CEST EUR 19.95 Payment 0 Ecommerce John Doe 123456789 87.164.131.37 DE Sparkasse Düren 39550110 Düren DE APPROVED johndoe@gmail.com 46297943 0 0 elv
TestCompany TestMerchant 4413726222814330 326077521 paypal 2017-01-30 11:03:40 CEST EUR 52.47 Payment 0 Ecommerce John Doe 91.65.26.202 DE APPROVED johndoe@gmail.com 30335869 0 0 paypal
TestCompany TestMerchant 4813726223690410 326077560 visa 2017-01-30 11:03:40 CEST EUR 59 Payment 0 Ecommerce John Doe 9333 62.158.81.100 DE 455578 DE APPROVED 446175 johndoe@gmail.com 45233240 1 0 visagold
TestCompany TestMerchant 1413726223640760 326077563 mc 2017-01-30 11:03:40 CEST CHF 47.48 Payment 0 Ecommerce John Doe 5807 85.4.157.187 CH 558265 CH APPROVED 77827 johndoe@gmail.com 5270646 1 0 mccredit
TestCompany TestMerchant 1813726223598550 326077482 visa 2017-01-30 11:03:40 CEST DKK 639 Payment 0 Ecommerce John Doe 4622 80.162.98.238 DK 457109 DK APPROVED 215927 johndoe@gmail.com 46189627 1 0 visadankort
TestCompany TestMerchant 4313726222980360 326077447 paypal 2017-01-30 11:03:40 CEST EUR 9.95 Payment 0 Ecommerce John Doe 91.54.42.161 DE APPROVED johndoe@gmail.com 46354867 0 0 paypal
TestCompany TestMerchant 1713726222377520 326077477 paypal 2017-01-30 11:03:40 CEST EUR 19.95 Payment 0 Ecommerce John Doe 80.226.24.5 DE APPROVED johndoe@gmail.com 46349478 0 0 paypal
TestCompany TestMerchant 1413726223228120 326077552 mc 2017-01-30 11:03:40 CEST NOK 943.95 Payment 0 Ecommerce John Doe 2982 81.167.102.18 NO 526792 NO APPROVED 628861 johndoe@gmail.com 39177831 1 0 mccredit
TestCompany TestMerchant 1413726223197910 326077558 mc 2017-01-30 11:03:40 CEST EUR 55.97 Payment 0 Ecommerce John Doe 7520 77.166.133.48 NL 520953 NL APPROVED 51301 johndoe@gmail.com 33387219 1 0 mccredit
TestCompany TestMerchant 4713726222115300 326077473 paypal 2017-01-30 11:03:40 CEST EUR 52.47 Payment 0 Ecommerce John Doe 217.80.106.25 DE APPROVED johndoe@gmail.com 41552467 0 0 paypal
TestCompany TestMerchant 1813726223105720 326077551 visa 2017-01-30 11:03:40 CEST EUR 38.47 Payment 0 Ecommerce John Doe 8661 84.122.4.197 ES 496663 ES APPROVED 256884 johndoe@gmail.com 18182116 1 0 visagold
TestCompany TestMerchant 1713726217400590 326077379 directEbanking 2017-01-30 11:03:40 CEST EUR 39.95 Payment 0 Ecommerce John Doe 123456789 84.193.85.113 BE ING België 377 BE APPROVED johndoe@gmail.com 30680805 0 0 23931-75200-51D08BAD-CBD6 directEbanking
TestCompany TestMerchant 1713726222982170 326077522 directdebit_NL 2017-01-30 11:03:40 CEST EUR 49.95 Payment 0 Ecommerce John Doe 123456789 80.60.78.74 NL ING NL UNKNOWN johndoe@gmail.com 32866081 0 0 directdebit_NL
TestCompany TestMerchant 4413726222925190 326077517 visa 2017-01-30 11:03:40 CEST EUR 39.98 Payment 40 Ecommerce John Doe 6216 82.232.46.101 FR 497886 FR APPROVED 855338 johndoe@gmail.com 13172003 1 0 visaclassic
TestCompany TestMerchant 4813726222763770 326077438 visa 2017-01-30 11:03:40 CEST SEK 624.95 Payment 0 Ecommerce John Doe 9360 90.228.207.137 SE 458109 SE APPROVED 151577 johndoe@gmail.com 11495170 1 0 visadebit
TestCompany TestMerchant 1413726217274300 326077293 directEbanking 2017-01-30 11:03:40 CEST EUR 59 Payment 0 Ecommerce John Doe 123456789 62.47.211.49 AT Raiffeisenbank Judenburg eGen 38368 AT APPROVED johndoe@gmail.com 44510306 0 0 23931-75200-51D08BA0-8AD6 directEbanking
TestCompany TestMerchant 1713726222649720 326077474 visa 2017-01-30 11:03:40 CEST DKK 419.97 Payment 0 Ecommerce John Doe 1699 178.155.240.3 DK 457171 DK APPROVED 215752 johndoe@gmail.com 46349426 1 0 visadankort
TestCompany TestMerchant 1813726222642590 326077441 visa 2017-01-30 11:03:40 CEST CHF 59.95 Payment 1 Ecommerce John Doe 9473 178.194.105.155 CH 495034 CH APPROVED 16011 johndoe@gmail.com 3636640 1 0 visadebit
TestCompany TestMerchant 4413726222432070 326077508 visa 2017-01-30 11:03:40 CEST SEK 496.97 Payment 0 Ecommerce John Doe 9644 90.232.17.7 SE 426388 SE APPROVED 991279 johndoe@gmail.com 39485126 1 0 visaclassic
TestCompany TestMerchant 1413726222382000 326077347 mc 2017-01-30 11:03:40 CEST EUR 59.95 Payment 1 Ecommerce John Doe 1005 81.244.134.132 BE 536521 BE DECLINED johndoe@gmail.com 32058703 1 0 mccredit
TestCompany TestMerchant 1813726222320040 326077512 visa 2017-01-30 11:03:40 CEST EUR 52.47 Payment 40 Ecommerce John Doe 4798 151.47.44.91 IT 456364 IT APPROVED 79032 johndoe@gmail.com 44000473 1 0 visaclassic
TestCompany TestMerchant 1813726222279640 326077399 mc 2017-01-30 11:03:40 CEST SEK 354.95 Payment 0 Ecommerce John Doe 5007 81.225.124.253 SE 541256 SE APPROVED 650540 johndoe@gmail.com 39511890 1 0 mccredit
TestCompany TestMerchant 1313726221487730 326077509 paypal 2017-01-30 11:03:40 CEST NOK 409.47 Payment 0 Ecommerce John Doe 85.164.97.58 NO APPROVED johndoe@gmail.com 14727629 0 0 paypal
TestCompany TestMerchant 1313726221165670 326077468 ideal 2017-01-30 11:03:40 CEST EUR 55.97 Payment 0 Ecommerce John Doe 123456789 217.122.129.222 NL NOT PROVIDED NL APPROVED johndoe@gmail.com 32493560 0 0 idealpostbank

Settlement detail report batch

File name SAMPLE_settlement_detail_report_batch_17_Feb_6
File format .csv


Company Account Merchant Account Psp Reference Merchant Reference Payment Method Creation Date TimeZone Type Modification Reference Gross Currency Gross Debit (GC) Gross Credit (GC) Exchange Rate Net Currency Net Debit (NC) Net Credit (NC) Commission (NC) Markup (NC) Scheme Fees (NC) Interchange (NC) Payment Method Variant Reserved2 Reserved3 Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved9 Reserved10
SupportAdyen SupportAdyenDemo 1313679128962710 325406007 elv 2013-05-08 09:49:43 CEST Settled 2413679129000870 EUR 49.95 1 EUR 49.7 0.25 elv
SupportAdyen SupportAdyenDemo 1713680142938010 325418414 elv 2013-05-09 13:58:58 CEST Settled 2413680143033050 EUR 53.9 1 EUR 53.65 0.25 elv
SupportAdyen SupportAdyenDemo 1313680249794410 325419918 elv 2013-05-09 16:57:11 CEST Settled 2313680249873690 EUR 44.95 1 EUR 44.7 0.25 elv
SupportAdyen SupportAdyenDemo 1313681154730390 325430762 bankTransfer_BE 2013-05-14 05:57:20 CEST Settled 1313681154730390 EUR 71.96 1 EUR 71.76 0.2 bankTransfer_BE
SupportAdyen SupportAdyenDemo 1313680593751040 325424322 bankTransfer_BE 2013-05-14 05:57:22 CEST Settled 1313680593751040 EUR 49.95 1 EUR 49.75 0.2 bankTransfer_BE
SupportAdyen SupportAdyenDemo 1813680074020520 325417185 bankTransfer_BE 2013-05-14 05:57:24 CEST Settled 1813680074020520 EUR 29.95 1 EUR 29.75 0.2 bankTransfer_BE
SupportAdyen SupportAdyenDemo 1813682625336830 325449838 bcmc 2013-05-11 10:56:32 CEST Settled 1813682625336830 EUR 41.28 1 EUR 40.45 0.83 bcmc
SupportAdyen SupportAdyenDemo 1713682661456550 325450897 bcmc 2013-05-11 11:56:45 CEST Settled 1713682661456550 EUR 29.95 1 EUR 29.35 0.6 bcmc
SupportAdyen SupportAdyenDemo 1713682599366270 325449150 bcmc 2013-05-11 10:13:49 CEST Settled 1713682599366270 EUR 29.95 1 EUR 29.35 0.6 bcmc
SupportAdyen SupportAdyenDemo 4313682131280080 325443719 directEbanking 2013-05-10 21:20:04 CEST Settled 4313682131280080 EUR 99.95 1 EUR 97.95 2 directEbanking
SupportAdyen SupportAdyenDemo 1713683975714840 325474912 directEbanking 2013-05-13 00:45:43 CEST Settled 1713683975714840 EUR 59 1 EUR 57.82 1.18 directEbanking
SupportAdyen SupportAdyenDemo 4813684064879120 325475227 directEbanking 2013-05-13 02:59:46 CEST Settled 4813684064879120 EUR 27.48 1 EUR 26.93 0.55 directEbanking
SupportAdyen SupportAdyenDemo 4313678337116540 325396579 elv 2013-05-07 11:49:31 CEST Chargeback 5313678337173230 EUR 95.2 1 EUR 102.7 7.5 elv
SupportAdyen SupportAdyenDemo 1813679158786420 325406459 elv 2013-05-08 10:38:52 CEST Chargeback 2413679158896170 EUR 71.96 1 EUR 79.46 7.5 elv
SupportAdyen SupportAdyenDemo 4413678334594430 325396485 elv 2013-05-07 11:45:11 CEST Chargeback 5313678334649870 EUR 44.95 1 EUR 52.45 7.5 elv
SupportAdyen SupportAdyenDemo 1313678415882680 325397860 elv 2013-05-07 14:00:41 CEST Chargeback 2413678415920930 EUR 49.95 1 EUR 57.45 7.5 elv
SupportAdyen SupportAdyenDemo 4813682653676260 325450762 bankTransfer_DE 2013-05-14 07:00:19 CEST Settled 4813682653676260 EUR 157.11 1 EUR 156.91 0.2 bankTransfer_DE
SupportAdyen SupportAdyenDemo 4713681407074910 325433971 bankTransfer_DE 2013-05-14 07:00:19 CEST Settled 4713681407074910 EUR 159 1 EUR 158.8 0.2 bankTransfer_DE
SupportAdyen SupportAdyenDemo 4713682118996100 325443337 giropay 2013-05-10 20:52:59 CEST Settled 4713682118996100 EUR 5.95 1 EUR 5.3 0.65 giropay
SupportAdyen SupportAdyenDemo 4713682983186990 325459007 giropay 2013-05-11 20:53:28 CEST Settled 4713682983186990 EUR 5.95 1 EUR 5.3 0.65 giropay
SupportAdyen SupportAdyenDemo 1813681755092490 325436094 giropay 2013-05-10 10:50:10 CEST Settled 1813681755092490 EUR 29.95 1 EUR 29 0.95 giropay
SupportAdyen SupportAdyenDemo 4713681935163810 325438865 giropay 2013-05-10 15:47:05 CEST Settled 4713681935163810 EUR 71.96 1 EUR 69.96 2 giropay
SupportAdyen SupportAdyenDemo 4713682765735800 325453767 ideal 2013-05-11 14:51:31 CEST Settled 4713682765735800 EUR 8.9 1 EUR 8.65 0.25 idealpostbank
SupportAdyen SupportAdyenDemo 1713681952402880 325439133 ideal 2013-05-10 16:18:01 CEST Settled 1713681952402880 EUR 18.9 1 EUR 18.65 0.25 idealpostbank
SupportAdyen SupportAdyenDemo 1313682996420950 325459139 ideal 2013-05-11 21:15:46 CEST Settled 1313682996420950 EUR 18.9 1 EUR 18.65 0.25 idealpostbank
SupportAdyen SupportAdyenDemo 4313682770569420 325453904 ideal 2013-05-11 15:01:14 CEST Settled 4313682770569420 EUR 27.48 1 EUR 27.23 0.25 idealpostbank
SupportAdyen SupportAdyenDemo 4813682602650660 325449216 directdebit_NL 2013-05-13 20:09:02 CEST Settled 4813682602650660 EUR 63.96 1 EUR 63.76 0.2 directdebit_NL
SupportAdyen SupportAdyenDemo 1313682864414000 325456252 bankTransfer_NL 2013-05-14 07:42:33 CEST Settled 1313682864414000 EUR 71.96 1 EUR 71.76 0.2 bankTransfer_NL
SupportAdyen SupportAdyenDemo 1313679144573160 325406252 bankTransfer_AT 2013-05-14 07:46:30 CEST Settled 1313679144573160 EUR 69.95 1 EUR 69.75 0.2 bankTransfer_AT
SupportAdyen SupportAdyenDemo 1813677945048460 325393381 bankTransfer_PT 2013-05-14 07:46:30 CEST Settled 1813677945048460 EUR 59.95 1 EUR 59.75 0.2 bankTransfer_PT
SupportAdyen SupportAdyenDemo 4813680846308240 325425565 bankTransfer_FI 2013-05-14 07:46:32 CEST Settled 4813680846308240 EUR 71.96 1 EUR 71.76 0.2 bankTransfer_FI
SupportAdyen SupportAdyenDemo 1713676855216130 325379231 bankTransfer_FR 2013-05-14 07:46:32 CEST Settled 1713676855216130 EUR 71.96 1 EUR 71.76 0.2 bankTransfer_FR
SupportAdyen SupportAdyenDemo 4413676186668170 325370010 bankTransfer_IT 2013-05-14 07:46:34 CEST Settled 4413676186668170 EUR 71.96 1 EUR 71.76 0.2 bankTransfer_IT
SupportAdyen SupportAdyenDemo 4813678767620760 325403797 bankTransfer_PT 2013-05-14 07:46:58 CEST Settled 4813678767620760 EUR 49.95 1 EUR 49.75 0.2 bankTransfer_PT
SupportAdyen SupportAdyenDemo 4713681143230900 325430395 bankTransfer_ES 2013-05-14 07:54:38 CEST Settled 4713681143230900 EUR 129.95 1 EUR 129.75 0.2 bankTransfer_ES
SupportAdyen SupportAdyenDemo 4313680761959520 325425002 mc 2013-05-10 07:10:46 CEST Settled 5313680762111570 EUR 49.95 1 EUR 49.5 0.3 0.03 0.12 mccredit
SupportAdyen SupportAdyenDemo 4713680812353130 325425266 mc 2013-05-10 08:34:43 CEST Settled 5313680812451020 EUR 29.95 1 EUR 29.67 0.18 0.02 0.08 mccredit
SupportAdyen SupportAdyenDemo 4313676945137540 325380783 mc 2013-05-10 10:06:58 CEST Refunded 1313681731511750 EUR 29.95 1 EUR 29.95 mccredit
SupportAdyen SupportAdyenDemo 1813679240430440 325407691 mc 2013-05-10 10:17:27 CEST Refunded 1413681738144560 EUR 59.95 1 EUR 59.95 mccredit
SupportAdyen SupportAdyenDemo 4413678448322470 325398453 visa 2013-05-07 14:54:23 CEST Settled 5413678448394890 CHF 59.97 0.794276067 EUR 46.52 0.29 0.1 0.72 visacorporate
SupportAdyen SupportAdyenDemo 1813678450183890 325398372 visa 2013-05-07 14:57:37 CEST Settled 2313678450225040 CHF 74.95 0.794276067 EUR 58.69 0.36 0.12 0.36 visaclassic
SupportAdyen SupportAdyenDemo 1713678451367130 325398414 visa 2013-05-07 14:59:38 CEST Settled 2313678451486770 CHF 64.95 0.794276067 EUR 50.4 0.31 0.1 0.78 visacorporate
SupportAdyen SupportAdyenDemo 1713677524130730 325386546 diners 2013-05-06 13:14:29 CEST Settled 2413677524217660 DKK 299.98 0.132512507 EUR 38.16 1.59 diners
SupportAdyen SupportAdyenDemo 1813678275257520 325395422 maestro 2013-05-07 10:10:05 CEST Settled 2313678277664330 SEK 833.92 0.11517165 EUR 95.74 0.3 maestro
SupportAdyen SupportAdyenDemo 1313681300987130 325433157 bijcard 2013-05-10 22:09:05 CEST Settled 2413681301065440 EUR 71.96 1 EUR 70.27 0.43 0.04 1.22 bijcard
SupportAdyen SupportAdyenDemo 1313683558334390 325465280 bankTransfer_PL 2013-05-14 08:48:16 CEST Settled 1313683558334390 PLN 82 0.238324971 EUR 19.34 0.2 bankTransfer_PL
SupportAdyen SupportAdyenDemo 1313678799343010 325404118 dotpay 2013-05-07 00:40:39 CEST Settled 1313678799343010 PLN 199.95 0.238324971 EUR 46.32 1.33 dotpay
SupportAdyen SupportAdyenDemo 1313642467023510 324959451 visa 2013-03-26 22:37:26 CEST Chargeback 2313642467170920 EUR 349.99 1 EUR 357.49 7.5 visaclassic
SupportAdyen SupportAdyenDemo 1813684322383860 325477283 ideal 2013-05-13 10:06:16 CEST Settled 1813684322383860 EUR 74.95 1 EUR 74.7 0.25 idealrabobank
SupportAdyen SupportAdyenDemo 2013-05-08 09:49:43 CEST MiscCosts EUR EUR 3239.81
SupportAdyen SupportAdyenDemo 2013-05-14 09:08:37 CEST MiscCosts EUR EUR 35.45
SupportAdyen SupportAdyenDemo 4813655361285480 325102564 paypal 2013-04-09 21:38:53 CEST ChargebackReversed 4813655361285480 EUR 59.95 1 EUR 59.17 paypal
SupportAdyen SupportAdyenDemo 4813679642368590 325414022 paypal 2013-05-08 00:04:35 CEST Settled 4813679642368590 EUR 49.95 1 EUR 49.28 0.67 paypal
SupportAdyen SupportAdyenDemo 1313663178890770 325178460 paypal 2013-04-18 22:45:20 CEST Chargeback 1313663178890770 EUR 49.95 1 EUR 49.28 paypal
SupportAdyen SupportAdyenDemo 1313665281084290 325207572 paypal 2013-05-08 10:50:32 CEST Refunded 1813680029916900 EUR 49.46 1 EUR 48.94 -0.52 paypal
SupportAdyen SupportAdyenDemo 4813682021404430 325440482 bankTransfer_SE 2013-05-14 10:08:37 CEST Settled 4813682021404430 SEK 244.98 0.11517165 EUR 28.01 0.2 bankTransfer_SE
SupportAdyen SupportAdyenDemo 4413684202919750 325475920 bankTransfer_NO 2013-05-14 10:15:29 CEST Settled 4413684202919750 NOK 309.98 0.13120153 EUR 40.47 0.2 bankTransfer_NO
SupportAdyen SupportAdyenDemo 2013-05-14 07:00:19 CEST AuthorisationSchemeFee Acquiring - Assessment Fees - all EUR EUR 225.58
SupportAdyen SupportAdyenDemo 1713679242204780 325407807 bankTransfer_DK 2013-05-14 10:16:04 CEST Settled 1713679242204780 DKK 372 0.132512507 EUR 49.09 0.2 bankTransfer_DK
SupportAdyen SupportAdyenDemo 2013-05-08 09:49:43 CEST Balancetransfer Balancetransfer EUR EUR 845.16
SupportAdyen SupportAdyenDemo 2013-05-14 10:53:01 CEST ManualCorrected IH1902003123452 BETAALD EUR 3.252,23 NL532ORS9900610000000 MERCHANT PAYMENTS INVOICE 400000041 B ILLING PERIOD FEB-15 SUPPORTADYEN 1 9.02.15 UW REF. 02000326852662 EUR EUR 3252.23
SupportAdyen SupportAdyenDemo 1714224620023620 1213_s4156871_1501281719 klarna 2013-05-07 14:54:23 CEST PaymentCost 4314225614125980 EUR 517.8 1 EUR 2.42 klarna_SE
SupportAdyen SupportAdyenDemo 4314249785405840 13499478 sepadirectdebit 2013-05-07 14:57:37 CEST RefundedReversed 1414254284829130 EUR 99 1 EUR 99 sepadirectdebit_authcap
SupportAdyen SupportAdyenDemo 2013-05-14 05:57:20 CEST ManualCorrected Manual Corrected EUR EUR 1649.22
SupportAdyen SupportAdyenDemo 2015-03-02 01:27:19 CEST Balancetransfer Balancetransfer EUR EUR 257.93
SupportAdyen SupportAdyenDemo 2013-05-08 00:04:35 CEST EpaPaid EUR EUR 176.46
SupportAdyen SupportAdyenDemo 2013-05-10 15:47:05 CEST MatchedStatement AIB MERCHANT SERVICES (RST121222120210 BETALINGSKENM. PA0236552144 Betalingskenm. PA0546543484521 Wereldbetaling SHA EUR EUR 500
SupportAdyen SupportAdyenDemo 2013-05-11 21:15:46 CEST BankInstructionReturned TX123156XT batch 205 SupportAdyenDemo batch 205 SupportAdyenDemo EUR EUR 0.97
SupportAdyen SupportAdyenDemo 2013-05-14 10:53:01 CEST InternalCompanyPayout MerchantToMerchantPayout EUR EUR 253.2
SupportAdyen SupportAdyenDemo 2013-05-10 21:20:04 CEST DepositCorrection Deposit Correction EUR EUR 12992
SupportAdyen SupportAdyenDemo 2013-05-08 00:04:35 CEST InvoiceDeduction Invoice 201411001713 EUR EUR 1018.89
SupportAdyen SupportAdyenDemo 4813683691750550 325468508 ideal 2013-05-14 10:53:01 CEST Refunded 1413685215353460 EUR 69.95 1 EUR 70.15 0.2 idealpostbank
SupportAdyen SupportAdyenDemo 2013-05-15 05:47:53 CEST Fee Transaction Fees May 2013 EUR EUR 398.37
SupportAdyen SupportAdyenDemo 2013-05-15 05:47:55 CEST MerchantPayout TX938848529XT batch 206 EUR EUR 15205.87

External settlement detail report batch

File name SAMPLE_external_settlement_report_with_info_2016_06_23
File format .csv

Company Account Merchant Account Psp Reference Merchant Reference Payment Method Creation Date TimeZone Type Modification Reference Gross Currency Gross Debit (GC) Gross Credit (GC) Exchange Rate Net Currency Net Debit (NC) Net Credit (NC) Commission (NC) Markup (NC) Scheme Fees (NC) Interchange (NC) Payment Method Variant Acquirer MID ARN Acquirer Reference Reserved6 Reserved7 Reserved8 Reserved9 Reserved10
ExampleCompany CoMobile 1234567891011121 COABN3W-277688 amex_applepay 2016-06-19 23:24:22 BST SentForSettle 2300000000000000 GBP 43 1 GBP 0 amex_applepay Amex 9000000007 12ABCD345EF
ExampleCompany CoMobile 1234567891011122 COBF2QS-277712 amex_applepay 2016-06-19 23:24:49 BST SentForSettle 2300000000000001 GBP 21.98 1 GBP 0 amex_applepay Amex 9600000000 12ABCD345EF
ExampleCompany CoMobile 1234567891011123 COA1RQP-278525 amex_applepay 2016-06-19 23:44:43 BST SentForSettle 2300000000000002 EUR 152.99 1 EUR 0 amex_applepay Amex 9500000000 12ABCD345EF
ExampleCompany CoMobile 1234567891011124 COA1RW5-278675 amex_applepay 2016-06-19 23:48:44 BST SentForSettle 2300000000000003 EUR 118.65 1 EUR 0 amex_applepay Amex 9500000000 12ABCD345EF
ExampleCompany CoMobile 1234567891011125 COA1S2B-278821 amex_applepay 2016-06-19 23:53:10 BST SentForSettle 2300000000000004 EUR 119.66 1 EUR 0 amex_applepay Amex 9500000000 12ABCD345EF
ExampleCompany CoWeb 1234567891011126 COA1S8R-279026 mc 2016-06-19 23:59:51 BST SentForSettle 2300000000000005 GBP 149.96 1 GBP 0 mcdebit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011127 COA1S8W-279028 visa 2016-06-20 00:00:05 BST SentForSettle 2300000000000010 GBP 204.93 1 GBP 0 visadebit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011128 CORANM1-278987 mc 2016-06-19 23:58:51 BST SentForRefund 2300000000000011 EUR 119.18 1 EUR 0 mccredit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011129 COA1CKZ-267009 visa 2016-06-19 21:09:09 BST SentForRefund 2300000000000012 GBP 114.2 1 GBP 0 visadebit Lloyds 500000000000000
ExampleCompany CoWeb 1234567891011130 COB1DFG-238646 visa 2016-06-19 16:41:01 BST SentForRefund 2300000000000013 EUR 48.6 1 EUR 0 visadebit EuroConex ExampleCompany 12ABCD345EF
ExampleCompany CoWeb 1234567891011131 COA15PL-261215 visa 2016-06-19 20:13:59 BST SentForRefund 2300000000000014 CHF 76.92 1 CHF 0 visadebit EuroConex ExampleCompany 12ABCD345EF
ExampleCompany CoB2B 1234567891011132 COBZP9C-232714 visa 2016-06-09 22:36:10 BST SentForRefund 2300000000000015 GBP 59.99 1 GBP 0 visadebit Lloyds 500000000000000
ExampleCompany CoB2B 1234567891011133 COA1GMD-269880 amex 2016-06-19 21:37:08 BST SentForRefund 2300000000000020 GBP 108.2 1 GBP 0 amex Amex 9500000000 12ABCD345EF
ExampleCompany CoB2B 1234567891011134 COA1JLT-271739 mc 2016-06-19 21:56:11 BST SentForRefund 2300000000000021 EUR 62.6 1 EUR 0 mccredit Lloyds 500000000000000
ExampleCompany CoB2B 1234567891011135 COA1GMD-269880 amex 2016-06-19 21:37:08 BST SentForRefund 2300000000000022 GBP 108.2 1 GBP 0 amex Amex 9500000000 12ABCD345EF
ExampleCompany CoB2B 1234567891011136 COA1JLT-271739 mc 2016-06-19 21:56:11 BST SentForRefund 2300000000000023 EUR 62.6 1 EUR 0 mccredit Lloyds 500000000000000

Dispute report

File name SAMPLE_dispute_report_2017_02_06
File format .csv

Company Account Merchant Account Psp Reference Merchant Reference Payment Method Record Date Record Date TimeZone Dispute Currency Dispute Amount Record Type Dispute Reason RFI Scheme Code RFI Reason Code CB Scheme Code CB Reason Code Payment Date Payment Date TimeZone Payment Currency Payment Amount Dispute Date Dispute Date TimeZone Dispute ARN User Name Risk Scoring Shopper Interaction Shopper Name Shopper Email Shopper Reference Shopper PAN Shopper IP Shopper Country Issuer Country Issuer Id 3D Directory Response 3D Authentication Response CVC2 Response AVS Response
SupportAdyen SupportAdyenDemo 1713696334968670 CREDITS_42267583 visa 2013-09-05 21:25:52 CEST LKR 1125 NotificationOfChargeback Card Absent Fraud visa 83 2013-05-27 07:49:54 CEST LKR 1125 2013-09-05 21:25:52 CEST 74987503147210000000000 system 0 ContAuth Joh Doe dummymail@gmail.com 12345 6775 175.157.155.110 LK LK 414395 3 0
SupportAdyen SupportAdyenDemo 4713721285264900 CREDITS_46341280 visa 2013-09-05 21:25:51 CEST NOK 104.3 NotificationOfChargeback Card Present Fraud visa 81 2013-06-27 10:08:46 CEST NOK 104.3 2013-09-05 21:25:51 CEST 74987503178293400000000 system 0 ContAuth Joh Doe dummymail@gmail.com 12346 1210 87.248.11.151 NO NO 417312 3 0
SupportAdyen SupportAdyenDemo 141653408691495 CREDITS_51057867 visa 2013-09-05 20:31:53 CEST USD 16.39 NotificationOfChargeback Cardholder does not Recognise visa 75 2013-08-01 09:07:49 CEST ILS 58.5 2013-09-05 20:31:53 CEST 74987503213256800000000 system 41 ContAuth Joh Doe dummymail@gmail.com 12347 2050 93.172.81.152 IL IL 458003 3 0
SupportAdyen SupportAdyenDemo 4813752944213210 CREDITS_50896724 visa 2013-09-05 20:31:53 CEST USD 16.39 NotificationOfChargeback Cardholder does not Recognise visa 75 2013-07-31 07:43:41 CEST ILS 58.5 2013-09-05 20:31:53 CEST 74987503212206400000000 system 41 ContAuth Joh Doe dummymail@gmail.com 12348 2050 93.172.81.152 IL IL 458003 3 0
SupportAdyen SupportAdyenDemo 1313794636479980 CREDITS_50903229 visa 2013-09-05 13:55:16 CEST EUR 12.42 NotificationOfChargeback Cardholder does not Recognise visa 75 2013-07-31 08:54:07 CEST ILS 58.5 2013-09-05 13:55:15 CEST 74657363217000200000000 system 41 ContAuth Joh Doe dummymail@gmail.com 12349 2050 93.172.81.152 IL IL 458003 0 0
SupportAdyen SupportAdyenDemo 4713754447138130 CREDITS_51251221 visa 2013-09-05 13:55:13 CEST EUR 12.48 NotificationOfChargeback Cardholder does not Recognise visa 75 2013-08-02 13:58:49 CEST ILS 58.5 2013-09-05 13:55:12 CEST 74657363218000400000000 system 41 ContAuth Joh Doe dummymail@gmail.com 12350 2050 89.139.152.72 IL IL 458003 0 0
SupportAdyen SupportAdyenDemo 4413754108621560 CREDITS_51250735 visa 2013-09-05 13:55:12 CEST EUR 12.48 NotificationOfChargeback Cardholder does not Recognise visa 75 2013-08-02 13:54:22 CEST ILS 58.5 2013-09-05 13:55:12 CEST 74657363218000400000000 system 41 ContAuth Joh Doe dummymail@gmail.com 12351 2050 89.139.152.72 IL IL 458003 0 0
SupportAdyen SupportAdyenDemo 1713752494197450 UNLIMITED_347635076 visa 2013-09-05 13:55:05 CEST EUR 42.46 NotificationOfChargeback Cardholder does not Recognise visa 75 2013-07-31 07:43:28 CEST ILS 199.99 2013-09-05 13:55:04 CEST 74657363217000200000000 system 41 ContAuth Joh Doe dummymail@gmail.com 12352 2050 93.172.81.152 IL IL 458003 0 0
SupportAdyen SupportAdyenDemo 4713769760138240 CREDITS_54109971 visa 2013-09-05 08:29:42 CEST EUR 10.11 Chargeback Cardholder Cancelled Recurring Transaction visa 41 2013-08-20 07:21:07 CEST USD 13.49 2013-09-02 12:23:45 CEST 74657363236000400000000 system 90 ContAuth Joh Doe dummymail@gmail.com 12353 1441 69.141.201.93 US US 473702 0 0
SupportAdyen SupportAdyenDemo 1713769760700900 CREDITS_54109980 visa 2013-09-05 08:29:43 CEST EUR 10.11 Chargeback Cardholder Cancelled Recurring Transaction visa 41 2013-08-20 07:21:10 CEST USD 13.49 2013-09-02 12:23:44 CEST 74657363236000400000000 system 90 ContAuth Joh Doe dummymail@gmail.com 12354 1441 69.141.201.93 US US 473702 0 0
SupportAdyen SupportAdyenDemo 4313999472859280 UNLIMITED_351182211 visa 2013-09-05 06:37:49 CEST USD 14.46 Chargeback Services Not Rendered visa 30 2013-08-03 18:28:05 CEST ILS 49.99 2013-09-01 15:09:36 CEST 74987503215593000000000 system 0 Ecommerce Joh Doe dummymail@gmail.com 12355 3740 85.64.252.71 IL IL 458028 1 0
SupportAdyen SupportAdyenDemo 1713758135113830 CREDITS_51887703 visa 2013-09-05 06:35:39 CEST IDR 89000 Chargeback Card Absent Fraud visa 83 2013-08-06 20:26:31 CEST IDR 89000 2013-08-31 15:18:55 CEST 74987503218664000000000 system 10 Ecommerce Joh Doe dummymail@gmail.com 12356 6064 182.11.138.27 ID ID 415735 1 0
SupportAdyen SupportAdyenDemo 4313650018595570 CREDITS_35681848 mc 2013-08-22 20:06:21 CEST INR 325 RequestForInformation Legal process request mc 34 2013-04-03 17:21:09 CEST INR 325 2013-08-22 20:06:21 CEST 74657363098000300000000 system 0 ContAuth Joh Doe dummymail@gmail.com 12357 7012 27.0.51.118 IN IN 447747 0 0