> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Adyen as a data source
> Bring data from Adyen to Nekt.
Adyen is a global payments platform that processes card, wallet and local payment methods, settles the funds and pays them out to your bank account. This connector brings your Adyen transaction, settlement and dispute data into your Nekt Catalog.
## Before you start
Adyen works differently from most connectors, and it is worth understanding before you begin.
Adyen has **no API that lists your transactions**. Everything transactional leaves the platform as a **report file** that Adyen generates in your Customer Area and serves over HTTPS. This connector downloads those files — which means it can only read a report that **already exists**. Adyen never generates one on request, and it offers no way to list which ones are available.
So there are two things you have to do in your Adyen Customer Area before the connector produces anything:
1. **Turn on automatic generation for each report you want**, in CSV.
2. **Create a Report user API credential** for Nekt to download them with.
If a report is not set to generate automatically, Adyen answers "not found" for it — exactly as it does for a day with no data. The connector reports in the run log which report and which account found nothing, but it cannot tell the two situations apart.
### 1. Turn on the reports
In your [Customer Area](https://ca-live.adyen.com/), for each report below: go to **Reports**, open the report, select **Manage report** > **Automatic (generate on a schedule)**, and choose the **CSV** file format.
| Report | Stream it feeds | What it answers | Suggested frequency |
| --------------------------- | ----------------------------- | -------------------------------------------------------------------------------------- | ------------------- |
| Received payment details | `received_payment_details` | Which payments came in, which were approved or refused, and what the acquirer answered | Daily |
| Payment accounting | `payment_accounting` | Every accounting event of every payment, with the fees charged at each stage | Daily |
| Settlement details | `settlement_details` | What was actually settled and paid out, and what each transaction cost | At batch close |
| Dispute transaction details | `dispute_transaction_details` | Chargebacks, notifications of fraud and requests for information | Daily |
| External settlement detail | `external_settlement_details` | Transactions settled by an external acquirer (only if you use one) | Daily |
You need the **Merchant Report** or **Generate key financial reports** [user role](https://docs.adyen.com/account/user-roles) to configure them.
Note the **account level** you generate each report at. Most reports can be generated for the company account, for individual merchant accounts, or both — and the connector has to look in the same place. By default it looks where Adyen publishes each report: per merchant account for the payment-oriented ones, and for the company account for the dispute report. The Settlement details report only exists per merchant account.
Adyen keeps generated reports for **two years**. Data older than that cannot be recovered through this connector; it has to be regenerated in the Customer Area first.
### 2. Create a Report user credential
In your Customer Area, go to **Developers** > **API credentials** > **Create new credential**:
1. Under **User type**, select **Report user**.
2. Under **Roles and Associated Accounts**, make sure the **Merchant Report Download** role is on, and give the credential access to the accounts you want to read.
3. Under **Authentication**, either create a password for **Basic Auth** (and note the user name shown next to it) or select **Generate New API Key**. Nekt accepts either one.
4. Select **Save**.
Copy the password or the API key immediately — Adyen shows each of them only once.
## Configuring Adyen as a Source
In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Adyen option from the list of connectors.
Click **Next** and you'll be prompted to add your access.
### 1. Add account access
The following configurations are available:
* **Company Account**: the name of your Adyen company account, exactly as it appears at the top of your Customer Area.
* **Merchant Accounts**: the names of the merchant accounts to read reports for, separated by commas. Required unless every report of yours is generated at company level.
* **Report User** and **Report User Password**: the Basic auth credentials of the Report user API credential you created above.
* **API Key**: the API key of that same credential, as an alternative to the user name and password. Fill in one or the other.
* **Environment**: `live` (default) or `test`. Live and test are separate Customer Areas with separate credentials, so the credentials must belong to the environment you select here.
The advanced settings let you match the connector to how your reports are generated:
* **Report account level**: (Default: `merchant`) where your reports are generated. The default reads each report at the level Adyen publishes it by default — the payment-oriented reports per merchant account, and the Dispute transaction details report for the company account. Choose `company` if you generate all of them for the company account, or `both` if you generate both; note that `both` extracts the same payment twice when a report exists at both levels.
* **Initial sync date**: (Default: 90 days ago) the earliest report date to read. The connector looks for one file per day from this date onwards, so a very early date makes the first sync long.
* **Lookback (days)**: (Default: 3) how many days before the last synced date every run reads again. Adyen generates the daily reports between 02:00 and 10:00 CET of the following day, so the lookback makes sure a report that was not ready during the previous run is still picked up.
* **Report time zone**: the IANA name of the time zone your reports are written in, for example `America/Sao_Paulo`. Adyen writes report timestamps in your account's reporting time zone with no offset, and names that zone in a separate column as an abbreviation that is ambiguous for several of its values. Set this and every timestamp is converted to UTC; leave it empty and timestamps are stored exactly as Adyen wrote them.
* **Report file format**: (Default: `csv`) the format your reports are generated in.
* **Initial settlement batch**: (Default: 1) the settlement batch number the first sync starts looking from. Adyen names the Settlement details report after the payout batch instead of a date, so set this to the oldest batch number still listed under **Reports** > **Settlement details** > **Generated reports**.
* **Settlement miss tolerance** and **Settlement probe limit**: how many consecutive missing batch reports end the walk, once a batch has been read (default 5) and before any batch has been read (default 500).
* **Requests per minute**: (Default: 240) an upper bound on how fast the connector downloads report files.
Once you're done, click **Next**.
### 2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams whose reports you actually generate in Adyen.
> Tip: The stream can be found more easily by typing its name.
Select the streams and click **Next**.
### 3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: you can choose between INCREMENTAL and FULL\_TABLE.
* Incremental: every time the extraction happens, we'll get only the new data - which is good if, for example, you want to keep every record ever fetched.
* Full table: every time the extraction happens, we'll get the current state of the data - which is good if, for example, you don't want to have deleted data in your catalog.
Report rows have no unique identifier: the same `psp_reference` appears once per accounting event, and fee and payout entries carry no reference at all. The connector therefore declares no primary key, and the incremental sync is by report file — each run reads the files it has not read yet, plus the lookback window.
Once you are done configuring, click **Next**.
### 4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters.
To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers), consider how often you want data to be extracted from this source. A daily trigger scheduled after 10:00 CET matches Adyen's own report generation window.
Optionally, you can define some additional settings:
* Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource [here](https://docs.nekt.com/get-started/core-concepts/resource-control).
* Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#additional-full-sync)**.
Once you are ready, click **Next** to finalize the setup.
### 5. Check your new source
You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.
## Good to know
* **Your report columns are yours to choose.** Under **Settings** > **Report columns** in your Customer Area you decide which columns each report carries and in which order. The connector knows every column Adyen documents and reads rows by column name, so adding a column or reordering them is safe. A column that Adyen does not document cannot be extracted, and the run log names it when that happens.
* **Two reports are not covered.** The **Advancements detail report** and the **Aggregate settlement details report** are named after values that cannot be predicted (the advancement code, or the schedule you configured), and Adyen offers no way to list the generated files, so the connector cannot find them.
* **Timestamps are in your reporting time zone**, not UTC, unless you fill in the **Report time zone** setting. Each timestamp column has a paired column naming the zone it was written in.
# Streams and Fields
## Available streams
| Stream | Slug | Adyen report | Description |
| --------------------------- | ----------------------------- | --------------------------- | ------------------------------------------------------------------------------ |
| Settlement Details | `settlement_details` | Settlement details | Settled transactions, fees and payouts, per payout batch. |
| Payment Accounting | `payment_accounting` | Payment accounting | Every accounting event of every payment, with its fees. |
| Received Payment Details | `received_payment_details` | Received payment details | Every payment attempt, with the acquirer response that approved or refused it. |
| Dispute Transaction Details | `dispute_transaction_details` | Dispute transaction details | Chargebacks, notifications of fraud and requests for information. |
| External Settlement Details | `external_settlement_details` | External settlement detail | Transactions settled by an external acquirer. |
## Fields by stream
Below you'll find all available data streams from Adyen and their corresponding fields. A column only reaches your Catalog if it is switched on for that report in your Customer Area.
Settled transactions, transaction fees, deposit corrections, invoice deductions and payouts, as they appear in the Settlement details report of one payout batch. Adyen names this report after the batch number, so the connector reads one file per batch.
**Report columns:**
* `company_account` - The name of your company account as registered in the Adyen payments platform
* `merchant_account` - The name of the merchant account that was used to process the original payment request
* `psp_reference` - Adyen's 16-character unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with
* `merchant_reference` - The reference that was specified in the payment request
* `payment_method` - The payment method used for the transaction. For example: visa, mc, amex
* `creation_date` - The timestamp indicating when the payment was created on the Adyen payments platform. Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `timezone` - The time zone of the Creation Date. This is the ISO code for your time zone setting
* `creation_date_ams` - The Creation Date in Amsterdam time (CET or CEST). Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `type` - The Journal type of the entry
* `modification_reference` - Adyen's unique 16-character reference for the modification (capture, refund or chargeback) that produced the entry. For MerchantPayout entries it
* `gross_currency` - The three-character ISO currency code for the transaction currency
* `gross_debit_gc` - The amount submitted in the transaction request. For example, 100.00
* `gross_credit_gc` - The amount submitted in the transaction request. For example, 100.00
* `exchange_rate` - 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.For
* `net_currency` - The three-character ISO currency code for the settlement currency
* `net_debit_nc` - The net amount debited from the payable batch
* `net_credit_nc` - The net amount credited from the payable batch
* `commission_nc` - The commission fee withheld by the acquirer, in the settlement (net) currency. When the acquirer reports at interchange level this column is empty
* `markup_nc` - The fee charged by the acquiring bank. If the acquirer does not provide the transaction information at the interchange level, this field is empty
* `scheme_fees_nc` - The fee charged by, for example, Visa or Mastercard. If the acquirer does not provide the transaction information at the interchange level, this
* `interchange_nc` - The fee charged by the issuing bank. If the acquirer doesn't provide the transaction information at the interchange level, this field is empty
* `dcc_markup_nc` - The DCC markup (in Net Currency)
* `advanced_nc` - The installment amount that was advanced. This is the gross amount of the advancement fee (in Net Currency)
* `advancement_code` - The code of the advancement batch
* `advancement_batch` - The code of the advancement. An advancement code can occur in multiple batches
* `booking_type` - Identifies the transaction/installment that was accelerated or represented. Possible values: FIRST: Installment first/original presentment
* `payment_method_variant` - The sub-brand of the payment method (if applicable). For example: visaclassic, visadebit, mccorporate
* `batch_number` - The sequence number of the settlement
* `reserved1` - Reserved for future enhancements
* `reserved2` - Reserved for future enhancements
* `reserved3` - Reserved for future enhancements
* `reserved4` - Reserved for future enhancements
* `reserved5` - Reserved for future enhancements
* `reserved6` - Reserved for future enhancements
* `reserved7` - Reserved for future enhancements
* `reserved8` - Reserved for future enhancements
* `reserved9` - Reserved for future enhancements
* `reserved10` - Reserved for future enhancements
* `acquirer` - The name of the acquirer that processed the original payment. For example: Cielo, Redecard
* `modification_merchant_reference` - The optional modification reference for modifications, if specified in the transaction
* `split_settlement` - Contains detailed information about split settlements in the form of key value pairs
* `booking_date` - The timestamp indicating when the event was entered into Adyen's accounting system. The format is `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26
* `booking_date_timezone` - The time zone of the Booking Date. This is the ISO code for your time zone setting. You can view the time zone setting for your company account in
* `booking_date_ams` - The timestamp indicating when the event was entered into Adyen's accounting system, in Amsterdam time (CET or CEST). Format: \`YYYY-MM-DD
* `additionaltype` - Additional journal type that gives more information about the entry
* `issuer_country` - The ISO country code of the issuer
* `shopper_country` - The ISO country code of the shopper, if available
* `clearing_network` - The clearing network. For example: Maestro, MasterCard, MoneySend, VISA, VISA Returns, VISA OCT
* `terminal_id` - Point-of-sale terminal identifier, for example P400Plus-123456789
* `tender_reference` - The tender reference of the point-of-sale payment
* `merchant_order_reference` - A reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference
* `metadata` - Contents from the metadata object related to the payment, in the form of key value pairs
* `pos_transaction_date` - The transaction date for a point-of-sale transaction. Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `pos_transaction_date_timezone` - The time zone of the Pos Transaction Date
* `store` - The identifier assigned to the store in your point-of-sale account
* `dispute_reference` - Adyen's unique 16 character reference for the dispute
* `register_booking_type` - Custom column concatenating the record type and the booking type of the entry
* `arn` - The Acquirer Reference Number, a unique number that tags a credit card transaction when it goes from your bank (the acquiring bank) to the card
* `shopper_reference` - The shopper ID or reference that was specified in the original transaction
* `payment_transaction_group` - A custom value that corresponds with a merchant-specific transaction group. This value is for specific use cases, and can be configured on request
* `settlement_flow` - The Adyen flow into which the transaction was booked
* `split_payment_data` - Split payment data for the payment, if applicable
* `authorisation_code` - The authorisation code returned for a successful payment
* `card_number` - Obfuscated card number showing the card BIN, an obfuscated section and the last four digits. For example: 4111111111
* `authorised_date` - The timestamp indicating when the payment was authorised. Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `authorised_date_timezone` - The time zone of the Authorised Date
* `balance_currency` - The three-character ISO currency code for the balance account currency. This column is only relevant if your company has (split) payments that are
* `net_debit_bc` - The net debit (in Balance Currency) of the balance account. This column is only relevant if your company has (split) payments that are partly
* `net_credit_bc` - The net credit (in Balance Currency) of the balance account. This column is only relevant if your company has (split) payments that are partly
* `payment_fees_nc` - The total amount (in Net Currency) in fees, commissions, and interchange costs for the transaction
* `global_card_brand` - The brand of the card used for the payment
* `gratuity_amount` - The additional gratuity amount on the payment
* `surcharge_amount` - The surcharge amount on the payment
* `funds_destination` - This column is only relevant if you are upgrading your Adyen for Platforms integration from the classic Platforms integration. This column shows
* `balance_platform_debit` - The total amount debited to the Balance Platform for a split payment. This column is only relevant if your company has (split) payments that are
* `balance_platform_credit` - The total amount credited to the Balance Platform for a split payment. This column is only relevant if your company has (split) payments that are
* `installments` - For installment transactions, the installment this entry belongs to, written as '6/9' for the 6th of 9 installments
**Added by the connector:**
* `report_account` - Adyen account the report file was downloaded for
* `report_scope` - Account level the file came from: `MerchantAccount` or `Company`
* `report_file_name` - Name of the report file the row was read from
* `report_batch_number` - Settlement batch number of the file, used as the incremental replication key
One row per accounting event of every payment — Received, Authorised, Refused, Captured, Settled, Refunded, Chargeback, PaidOut and the rest — with the fee columns that go with each stage. This is the stream that ties a payment to its cost.
**Report columns:**
* `company_account` - The name of your company account as registered in the Adyen payments platform
* `merchant_account` - The name of the merchant account that was used to process the original payment request. The report may contain line items for multiple merchant
* `psp_reference` - Adyen's 16-character unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with
* `merchant_reference` - The reference that was specified in the payment request
* `payment_method` - The payment method used for the transaction. For example: visa, mc, amex
* `booking_date` - The timestamp indicating when the event was entered into Adyen's accounting system. The format is `YYYY-MM-DD HH:MM:SS`. For example: 2021-07-26
* `timezone` - The time zone of the Booking Date column. This is the ISO code for your time zone setting
* `main_currency` - The three-character ISO code for the currency of the main amount
* `main_amount` - The amount recorded when the transaction reaches the Record Type. For example, the main amount of a `Settled` transaction is the amount after
* `record_type` - The accounting record type of the entry, which is the stage of the payment lifecycle it records. For example: Received, Authorised, Refused,
* `payment_currency` - The three-character ISO code for the currency that was used to process the payment
* `received_pc` - The amount (in Payment Currency) debited or credited on the Received accounting register
* `authorised_pc` - The amount (in Payment Currency) debited or credited on the Authorised accounting register
* `captured_pc` - The amount (in Payment Currency) debited or credited on the Captured accounting register
* `settlement_currency` - The three-character ISO code for the currency that was used when settling the payment
* `payable_sc` - The amount (in Settlement Currency) debited or credited on the Payable accounting register. This will be paid out to your bank account
* `commission_sc` - The commission fee that was withheld by the acquirer (in Settlement Currency) If the acquirer provides the transaction information at the
* `markup_sc` - The fee charged by the acquiring bank (in Settlement Currency)
* `scheme_fees_sc` - The fee charged by, for example, Visa or Mastercard (in Settlement Currency)
* `interchange_sc` - The fee charged by the issuing bank (in Settlement Currency)
* `processing_fee_currency` - The three-character ISO code for the currency in which the processing (or gateway) fee is charged
* `processing_fee_fc` - The amount (in Processing Fee Currency) charged on the Processing Fee accounting register
* `user_name` - The user (interactive or webservice user) who performed the action resulting in the accounting record. If the record was created by an automated
* `payment_method_variant` - The sub-brand of the payment method (if applicable). For example: visaclassic, visadebit, mccorporate
* `modification_merchant_reference` - The optional modification reference for modifications, if specified in the transaction
* `metadata` - The contents of the metadata object of the payment, in the form of key-value pairs
* `merchant_order_reference` - A reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference
* `reserved3` - Reserved for future enhancements
* `reserved4` - Reserved for future enhancements
* `reserved5` - Reserved for future enhancements
* `reserved6` - Reserved for future enhancements
* `reserved7` - Reserved for future enhancements
* `reserved8` - Reserved for future enhancements
* `reserved9` - Reserved for future enhancements
* `reserved10` - Reserved for future enhancements
* `issuer_country` - The two-character ISO 3166-1 alpha-2 country code where the card was issued
* `shopper_country` - The two-character ISO country code of the shopper, if available
* `payable_batch` - The sequence number of the payout batch
* `unique_terminal_id` - Point-of-sale terminal identifier, for example P400Plus-123456789
* `booking_date_ams` - The timestamp indicating when the event was entered into Adyen's accounting system, in Amsterdam time (CET or CEST). Format: \`YYYY-MM-DD
* `creation_date` - The timestamp indicating when the payment was created on the Adyen payments platform. Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `creation_date_ams` - The Creation Date in Amsterdam time (CET or CEST). Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `payout_date` - The timestamp indicating the payout date, when available. Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `gratuity_amount` - The additional gratuity amount on the payment
* `icsf_details` - The detailed specification of each applicable interchange and scheme fee for the payment, if available. The data is included in this columns in
* `card_number` - Obfuscated card number showing the card BIN, an obfuscated section, and the last four digits. For example: 4111111111
* `acquirer` - The name of the acquirer that processed the original payment. For example: Cielo, Redecard
* `acquirer_account` - The acquirer account that was used for the transaction
* `mid` - The Merchant ID from the acquirer that was used to process the payment
* `acquirer_auth_code` - The Acquirer Authorisation Code. Can be included and used to match Auth Code on the merchant gateway side with the Auth Code in this report
* `acquirer_reference` - The acquirer's unique ID for the payment, if available
* `arn` - The Acquirer Reference Number, a unique number that tags a credit card transaction when it goes from your bank (The Acquiring Bank) through to the
* `original_amount` - The amount of the transaction
* `installments_pc` - The amount of the installment, in payment currency (PC)
* `advanced_pc` - The installment amount that was advanced. This is the gross amount of the advancement fee, in payment currency (PC)
* `advancement_code` - The code of the advancement. An advancement code can contain multiple advancement batches
* `advancement_batch` - The code of the advancement batch
* `booking_type` - Identifies the transaction/installment that was accelerated or represented. Possible values: FIRST: Installment first/original presentment
* `advancement_fee_percent` - The calculated fee for the advancement of an installment, as a percentage
* `installments` - For installment transactions, the installment this entry belongs to, written as '6/9' for the 6th of 9 installments
* `store` - The store identifier, as configured in point-of-sale
* `issuer_name` - Name of the issuing bank, if available
* `risk_premium` - For payments where the Record Type is Received, the value of this field indicates if the payment triggered RevenueProtect checks (resulting in
* `register_booking_type` - Custom column concatenating the record type and the booking type of the entry
* `modification_psp_reference` - In most instances, this is Adyen's unique 16 character code child reference that is associated with the modification request, for example,
* `shopper_reference` - The shopper ID or reference that was specified in the original transaction
* `shopper_name` - The name of the cardholder, as specified in the transaction, if available
* `payment_account_reference` - The Payment Account Reference is a unique identifier that links a network token with the underlying primary account number (PAN)
* `tender_reference` - The tender reference of the point-of-sale payment
* `dcc_markup_sc` - The DCC markup (in Settlement Currency)
* `global_card_brand` - The brand of the card used for the payment
* `surcharge_amount` - The surcharge amount on the payment
* `funding_source` - The funding source of the card used for the payment. Possible values: CREDIT, DEBIT, DEFERRED\_DEBIT, PREPAID, PREPAID\_RELOADABLE,
* `payment_requester_type` - Contains the value `autorescue` if there was an auto rescue attempt for the payment
* `network_token_used` - If true, a network token was used to authorize the payment
* `network_token_available` - If true, a network token was available for the payment
* `split_payment_data` - Split payment data for the payment, if applicable
* `exchange_rate` - The exchange rate for the payment
**Added by the connector:**
* `report_account` - Adyen account the report file was downloaded for
* `report_scope` - Account level the file came from: `MerchantAccount` or `Company`
* `report_file_name` - Name of the report file the row was read from
* `report_date` - Date the report file covers, used as the incremental replication key
One row per payment attempt, authorised or refused, with the acquirer's answer (`acquirer_response` and `raw_acquirer_response`), the risk score, the 3D Secure result and the shopper and card details.
**Report columns:**
* `company_account` - The name of your company account as registered in the Adyen payments platform
* `merchant_account` - The name of the merchant account that was used to process the original payment request. The report may contain line items for multiple merchant
* `psp_reference` - Adyen's 16-character unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with
* `merchant_reference` - The reference that was specified in the payment request
* `payment_method` - The payment method used for the transaction. For example: visa, mc, mc\_applepay, amex
* `creation_date` - The timestamp indicating when the payment was created on the Adyen payments platform. Format: `YYYY-MM-DD HH:MM:SS`. For example: 2012-07-26 19:58:55
* `time_zone` - The time zone of the Creation Date. This is the ISO code for your time zone setting
* `currency` - The three-character ISO currency code
* `amount` - The amount of the payment (authorisation amount). Always a positive value, even if the payment was canceled before being captured
* `type` - The record type. For this report, the value is always Payment
* `risk_scoring` - The total risk score of the payment
* `shopper_interaction` - The transaction type. Possible values: Ecommerce, ContAuth, POS, MOTO
* `shopper_name` - The name of the cardholder, as specified in the transaction, if available
* `shopper_pan` - The Primary Account Number (PAN). In case of card payments, the last four digits of the card number. For SEPA, this field shows the IBAN and BIC
* `shopper_ip` - The IP address (IPV4 or IPV6) of the shopper as specified in the original transaction, if available
* `shopper_country` - The ISO country code of the shopper, if available. If not available, this is computed based on the shopper's IP address
* `issuer_name` - The name of the issuing bank, if available
* `issuer_id` - The unique identifier of the issuer. In case of card payments this will be the issuer BIN (first six digits of the card number)
* `issuer_city` - The city of the issuer, if available
* `issuer_country` - The ISO country code of the issuer
* `acquirer_response` - The normalized response from the acquirer. Not necessarily the final status of the payment. When a payment is canceled before being captured, the
* `authorisation_code` - The authorisation code returned for a successful payment
* `shopper_email` - The email address of the shopper, as specified in the original transaction, if available
* `shopper_reference` - The shopper ID or reference that was specified in the original transaction
* `three_d_directory_response` - For payments processed with 3D Secure (Secure Code/Verified by Visa), the 3D Directory response. Values: Y, N, U, E
* `three_d_authentication_response` - For payments processed with 3D Secure (Secure Code/Verified by Visa), and directory response Y, this holds the authentication response. Values: Y,
* `cvc2_response` - The result passed back by the issuer after verifying the CVC2, or CVV2/CID in case of Visa/Amex
* `avs_response` - If Address Verification (AVS) was performed, the result of the AVS Check
* `billing_street` - The street part of the billing address
* `billing_house_number_name` - The house number or name part of the billing address
* `billing_city` - The city part of the billing address
* `billing_postal_code_zip` - The ZIP code or postal code part of the billing address
* `billing_state_province` - The state or province of the billing address
* `billing_country` - The ISO country code of the billing address
* `delivery_street` - The street part of the delivery address
* `delivery_house_number_name` - The house number or name part of the billing address
* `delivery_city` - The city part of the delivery address
* `delivery_postal_code_zip` - The ZIP code or postal code part of the delivery address
* `delivery_state_province` - The state or province of the delivery address
* `delivery_country` - The ISO country code of the delivery address
* `acquirer_reference` - The reference number for the transaction provided by the acquirer
* `payment_method_variant` - The payment method sub-brand, or the main payment method if not available (for example mccredit or visagold)
* `raw_acquirer_response` - The raw response we receive from the acquirer, where available. When a payment is canceled before being captured, the raw acquirer response will
* `original_amount` - The original amount of the payment
* `cashback_amount` - The additional cashback amount on the payment
* `pos_charity_amount` - The additional charity amount on the payment. Applies to point-of-sale transactions
* `pos_gratuity_amount` - The additional gratuity amount on the payment. Applies to point-of-sale transactions
* `pos_cashback_amount` - The additional cashback amount on the payment. Applies to point-of-sale transactions
* `pos_discount_amount` - The additional discount amount on the payment. Applies to point-of-sale transactions
* `pos_surcharge_amount` - The surcharge amount on the payment
* `pos_payment_device` - The device that was used to make the payment
* `shopper_phone_number` - The phone number of the shopper, as specified in the original transaction, if available
* `alternative_acquirer_reference` - The alternative acquirer reference of the acquirer that was used for the transaction
* `acquirer` - Name of the acquirer that processed the original payment
* `acquirer_account` - The acquirer account that was used for the transaction
* `installments` - For installment transactions, the installment this entry belongs to, written as '6/9' for the 6th of 9 installments
* `dcc` - Whether Dynamic Currency Conversion was used for the payment. Possible values: 'DCC accepted', 'DCC declined' (the shopper paid in the merchant
* `bcmc_iban_bic` - The Bancontact IBAN or BIC
* `bin_funding_source` - The funding source derived from the card BIN. Possible values: CREDIT, DEBIT, DEFERRED\_DEBIT, PREPAID, PREPAID\_RELOADABLE, PREPAID\_NONRELOADABLE
* `device_fingerprint` - The device fingerprint of the shopper's device, as specified in the original transaction, if available
* `device` - The device that was used to make the payment
* `browser` - The browser that was used to make the payment
* `merchant_order_reference` - A reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference
* `payment_requester_type` - Contains the value `autorescue` if there was an auto rescue attempt for the payment
* `network_token_used` - If true, a network token was used to authorise the payment
* `network_token_available` - If true, a network token was available for use for the payment
* `airline_data` - Airline data related to the payment, if available
* `risk_profile` - The name of the risk profile that was evaluated during the transaction
* `risk_profile_id` - The ID of the risk profile that was evaluated during the transaction
* `risk_profile_reference` - The reference number of the risk profile that was evaluated during the transaction
* `pos_transaction_date` - The transaction date for a point-of-sale transaction
* `pos_store` - The identifier assigned to the store in your point-of-sale account
* `pos_entry_mode` - How the card details were captured at the point of sale. For example: MKE, MSR, Bar Code Read, OCR Coding Read, Chip, CLTS Chip, RFID, CTLS MSR or
* `pos_cvm_performed` - A two-digit hexadecimal code indicating the type of card verification that was used
* `pos_library_implementation` - The type of library implementation, for example Android, iOS, C or .NET
* `pos_library_version` - Version number of the library used, or standalone if the payment terminal is not integrated with the POS system
* `pos_terminal_version` - The version of the POS terminal application
* `ares_transstatus` - The transaction status of the 3D Secure 2 authentication request. This is the final result of the authentication, unless the value is C, which
* `rreq_transstatus` - The result of the 3D Secure challenge flow that is sent to the 3D Secure directory server. This is the final result of the authentication. This
* `three_ds_version` - The version of the 3D Secure protocol used for the payment
* `liability_shift` - Indicates if a liability shift took place for the payment. Possible values: TRUE or FALSE
* `merchant_category_code` - The Merchant Category Code
* `retry_json` - Retry information about the payment
* `pos_store_and_forward_indicator` - Indicates if this was a store-and-forward transaction. Possible values: TRUE or FALSE
* `pos_cash_register_name` - The name of the POS system
* `pos_tender_reference` - The tender reference of the point-of-sale payment
* `split_payment_data` - Split payment data for the payment, if applicable
* `realtime_account_updater_status` - The status of the Real Time Account Updater request
* `original_card_bin` - The card BIN of the card that was used to process the original payment request
* `network_transaction_reference` - The network transaction reference of the payment
* `card_number` - Obfuscated card number showing the card BIN, an obfuscated section and the last four digits. For example: 4111111111
* `metadata` - The contents of the metadata object of the payment, in the form of key value pairs
* `global_card_brand` - The brand of the card used for the payment
* `recurring_detail_reference` - The recurring detail reference used for the payment
* `reserved2` - Reserved for future enhancements
* `reserved3` - Reserved for future enhancements
**Added by the connector:**
* `report_account` - Adyen account the report file was downloaded for
* `report_scope` - Account level the file came from: `MerchantAccount` or `Company`
* `report_file_name` - Name of the report file the row was read from
* `report_date` - Date the report file covers, used as the incremental replication key
Chargebacks, second chargebacks, notifications of fraud and requests for information, with the scheme reason codes and the dates of the dispute life cycle.
**Report columns:**
* `company_account` - Name of your company account as registered in the Adyen payments platform
* `merchant_account` - Name of your merchant account used to process the original payment request
* `psp_reference` - Adyen's unique 16 character reference for the payment. This is the PSP reference for the original authorisation request
* `merchant_reference` - Reference number provided when initiating the payment request
* `payment_method` - Payment method type of the payment which was processed. For example: visa, mc, amex
* `record_date` - Timestamp of when the dispute event took place as entered into Adyen's accounting system. Format: `YYYY-MM-DD HH:MM:SS` For example: 2012-07-26
* `record_date_timezone` - Time zone of the Record Date. This is the ISO code for your time zone setting
* `dispute_currency` - Disputes do not have to be in the original transaction currency, but can be in the currency of the cardholder. Also disputes can be of a lower
* `dispute_amount` - The amount of the disputed payment. For example, 100.00
* `record_type` - The accounting record type of the entry, which is the stage of the payment lifecycle it records. For example: Received, Authorised, Refused,
* `dispute_psp_reference` - Adyen's unique 16 character reference for the dispute
* `dispute_reason` - Dispute reason (free format) provided by the bank or payment method
* `rfi_scheme_code` - Payment method scheme/institution which issued the code in the following column. For example: visa, mc, amex
* `rfi_reason_code` - Request for Information reason code as provided by the bank or payment method. The mapping is defined by the scheme/institution. This is blank if
* `cb_scheme_code` - Payment method scheme/institution which issued the code in the following column. For example: visa, mc, amex
* `cb_reason_code` - Chargeback reason code as provided by the bank or payment method. The mapping is defined by the scheme/institution. This may be blank if there is
* `nof_scheme_code` - Payment method scheme/institution which issued the Notification of Fraud (NoF) code in the NoF Reason Code column. For example: visa, mc, amex
* `nof_reason_code` - Notification of Fraud reason code as provided by the bank or payment method. The mapping is defined by the scheme/institution
* `payment_date` - Date of the original payment (authorisation)
* `payment_date_timezone` - Time zone of the Payment Date. This is the ISO code for your time zone setting
* `payment_currency` - Three character ISO code for the currency which was used for processing the payment. This may differ from the dispute currency in rare cases
* `payment_amount` - Authorisation amount of the original payment
* `dispute_date` - Date the dispute was first entered into the system. This can be the same date as the RFI
* `dispute_date_timezone` - Time zone of the Dispute Date. This is the ISO code for your time zone setting
* `dispute_arn` - Acquirer Reference Number, a unique number that tags a dispute when it goes from your bank account (The Acquiring Bank)
* `user_name` - User (interactive or webservice user) who performed the action resulting in the accounting record. If the record was created by an automated
* `risk_scoring` - Total risk scoring value of the original payment
* `shopper_interaction` - Transaction type. Possible values: Ecommerce, ContAuth, POS, Moto
* `shopper_name` - Name of the cardholder as provided during the original transaction (if available)
* `shopper_email` - Email address of the shopper/consumer as provided during the original transaction (if available)
* `shopper_reference` - Supplied customer ID/reference as supplied in the original transaction
* `shopper_pan` - Account number of the shopper/consumer. In case of card payments, the last four digits of the card number
* `iban` - Shopper's bank account IBAN number
* `bic` - Shopper's bank account BIC number
* `shopper_ip` - IP address (IPV4 or IPV6) of the shopper/consumer as provided during the original transaction (if available)
* `shopper_country` - ISO country code of the shopper (if available)
* `issuer_country` - ISO country code of the issuer (if available)
* `issuer_id` - Unique identifier of the issuer. In case of card payments this will be the issuer BIN (first 6 digits of the card number)
* `three_d_directory_response` - Payments which were processed using 3D Secure (Secure Code / Verified by Visa), the directory response. Possible values: Y, N, U, E
* `three_d_authentication_response` - Payments which were processed using 3D Secure (Secure Code / Verified by Visa) and had directory response 'Y', the authentication response
* `cvc2_response` - Result passed back by the issuer after verifying the CVC2 (or CVV2/CID in case of Visa/Amex)
* `avs_response` - Result of the AVS check, if performed
* `dispute_auto_defended` - Set to `true`, if chargeback was auto-defended by Adyen. Empty if it was not
* `dispute_end_date` - Date and time of day when dispute defense period ended
* `dispute_end_date_timezone` - Time zone of the Dispute End Date. This is the ISO code for your time zone setting
* `reserved4` - Reserved for future enhancements
* `reserved5` - Reserved for future enhancements
* `acquirer` - Name of the Acquirer that processed the original payment
* `acquirer_account` - The Acquirer account that was used for the transaction
* `issuer_region_program` - The issuer region in which the transaction was made
* `liability_shift` - Indicates if there was a liability shift for the transaction
* `metadata` - Contents from the metadata object related to the payment, in the form of key value pairs
* `data_ed` - Contents from the `Data Ed` object related to the dispute
* `rdr` - Indicates Rapid Dispute Resolution (RDR) chargebacks (Visa only)
* `second_chargeback` - Indicator that marks if a second chargeback is present
* `shopper_phone_number` - Phone number of the shopper or consumer as provided during the original transaction (if available)
* `shopper_statement` - The shopper statement (descriptor) posted in the payment request
* `status` - The most recent chargeback status
**Added by the connector:**
* `report_account` - Adyen account the report file was downloaded for
* `report_scope` - Account level the file came from: `MerchantAccount` or `Company`
* `report_file_name` - Name of the report file the row was read from
* `report_date` - Date the report file covers, used as the incremental replication key
Transactions settled by an external acquirer rather than by Adyen. Empty unless your account processes through an external acquirer.
**Report columns:**
* `company_account` - Name of your company account within the Adyen payments platform
* `merchant_account` - Name of your merchant account that was used to process the original payment request. The report may contain line items for multiple merchant accounts
* `psp_reference` - Unique 16-character reference provided by Adyen for the original authorisation request. For unmatched transactions, this field can contain a
* `merchant_reference` - Reference number that you provided when initiating the payment request
* `payment_method` - Payment method type of the processed payment. For example: `visa`, `mc`, or `amex`
* `creation_date` - The timestamp of when the payment was received by the Adyen payments platform. Format: `YYYY-MM-DD HH:MM:SS` For example: `2012-07-26 19:58:55`
* `timezone` - The time zone of the Creation Date. This is the ISO code for your time zone setting
* `type` - Journal type of the entry
* `modification_reference` - Adyen's unique 16-character reference for the modification (capture, refund or chargeback) that produced the entry. For MerchantPayout entries it
* `gross_currency` - Three-character ISO currency code that was used for processing the payment (transaction currency)
* `gross_debit_gc` - Amount submitted in the transaction request. For example, `100.00`
* `gross_credit_gc` - Amount submitted in the transaction request. For example, `100.00`
* `exchange_rate` - Exchange rate used for converting the gross amount into the net amount. This is 1 if you process and settle in the same currency
* `net_currency` - Three-character ISO currency code that was used for processing the payment (settlement currency)
* `net_debit_nc` - Amount submitted in the transaction request minus acquirer fees. For example: `100.00`
* `net_credit_nc` - Amount submitted in the transaction request minus acquirer fees. For example: `100.00`
* `commission_nc` - The commission fee withheld by the acquirer, in the settlement (net) currency. When the acquirer reports at interchange level this column is empty
* `markup_nc` - Fee charged by the acquirer. This field is empty if the acquirer doesn't provide transaction information at the interchange level
* `scheme_fees_nc` - Fee which is charged by Visa or Mastercard. This field is empty if the acquirer doesn't provide transaction information at the interchange level
* `interchange_nc` - Fee charged by the issuing bank. This field is empty if the acquirer doesn't provide transaction information at the interchange level
* `payment_method_variant` - Payment method sub-type of the processed payment. For example: `visa classic`, `mc`, or `amex`
* `acquirer` - Name of the acquirer that processed the original payment. For example: `Cielo` or `Redecard`
* `mid` - Merchant ID from the acquirer that was used for processing the payment
* `arn` - Acquirer Reference Number, a unique number that tags a credit card transaction when it goes from the acquirer to the card scheme at the issuer
* `acquirer_reference` - The acquirer's unique ID for the payment, if provided
* `modification_merchant_reference` - Your optional reference for the payment modification
* `reserved7` - Where installment transactions are applicable, this shows the installment corresponding to this entry. For example, `6/9` indicates that this
* `reserved8` - Reserved for future enhancements
* `reserved9` - Reserved for future enhancements
* `reserved10` - Reserved for future enhancements
* `store_code` - Identifier for the store where a transaction occurs
* `merchant_order_reference` - A reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference
* `acquirer_auth_code` - Authorisation code returned by the acquirer for a successful payment. You can match it to the Authorisation Code on the merchant gateway.This code
* `card_bin` - First six digits of the card number
* `card_number_summary` - Last four digits of the card number
* `submerchant_identifier` - An identifier for the Merchant of Record when a transaction is submitted through a payment facilitator. The payment facilitator must send this
* `metadata` - The contents of the metadata object of the payment, in the form of key:value pairs
**Added by the connector:**
* `report_account` - Adyen account the report file was downloaded for
* `report_scope` - Account level the file came from: `MerchantAccount` or `Company`
* `report_file_name` - Name of the report file the row was read from
* `report_date` - Date the report file covers, used as the incremental replication key