> Continuous Process Improvement > Payments Processing > Adyen > Data Template

Your Payments Processing Data Template

Adyen

Payments Processing Attributes (20) Payments Processing Activities (16) Extraction Guides (2)

Your Payments Processing Data Template

This template provides a comprehensive guide for collecting the necessary data to analyze your payments processing in Adyen. It outlines all essential data attributes and process activities to track, along with practical instructions for data extraction. Use this to ensure you capture all critical information for effective process mining.

Recommended attributes to collect
Key activities to track
Practical extraction guidance for Adyen

New to event logs? Learn how to create a process mining event log.

Download Template

Payments Processing Attributes

These are the recommended data fields to include in your event log for comprehensive analysis of your payments processing within Adyen.

5 Required 7 Recommended 8 Optional

	Name	Description
	Activity Name EventCode	The specific stage or action occurring in the payment lifecycle.
Description This attribute defines the specific event that has occurred, such as AUTHORISATION, CAPTURE, or REFUND. It dictates the nodes in the process map and determines the flow of the transaction. In analysis, these codes are translated into human-readable activity names to visualize the process flow. Variations in the sequence of these codes indicate different process paths, such as straight-through processing versus exception handling. Why it matters Defines the 'what' of the process mining model, enabling the visualization of process flows. Where to get Adyen Notification Webhooks 'eventCode' field. Examples AUTHORISATIONCAPTUREREFUNDCANCELLATIONCHARGEBACK
	Event Timestamp EventDate	The date and time when the specific payment activity occurred.
Description This attribute records the precise timestamp of when an event (like authorization or settlement) was logged in the system. It allows for the chronological ordering of activities within a case. In analysis, this is crucial for calculating cycle times, identifying bottlenecks, and determining the throughput of the system over time. It supports all time-based KPIs such as 'Overall Payment Cycle Time'. Why it matters Essential for ordering events and calculating all duration-based metrics. Where to get Adyen Notification Webhooks 'eventDate' field. Examples 2023-10-27T10:00:00+01:002023-10-27T10:05:30+01:002023-10-28T09:15:00+01:00
	Payment Transaction ID PspReference	The unique reference identifier assigned by Adyen to each payment transaction.
Description This attribute serves as the primary key for the entire payment lifecycle within the Adyen ecosystem. It links the initial payment request to subsequent events such as authorization, capture, settlement, and potential refunds or chargebacks. In analysis, this ID is used to group discrete events into a single case, enabling end-to-end process reconstruction. It allows analysts to track the specific journey of a payment from the shopper's initiation to the final financial settlement. Why it matters It is the fundamental link that groups disconnected events into a single process instance for mining. Where to get Adyen Payment Response 'pspReference' or Settlement Detail Report 'PSP Reference' column. Examples 851564567890123479145612345678908825641234567890
	Last Data Update LastDataUpdate	The timestamp when the record was last extracted or refreshed.
Description This attribute indicates the freshness of the data in the process mining model. It helps users understand if they are looking at real-time data or a snapshot. In analysis, this is primarily a technical field used for data governance and validating that the pipeline is running correctly. Why it matters Technical field to track data freshness. Where to get System time at extraction. Examples 2023-10-30T12:00:00Z
	Source System SourceSystem	The name of the system where the data originated.
Description This static attribute identifies that the record came from Adyen. In multi-system process mining (e.g., combining Adyen with SAP), this is crucial for lineage. In analysis, it allows users to filter activities that specifically occurred within the payment gateway versus the ERP or Order Management System. Why it matters Crucial for data lineage in multi-system process mining. Where to get Static value during extraction. Examples AdyenAdyen_Production
	Is Rework IsRework	Flag indicating if the transaction involved retries or error corrections.
Description A boolean flag that is true if the case contains multiple attempts at authorization, or contains activities like 'Payment Refused' followed by a retry. In analysis, this drives the 'Payment Rework and Exception Hotspots' dashboard. It allows analysts to filter specifically for problematic cases to understand why process flows are not following the happy path. Why it matters Identifies inefficient cases requiring manual or system intervention. Where to get Calculated based on occurrence of failure events > 0. Examples truefalse
	Merchant Account MerchantAccount	The specific merchant account within Adyen processing the transaction.
Description Adyen allows multiple merchant accounts under a single company account. This attribute identifies which specific business unit, brand, or regional entity processed the payment. In analysis, this serves as a primary dimension for segmentation. It allows stakeholders to compare performance, failure rates, and volumes across different business units or brands to identify specific areas for improvement. Why it matters Key for segmenting performance by business unit or subsidiary. Where to get Adyen Payment Request/Response 'merchantAccount'. Examples MyStore_UKMyStore_USGlobalSales_Main
	Overall Payment Cycle Time TotalCycleTime	The total duration from payment request creation to settlement.
Description This is a calculated metric measuring the time elapsed between the very first event (e.g., 'Payment Request Received') and the 'Payment Settled' event. In analysis, this is the primary efficiency KPI. It highlights the speed of cash flow. Long cycle times might indicate issues with capture delays or settlement cycles. Why it matters KPI for working capital optimization. Where to get Calculated: Timestamp(Settled) - Timestamp(Created). Examples 2 days4 hours5 minutes
	Payment Method PaymentMethod	The specific method used by the shopper to pay, such as Visa or PayPal.
Description This attribute captures the type of payment instrument used, including credit card brands (Visa, MC), digital wallets (PayPal, Apple Pay), or local payment methods (iDEAL, Sofort). In analysis, this is vital for the 'Payment Method Performance Insights' dashboard. It helps correlations between specific payment methods and authorization rates, processing speeds, or technical failures. Why it matters Critical for analyzing success rates and costs across different payment providers. Where to get Adyen Payment Response 'paymentMethod.brand' or 'paymentMethod.type'. Examples visamcpaypalidealklarna
	Payment Status PaymentStatus	The current state of the payment (e.g., Authorised, Settled, Refused).
Description This attribute reflects the latest known status of the payment transaction. It is often derived from the most recent activity in the case. In analysis, it allows for quick filtering of cases (e.g., 'Show me all currently Refused payments'). It is essential for the 'Payment Throughput and Status Monitoring' dashboard. Why it matters Provides a snapshot of the current health of the transaction. Where to get Derived from the last event code in the case. Examples SettledRefusedAuthorised
	Refusal Reason RefusalReason	The text description explaining why a payment was refused or failed.
Description When a transaction fails, Adyen provides a reason code or description (e.g., 'Not enough balance', 'CVC Declined', 'Expired Card'). In analysis, this is the primary driver for the 'Payment Transaction Failure Rate' dashboard. Analyzing these reasons helps identify whether failures are due to technical issues, fraud rules, or shopper behavior, guiding specific remediation actions. Why it matters The key attribute for root cause analysis of failed payments. Where to get Adyen Payment Response 'refusalReason'. Examples RefusedNot enough balanceExpired CardAcquirer ErrorFraud
	Transaction Amount PaymentAmount	The monetary value of the payment transaction.
Description This attribute represents the financial value associated with the transaction. It is usually stored as a minor unit (e.g., cents) in the raw data but should be converted for reporting. In analysis, this enables the 'Payment Throughput' dashboard and helps prioritize high-value rework cases. It is also used to calculate the total volume processed and financial impact of failed transactions. Why it matters Necessary for financial impact analysis and throughput monitoring. Where to get Adyen Payment Request 'amount.value'. Examples 10005509900
	Acquirer Reference AcquirerReference	Reference number provided by the acquiring bank.
Description This is the external reference assigned by the underlying financial institution (acquirer) that processes the card transaction. It is distinct from the Adyen PSP reference. In analysis, this field is critical for the 'Payment Reconciliation Delay Analysis'. It is the key used to match Adyen records against bank statements in external ledgers. Why it matters Essential for 3-way matching and external reconciliation. Where to get Adyen Payment Response 'additionalData.acquirerReference'. Examples 1234567890987654321
	Auth Code AuthorisationCode	The authorization code returned by the issuer upon approval.
Description A code indicating that the funds have been reserved on the shopper's card. This is the proof of a successful authorization. In analysis, this is primarily for audit and traceability. It validates that the 'Payment Authorised' activity was legitimate. Why it matters Proof of successful authorization for audit trails. Where to get Adyen Payment Response 'authCode'. Examples 123456098712
	Currency PaymentCurrency	The three-letter ISO code denoting the currency of the transaction.
Description This attribute defines the currency in which the `PaymentAmount` is expressed. Common values include EUR, USD, GBP, etc. In analysis, this is used to group transactions by market and is essential for normalizing financial values when aggregating data across different regions. Why it matters Contextualizes the amount field for multi-currency reporting. Where to get Adyen Payment Request 'amount.currency'. Examples EURUSDGBP
	Customer ID ShopperReference	A unique reference used to identify the shopper across multiple transactions.
Description This identifier links different transactions to the same customer entity. It is provided by the merchant during the payment request. In analysis, this allows for a customer-centric analysis, enabling the detection of repeat offenders in fraud cases or loyal customers in successful transaction analysis. It facilitates the 'Customer' generic mapping. Why it matters Enables customer-level aggregation and behavior analysis. Where to get Adyen Payment Request 'shopperReference'. Examples CUST-001user_12345email@example.com
	Fraud Risk Score RiskScore	The risk score assigned to the transaction by the fraud engine.
Description Adyen's RevenueProtect engine assigns a numeric score (0-100) indicating the likelihood of fraud. Higher scores often trigger manual review or automatic blocking. In analysis, this supports the 'Financial Compliance Risk Overview'. Correlating high risk scores with chargebacks helps tune fraud rules. High scores that result in successful payments might indicate false positives in the risk model. Why it matters Essential for analyzing the efficiency of fraud prevention logic. Where to get Adyen Risk API response or Reporting 'fraudResult.accountScore'. Examples 025100
	Settlement Batch Number BatchNumber	The batch number associated with the settlement of funds.
Description Adyen groups settled payments into batches for payout. This attribute identifies which batch a specific transaction belongs to. In analysis, this is used to group payments by their payout cycle. It helps in auditing if specific batches are delayed and supports the 'Payment Settled' activity tracking. Why it matters Links individual transactions to bulk financial settlements. Where to get Adyen Settlement Detail Report 'Batch Number'. Examples 100255
	Shopper Country ShopperCountry	The two-letter country code of the shopper.
Description This attribute indicates the location of the shopper, typically derived from the card issuing country or billing address. In analysis, it is used for regional performance analysis. It helps identify if specific countries have higher decline rates or slower processing times due to local banking infrastructure. Why it matters Allows for geographic segmentation of payment performance. Where to get Adyen Payment Request 'countryCode' or 'billingAddress.country'. Examples NLUSDE
	Shopper Interaction Type ShopperInteraction	Indicates if the payment was Ecommerce, POS, or a subscription (ContAuth).
Description This attribute categorizes the nature of the interaction between the shopper and the merchant. Typical values are `Ecommerce` (online), `POS` (in-store), or `ContAuth` (recurring/subscription). In analysis, this helps distinguish between different business models and sales channels. Process flows often differ significantly between POS and Ecommerce, making this a vital filter for clean process discovery. Why it matters Differentiates process flows between online, in-store, and recurring payments. Where to get Adyen Payment Request 'shopperInteraction'. Examples EcommerceContAuthPOSMoto

Required Recommended Optional

Payments Processing Activities

These are the key process steps and milestones to capture in your event log for accurate process discovery in your Adyen payments flows.

5 Recommended 11 Optional

	Activity	Description
	Payment Authorised	The card issuer or payment method has approved the transaction and funds are reserved. Captured via the standard Adyen notification webhook.
Why it matters A critical milestone indicating the transaction is valid and funds are available. Precondition for capture. Where to get Adyen Notification Webhook: eventCode 'AUTHORISATION' with success='true'. Capture Logged on AUTHORISATION webhook success Event type explicit
	Payment Captured	The command to transfer funds from the shopper to the merchant has been successfully processed. This can be immediate (auto-capture) or delayed (manual capture).
Why it matters Confirms revenue recognition. The time between Authorization and Capture is key for 'Payment Authorization Lead Time' KPI. Where to get Adyen Notification Webhook: eventCode 'CAPTURE' with success='true'. Capture Logged on CAPTURE webhook success Event type explicit
	Payment Refused	The transaction was declined by the issuer or Adyen's risk rules. Captured via the authorization webhook with a failure status.
Why it matters Directly impacts the 'Payment Transaction Failure Rate' KPI. Analysis of refusal reasons helps optimize authorization rates. Where to get Adyen Notification Webhook: eventCode 'AUTHORISATION' with success='false'. Capture Logged on AUTHORISATION webhook failure Event type explicit
	Payment Request Received	The initial receipt of the transaction request by the Adyen payment platform. This is captured from the initial API request timestamp or the creation of the pspReference.
Why it matters Marks the absolute start of the process instance. Essential for calculating the total end-to-end cycle time. Where to get Adyen Payment API logs or the timestamp associated with the creation of the pspReference. Capture Logged when pspReference is generated via API Event type explicit
	Payment Settled	Funds have been successfully cleared and credited to the merchant's Adyen account. This appears in the Settlement Detail Report.
Why it matters The financial conclusion of the successful process. Essential for 'Overall Payment Cycle Time' and 'Payment Reconciliation Delay Analysis'. Where to get Adyen Settlement Detail Report (SDR), record type 'Settled'. Capture Logged when transaction appears in Settlement Report Event type explicit
	Capture Failed	The attempt to capture authorized funds failed, often due to technical timeout or card status changes between auth and capture.
Why it matters Critical error point requiring rework or retry. Contributes to 'Payment Exception Rate'. Where to get Adyen Notification Webhook: eventCode 'CAPTURE_FAILED'. Capture Logged on CAPTURE_FAILED webhook Event type explicit
	Chargeback Defended	Evidence has been submitted to Adyen to contest a chargeback. This represents a rework/manual activity in the dispute flow.
Why it matters Tracks the effort spent on revenue protection. Important for 'Payment Rework Rate'. Where to get Adyen Disputes API or Case Management logs showing evidence submission. Capture Inferred from status change to 'Defense Supplied' Event type inferred
	Chargeback Notification Received	Adyen has received a dispute notification from the card scheme. This triggers the dispute workflow.
Why it matters Major compliance and risk indicator. Drives the 'Compliance Incident Rate' and requires immediate manual intervention. Where to get Adyen Notification Webhook: eventCode 'CHARGEBACK' or 'NOTIFICATION_OF_CHARGEBACK'. Capture Logged on CHARGEBACK webhook Event type explicit
	Chargeback Reversed	The dispute was won, and funds are returned to the merchant. This is a successful resolution of an exception.
Why it matters Positive outcome for risk management. Offsets the financial impact of the initial chargeback. Where to get Adyen Notification Webhook: eventCode 'CHARGEBACK_REVERSED'. Capture Logged on CHARGEBACK_REVERSED webhook Event type explicit
	Payment Cancelled	The authorization was voided before funds were captured. This releases the reserved funds on the shopper's card.
Why it matters Represents a process loop where a valid order is terminated before completion, often due to customer request or inventory timeout. Where to get Adyen Notification Webhook: eventCode 'CANCELLATION'. Capture Logged on CANCELLATION webhook Event type explicit
	Payment Sent for Settlement	Adyen has forwarded the transaction to the acquiring bank or network for financial processing. The status changes to SentForSettlement.
Why it matters Marks the transition from operational processing to financial clearing. Delays here affect cash flow. Where to get Adyen Transaction Status API or inferred from status change history logs. Capture Compare status field transition to SentForSettlement Event type inferred
	Payout Confirmed	Funds associated with a batch of settled transactions have been paid out to the merchant's bank account.
Why it matters Represents the actual cash transfer to the business, linked to 'Payment Reconciliation Cycle Time'. Where to get Adyen Notification Webhook: eventCode 'PAYOUT_THIRD_PARTY' or inferred from Payout Report. Capture Join Payout Report batch ID to Transaction ID Event type inferred
	Refund Initiated	A request to return funds to the shopper has been triggered. This starts a reverse process flow.
Why it matters Indicates a post-settlement exception. High refund rates may indicate upstream quality issues. Where to get Adyen Notification Webhook: eventCode 'REFUND'. Capture Logged on REFUND webhook triggering Event type explicit
	Refund Settled	The refund has been processed financially and debited from the merchant account. Confirmed via the Settlement Detail Report.
Why it matters Closes the loop on the refund process. Important for 'Average Error Resolution Time' if the refund was due to error. Where to get Adyen Settlement Detail Report, record type 'Refunded' or 'RefundedReversed'. Capture Logged when refund appears in Settlement Report Event type explicit
	Risk Screening Performed	Adyen's RevenueProtect engine analyzes the transaction for fraud signals. This is inferred from the presence of a fraud score or risk result in the authorization response.
Why it matters High risk scores can trigger manual reviews or automatic refusals, creating bottlenecks or process termination points. Where to get Adyen Payment Response (fraudResult field) or Case Management logs. Capture Inferred from presence of fraudResult object Event type inferred
	Technical Error Logged	A system error occurred during processing, such as a webhook failure or API timeout. Identified via specific error codes in the interface.
Why it matters Directly supports 'Payment Transaction Failure Rate' analysis by categorizing technical vs. financial failures. Where to get Adyen Interface logs or specific failure responses in API calls. Capture Logged when error response code 5xx or 4xx is returned Event type explicit

Recommended Optional

Extraction Guides

How to get your data from Adyen

Steps

Log in to the Adyen Customer Area with a user account that has the Merchant Report role.
Navigate to Reports and select Settlement details from the menu.
Locate the Automatic generation settings or choose Generate report for a one-time export.
In the configuration panel, ensure the Format is set to CSV (comma-separated values).
Under Include columns, ensure you select All or specifically check: Company Account, Merchant Account, Psp Reference, Merchant Reference, Payment Method, Creation Date, TimeZone, Type, Modification Reference, Gross Currency, Gross Debit, Gross Credit, Exchange Rate, Net Currency, Net Debit, Net Credit, Commission, Markup, Scheme Fees, and Interchange.
IMPORTANT: Ensure the report scope includes all Journal Types (Settled, Refunded, Chargeback, PaidOut, etc.) to capture the full financial lifecycle.
Generate the report for the desired date range (e.g., Last 90 Days). Note that settlement reports generate based on the settlement batch date, not the transaction date.
Download the generated CSV file to your local extraction environment.
Run the transformation script (provided below) to reshape the 'Wide' CSV ledger into a 'Long' Event Log format required for ProcessMind.
The script performs critical transformations: it unpivots the Creation Date to create 'Payment Request Received' events and maps the Type column to specific financial activities.
Verify the output CSV contains headers: PspReference, EventCode, EventDate, SourceSystem.
Upload the final transformed CSV to ProcessMind.

Configuration

Report Type: Settlement Detail Report (financial ledger)
File Format: CSV (standard comma separation)
Granularity: Transaction Level (one row per financial journal entry)
Timezone: UTC (strongly recommended to align extraction with other systems)
Date Range: Aligns with Settlement Batches (Batch Closed Date), not Transaction Creation Date. Ensure overlap is handled if running incrementally.
Required Columns: Psp Reference (Key), Type (Activity), Creation Date, Booking Date (Event Timestamps), Merchant Account.
Filter Settings: Ensure no filters exclude 'Chargeback' or 'Refund' types to ensure process completeness.

a Sample Query config

import pandas as pd
from datetime import datetime

# CONFIGURATION
INPUT_FILE = 'settlement_detail_report.csv'
OUTPUT_FILE = 'adyen_event_log.csv'
SOURCE_SYSTEM = 'Adyen'

# Load the Adyen Settlement Detail Report
# Skip standard Adyen header rows if present (often reports start on row 1 or have metadata on top)
df = pd.read_csv(INPUT_FILE, keep_default_na=False)

# Define the output list
event_log = []

# Helper function to append events
def add_event(psp_ref, activity, timestamp, attributes):
    if not timestamp or str(timestamp).strip() == '':
        return
    base_event = {
        'PspReference': psp_ref,
        'EventCode': activity,
        'EventDate': timestamp,
        'SourceSystem': SOURCE_SYSTEM,
        'LastDataUpdate': datetime.utcnow().isoformat(),
        'MerchantAccount': attributes.get('Merchant Account', ''),
        'PaymentMethod': attributes.get('Payment Method', ''),
        'PaymentAmount': attributes.get('Gross Credit', 0) if attributes.get('Gross Credit') else attributes.get('Gross Debit', 0) * -1
    }
    # Merge optional attributes
    base_event.update(attributes)
    event_log.append(base_event)

# Iterate through the ledger rows
for index, row in df.iterrows():
    psp_ref = row.get('Psp Reference')
    journal_type = row.get('Type')
    creation_date = row.get('Creation Date') # Used for Auth/Request
    booking_date = row.get('Booking Date')   # Used for Settlement/Financials
    
    # Common attributes for this row
    row_attrs = {
        'MerchantAccount': row.get('Merchant Account'),
        'PaymentMethod': row.get('Payment Method'),
        'RefusalReason': row.get('Refusal Reason', ''),
        'PaymentStatus': journal_type
    }

    # --- 1. DERIVED UPSTREAM ACTIVITIES ---
    # Since this is a settlement report, we infer the Request/Auth from the Creation Date
    # of the first record we see for this PSP Reference. 
    # Logic: If Creation Date exists, implies Request and Auth occurred.
    
    if creation_date:
        # Activity: Payment Request Received
        add_event(psp_ref, 'Payment Request Received', creation_date, row_attrs)
        
        # Activity: Risk Screening Performed (Inferred from existence of transaction)
        # Note: True risk score requires 'Payments Accounting Report', inferred here for process continuity
        add_event(psp_ref, 'Risk Screening Performed', creation_date, row_attrs)
        
        # Activity: Payment Authorised
        # Typically happens immediately after request for successful settled items
        add_event(psp_ref, 'Payment Authorised', creation_date, row_attrs)

    # --- 2. MAPPED FINANCIAL ACTIVITIES ---
    # Map Adyen Ledger Types to Process Activities using Booking Date
    
    if journal_type == 'Settled':
        add_event(psp_ref, 'Payment Settled', booking_date, row_attrs)
        
        # Activity: Payment Sent for Settlement
        # Inferred: Occurs shortly before settlement. 
        # Using Creation Date if Booking Date is distinct, or defaulting to Booking Date.
        sent_date = creation_date if creation_date else booking_date
        add_event(psp_ref, 'Payment Sent for Settlement', sent_date, row_attrs)

    elif journal_type == 'Refunded':
        add_event(psp_ref, 'Refund Initiated', creation_date, row_attrs)
        add_event(psp_ref, 'Refund Settled', booking_date, row_attrs)

    elif journal_type == 'Chargeback':
        add_event(psp_ref, 'Chargeback Notification Received', booking_date, row_attrs)

    elif journal_type == 'ChargebackRetried':
        add_event(psp_ref, 'Chargeback Defended', booking_date, {'IsRework': 'True'})

    elif journal_type == 'ChargebackReversed':
        add_event(psp_ref, 'Chargeback Reversed', booking_date, row_attrs)

    elif journal_type == 'PaidOut':
        # Payouts often group many transactions. 
        # If the report is at transaction level, this row represents the batch payout.
        add_event(psp_ref, 'Payout Confirmed', booking_date, row_attrs)

    elif journal_type == 'CaptureFailed':
        add_event(psp_ref, 'Capture Failed', booking_date, {'IsRework': 'True'})

    # --- 3. EXCEPTION HANDLING ---
    # These statuses often appear in 'Received payment details' reports but rarely in Settlement
    # unless fees were applied.
    
    elif journal_type == 'Refused': 
        add_event(psp_ref, 'Payment Refused', creation_date, row_attrs)
        
    elif journal_type == 'Cancelled':
        add_event(psp_ref, 'Payment Cancelled', creation_date, row_attrs)

    elif journal_type == 'Error':
        add_event(psp_ref, 'Technical Error Logged', booking_date, {'IsRework': 'True'})

# Convert to DataFrame
events_df = pd.DataFrame(event_log)

# Deduping: Adyen reports may have multiple lines for partial settlements.
# We sort by date and keep unique Activity per PSP Reference if timestamps match exactly.
events_df.drop_duplicates(subset=['PspReference', 'EventCode', 'EventDate'], inplace=True)

# Output
events_df.to_csv(OUTPUT_FILE, index=False)
print(f'Successfully extracted {len(events_df)} events to {OUTPUT_FILE}')

Steps

Prerequisite Configuration: Ensure you have an Adyen Report user with the Merchant Report role enabled. Obtain your API Key from the Customer Area under Developers > API Credentials.
Identify Required Reports: This extraction relies on two key CSV reports generated by Adyen: the Settlement Detail Report (for financial events like Settlement, Chargebacks, Refunds) and the Received Payment Detail Report (for operational events like Requests, Refusals, Authorizations).
Python Environment Setup: Install the necessary libraries using pip: pandas, requests, and numpy. These will be used for API communication and data transformation.
API Connection Implementation: Configure the Python script (provided below) to authenticate against the https://management-test.adyen.com or https://management-live.adyen.com endpoints. You will use the Report API to list available reports for your specific date range and download the URLs.
Data Ingestion: The script reads the raw CSV data into pandas DataFrames. Adyen reports are typically 'wide' (one row per transaction with multiple status columns), so transformation is required.
Activity Mapping - Operational: Process the Received Payment Detail Report. Map the CreationDate to Payment Request Received. Use logic to inspect the Status column (e.g., Authorised, Refused, Error) to generate Payment Authorised, Payment Refused, or Technical Error Logged events.
Activity Mapping - Financial: Process the Settlement Detail Report. This report contains a JournalType column. Map values like Settled to Payment Settled, Refunded to Refund Initiated, and Chargeback to Chargeback Notification Received.
Inferring Complex Activities:
- Risk Screening Performed: Check if the FraudScore column is populated and greater than -1.
- Payout Confirmed: Link transactions via the BatchNumber to the Payout entry in the settlement report.
- Chargeback Defended: Look for SecondChargeback or Defense journal types.
Data Transformation: Apply a 'melt' or 'stack' operation in pandas to convert the wide dataset into a long event log format where every activity is a separate row.
Attribute Standardization: Rename columns to match the target schema: PspReference, EventCode, EventDate, SourceSystem (hardcoded to 'Adyen'), and PaymentAmount. Ensure dates are parsed to ISO 8601 format.
Filtering: Filter out internal reconciliation rows that do not represent process steps (e.g., header rows or balance carry-overs) using the Type filter.
Final Export: The script exports the processed DataFrame to a CSV file named adyen_event_log.csv, ready for upload to ProcessMind.

Configuration

API Environment: Switch between Adyen Test (management-test.adyen.com) and Live (management-live.adyen.com) endpoints based on the deployment phase.
Authentication: Use x-api-key in the header. Do not use Basic Auth for the Management API.
Report Types:
- settlement_detail_report: Critical for financial lifecycle events.
- received_payment_detail_report: Critical for initial request and authorization logic.
Date Range: Adyen reports are generated based on batch closure. Ensure the script requests reports covering the CreationDate of interest + 7 days to capture delayed settlements.
Merchant Account Scope: If you have multiple merchant accounts, iterate through the list of accounts or use the Company Account level report if available.
Pandas Configuration: Ensure low_memory=False is set when reading CSVs if transaction volume exceeds 100k rows to prevent type inference errors.

a Sample Query python

import pandas as pd
import requests
import io
import numpy as np
from datetime import datetime

class=class="hl-string">"hl-comment"># Configuration
API_KEY = class="hl-string">'YOUR_ADYEN_API_KEY'
MERCHANT_ACCOUNT = class="hl-string">'YOUR_MERCHANT_ACCOUNT'
BASE_URL = class="hl-string">'https://management-live.adyen.com/v1'
HEADERS = {class="hl-string">'x-api-key': API_KEY, class="hl-string">'Content-Type': class="hl-string">'application/json'}

class=class="hl-string">"hl-comment"># Placeholder for fetching report URLs via API
class=class="hl-string">"hl-comment"># In production, use GET /companies/{companyId}/reports or /merchants/{merchantId}/reports
class=class="hl-string">"hl-comment"># For this script, we assume the CSV content is loaded into DataFrames

def transform_adyen_data(received_payments_csv_path, settlement_details_csv_path):
    
    class=class="hl-string">"hl-comment"># 1. Load Data
    print(class="hl-string">'Loading reports...')
    df_received = pd.read_csv(received_payments_csv_path)
    df_settled = pd.read_csv(settlement_details_csv_path)

    events = []

    class=class="hl-string">"hl-comment"># 2. Process Received Payment Detail Report (Operational Events)
    class=class="hl-string">"hl-comment"># This report covers: Request, Auth, Refusal, Risk, Capture, Errors
    
    for _, row in df_received.iterrows():
        psp = str(row.get(class="hl-string">'PspReference', class="hl-string">''))
        created_date = pd.to_datetime(row.get(class="hl-string">'CreationDate'))
        amount = row.get(class="hl-string">'Amount', 0)
        status = row.get(class="hl-string">'Status', class="hl-string">'')
        fraud_score = row.get(class="hl-string">'FraudScore', None)
        refusal_reason = row.get(class="hl-string">'RefusalReason', class="hl-string">'')
        
        class=class="hl-string">"hl-comment"># Activity: Payment Request Received
        events.append({
            class="hl-string">'PspReference': psp,
            class="hl-string">'EventCode': class="hl-string">'Payment Request Received',
            class="hl-string">'EventDate': created_date,
            class="hl-string">'PaymentAmount': amount,
            class="hl-string">'PaymentMethod': row.get(class="hl-string">'PaymentMethod', class="hl-string">''),
            class="hl-string">'RefusalReason': None,
            class="hl-string">'SourceSystem': class="hl-string">'Adyen'
        })

        class=class="hl-string">"hl-comment"># Activity: Risk Screening Performed
        class=class="hl-string">"hl-comment"># Inferred if a fraud score was calculated
        if pd.notna(fraud_score):
            events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': class="hl-string">'Risk Screening Performed',
                class="hl-string">'EventDate': created_date + pd.Timedelta(seconds=1), class=class="hl-string">"hl-comment"># Slight offset
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'SourceSystem': class="hl-string">'Adyen'
            })

        class=class="hl-string">"hl-comment"># Activity: Payment Authorised / Refused / Error
        if status == class="hl-string">'Authorised':
            events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': class="hl-string">'Payment Authorised',
                class="hl-string">'EventDate': created_date + pd.Timedelta(seconds=2),
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'SourceSystem': class="hl-string">'Adyen'
            })
        elif status == class="hl-string">'Refused':
            events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': class="hl-string">'Payment Refused',
                class="hl-string">'EventDate': created_date + pd.Timedelta(seconds=2),
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'RefusalReason': refusal_reason,
                class="hl-string">'SourceSystem': class="hl-string">'Adyen'
            })
        elif status == class="hl-string">'Error':
            events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': class="hl-string">'Technical Error Logged',
                class="hl-string">'EventDate': created_date + pd.Timedelta(seconds=2),
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'RefusalReason': row.get(class="hl-string">'AcquirerResponse', class="hl-string">'Technical Error'),
                class="hl-string">'SourceSystem': class="hl-string">'Adyen'
            })
        elif status == class="hl-string">'Cancelled':
            events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': class="hl-string">'Payment Cancelled',
                class="hl-string">'EventDate': created_date + pd.Timedelta(seconds=5),
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'SourceSystem': class="hl-string">'Adyen'
            })

    class=class="hl-string">"hl-comment"># 3. Process Settlement Detail Report (Financial Events)
    class=class="hl-string">"hl-comment"># This report covers: Capture, Settlement, Refunds, Chargebacks, Payouts
    
    for _, row in df_settled.iterrows():
        psp = str(row.get(class="hl-string">'PspReference', class="hl-string">''))
        journal_type = row.get(class="hl-string">'JournalType', class="hl-string">'')
        process_date = pd.to_datetime(row.get(class="hl-string">'CreationDate')) class=class="hl-string">"hl-comment"># Or ProcessingDate
        amount = row.get(class="hl-string">'NetCredit', 0) if pd.notna(row.get(class="hl-string">'NetCredit')) else row.get(class="hl-string">'GrossCredit', 0)
        
        class=class="hl-string">"hl-comment"># Map JournalType to Activities
        activity_name = None
        
        if journal_type == class="hl-string">'SentForSettlement':
            activity_name = class="hl-string">'Payment Sent for Settlement'
        elif journal_type == class="hl-string">'Settled':
            activity_name = class="hl-string">'Payment Settled'
        elif journal_type == class="hl-string">'SentForRefund' or journal_type == class="hl-string">'Refunded':
            activity_name = class="hl-string">'Refund Initiated'
        elif journal_type == class="hl-string">'SettledRefund':
            activity_name = class="hl-string">'Refund Settled'
        elif journal_type == class="hl-string">'Chargeback':
            activity_name = class="hl-string">'Chargeback Notification Received'
        elif journal_type == class="hl-string">'SecondChargeback' or journal_type == class="hl-string">'Defense':
            activity_name = class="hl-string">'Chargeback Defended'
        elif journal_type == class="hl-string">'ChargebackReversed':
            activity_name = class="hl-string">'Chargeback Reversed'
        elif journal_type == class="hl-string">'CaptureFailed':
            activity_name = class="hl-string">'Capture Failed'
        elif journal_type == class="hl-string">'PaidOut':
            class=class="hl-string">"hl-comment"># PaidOut is usually batch level, if psp is present, map it
            activity_name = class="hl-string">'Payout Confirmed'
        
        class=class="hl-string">"hl-comment"># Logic for class="hl-string">'Payment Captured' 
        class=class="hl-string">"hl-comment"># Adyen often auto-captures. If we see Settled, we assume Captured occurred prior if not explicitly logged.
        class=class="hl-string">"hl-comment"># Here we rely on class="hl-string">'SentForSettlement' as the trigger for Capture success in many flows.
        if journal_type == class="hl-string">'SentForSettlement':
             events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': class="hl-string">'Payment Captured',
                class="hl-string">'EventDate': process_date - pd.Timedelta(seconds=1),
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'SourceSystem': class="hl-string">'Adyen'
            })

        if activity_name:
            events.append({
                class="hl-string">'PspReference': psp,
                class="hl-string">'EventCode': activity_name,
                class="hl-string">'EventDate': process_date,
                class="hl-string">'PaymentAmount': amount,
                class="hl-string">'SourceSystem': class="hl-string">'Adyen',
                class="hl-string">'MerchantAccount': row.get(class="hl-string">'MerchantAccount', MERCHANT_ACCOUNT),
                class="hl-string">'PaymentMethod': row.get(class="hl-string">'PaymentMethod', class="hl-string">'')
            })

    class=class="hl-string">"hl-comment"># 4. Create DataFrame
    df_events = pd.DataFrame(events)
    
    class=class="hl-string">"hl-comment"># 5. Post-Processing & Cleanup
    if not df_events.empty:
        class=class="hl-string">"hl-comment"># Ensure standard columns
        df_events[class="hl-string">'LastDataUpdate'] = datetime.now().isoformat()
        df_events[class="hl-string">'TotalCycleTime'] = None class=class="hl-string">"hl-comment"># Calculated in ProcessMind
        df_events[class="hl-string">'IsRework'] = df_events[class="hl-string">'EventCode'].apply(lambda x: 1 if class="hl-string">'Chargeback' in x or class="hl-string">'Refused' in x else 0)
        df_events[class="hl-string">'PaymentStatus'] = df_events.sort_values(class="hl-string">'EventDate').groupby(class="hl-string">'PspReference')[class="hl-string">'EventCode'].transform(class="hl-string">'last')
        
        class=class="hl-string">"hl-comment"># Filter invalid rows (empty PspReference)
        df_events = df_events[df_events[class="hl-string">'PspReference'] != class="hl-string">'nan']
        df_events = df_events[df_events[class="hl-string">'PspReference'] != class="hl-string">'']

        class=class="hl-string">"hl-comment"># Sort
        df_events = df_events.sort_values([class="hl-string">'PspReference', class="hl-string">'EventDate'])
        
    return df_events

class=class="hl-string">"hl-comment"># Execution Entry Point
class=class="hl-string">"hl-comment"># Replace paths with actual file locations or API download streams
if __name__ == class="hl-string">'__main__':
    class=class="hl-string">"hl-comment"># Example usage
    df_log = transform_adyen_data(class="hl-string">'received_payment_detail_report.csv', class="hl-string">'settlement_detail_report.csv')
    
    class=class="hl-string">"hl-comment"># Export
    df_log.to_csv(class="hl-string">'ProcessMind_Adyen_Log.csv', index=False, date_format=class="hl-string">'%Y-%m-%d %H:%M:%S')
    print(fclass="hl-string">'Extraction Complete. Generated {len(df_log)} events.')

Your Payments Processing Data Template

Your Payments Processing Data Template

Payments Processing Attributes

Payments Processing Activities

Extraction Guides

Adyen Settlement Detail Report Export

Steps

Configuration

a Sample Query config

Python Extraction via Reporting API

Steps

Configuration

a Sample Query python

Ready to Get Started?

Unlock Seamless Payments Processing in Adyen Today.

Your Payments Processing Data Template

Your Payments Processing Data Template

Payments Processing Attributes

Payments Processing Activities

Extraction Guides

Adyen Settlement Detail Report Export

Steps

Configuration

a Sample Query config

Python Extraction via Reporting API

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Unlock Seamless Payments Processing in Adyen Today.