Single Transaction Report
Single Transaction Report Sample
The Single Transaction Report is a comprehensive daily transactional report that provides detailed information about all payment activities for a merchant during a specific period. The report is delivered in CSV or XLSX format and contains multiple tabs, each dedicated to a specific transaction type.
Summary
This summary tab provides an aggregated overview of all transaction types during the report period, displaying total amounts for payments, refunds, chargebacks, and chargeback reversals. The summary calculates net amounts by transaction type (LOCAL, XB, MIXED, or FULL_LOCAL) and shows the overall financial impact for the period. Each row in the summary represents a different transaction classification, with columns showing payment totals, refund totals, chargeback totals, reversal totals, and the net total amount.
| Field | Format | Description | Example | Edge Cases |
|---|---|---|---|---|
| PAYMENT | Decimal number with 2 decimal places | Aggregated sum of all payment transaction net amounts (charge amount minus fees). Sum of (charge_amount - fee_amount) for all entries where entry_type_group is PAYMENT or ACCELERATION. | 1497.90, 5.40 | Includes both local and cross-border payments; zero if no payments in period. |
| REFUND | Decimal number with 2 decimal places (positive value) | Aggregated sum of all refund transaction amounts (displayed as positive, deducted from TOTAL). Sum of (charge_amount + fee_amount) for all entries where entry_type_group is REFUND. | 1505.20, 4.40 | Value is subtracted from TOTAL despite being positive; zero if no refunds in period. |
| CHARGEBACK | Decimal number with 2 decimal places (positive value) | Aggregated sum of all chargeback transaction amounts (displayed as positive, deducted from TOTAL). Sum of (charge_amount + fee_amount) for all entries where entry_type_group is CHARGEBACK. | 2.20, 4.40, 0.00 | Value is subtracted from TOTAL despite being positive; zero if no chargebacks in period. |
| CHARGEBACK REVERSAL | Decimal number with 2 decimal places (positive value) | Aggregated sum of all chargeback reversal amounts (added back to TOTAL). Sum of (charge_amount - fee_amount) for all entries where entry_type_group is REVERSAL. | 1.80, 3.60, 0.00 | Value is added to TOTAL; zero if no reversals in period. |
| ADJUSTMENTS | Decimal number with 2 decimal places (can be +/-) | Sum of manual settlement adjustments applied to the reporting period (optional field). Sum of adjustment_amount from adjustments table for the reporting period. | 0.00, 1.00 | Only included if configured; can be negative for deductions. |
| TOTAL | Decimal number with 2 decimal places (can be +/-) | Net sum of all transaction types (PAYMENT - REFUND - CHARGEBACK + REVERSAL + ADJUSTMENTS). PAYMENT + REVERSAL + ADJUSTMENTS - REFUND - CHARGEBACK | -7.70, 0.20 | Can be negative if refunds/chargebacks exceed payments; represents cash flow impact. |
| TYPE | String enumeration (FULL_LOCAL, MIXED, XB, LOCAL) | Classification of transaction flow type based on recipient code and payment routing. Determined by recipient_code field: ME = FULL_LOCAL, ebanx-xb = XB, combination = MIXED. | FULL_LOCAL, MIXED, XB | LOCAL is used for specific aggregations; MIXED indicates split flows. |
Payments
This tab contains all payment transactions processed during the report period, including both credit card payments and PIX instant payments. Each payment entry displays the deposited date, open date, confirmed date, payment code, order number, payment type and method, currency, charge amount, processing fees, net amount, payment hash, customer information, installment details, total amount, recipient code, and transaction type classification. For credit card transactions, the report includes card details such as BIN and masked card numbers. When installment grouping is enabled, multiple installments with the same payment hash are consolidated into a single row showing aggregated amounts.
| Field | Format | Description | Example | Edge Cases |
|---|---|---|---|---|
| DEPOSITED DATE | Date string (YYYY-MM-DD) | Date when the transaction was deposited/settled in system. | 2022-05-20 | Always populated for settled transactions; represents effective settlement date |
| OPEN DATE | DateTime string (YYYY-MM-DD HH:MM:SS) | Date and time when the transaction was initially created. | 2022-04-15 16:40:01 | Never null; always populated at transaction creation |
| CONFIRMED DATE | DateTime string (YYYY-MM-DD HH:MM:SS) | Date and time when the transaction was confirmed/completed. | 2022-04-20 15:40:01 | Null for non-confirmed transactions |
| PMT CODE | String (merchant-defined) | Merchant-provided payment code identifier. | INV-MERCHANT-CODE-001 | Can be null if merchant doesn't provide it |
| ORDER NUMBER | String (optional) | Order reference number from merchant's e-commerce system. | PAYMENT-CODE-001 | Can be null; multiple transactions can share same order number |
| PMT TYPE | String (payment type group code) | Payment type group code (e.g., creditcard, cash). | creditcard, cash, ewallet | Always populated for valid payment types |
| PMT METHOD | String (payment method code) | Specific payment method code (e.g., visa, boleto, pix). | visa, mastercard, pix, boleto | Always populated; determines available features |
| CURRENCY | 3-letter ISO 4217 currency code | Transaction currency code. | BRL, USD, MXN | Always populated; matches country's primary currency for local transactions |
| CHARGE AMOUNT | Decimal number with 2 decimal places | Transaction amount (positive for payments, negative for refunds/chargebacks). | 2.00, -50.00 (negative for refunds) | Sign indicates transaction direction; zero-decimal currencies have no decimal places |
| PROCESSING FEE | Decimal number with 2 decimal places | Processing fee charged for the transaction. | 0.20 | Can be 0.00 for fee-free transactions; includes all fee components |
| NET | Decimal number with 2 decimal places | Net amount after fees (charge_amount - fee_amount for payments, charge_amount + fee_amount for refunds). For payments: charge_amount - fee_amount; For refunds/chargebacks: charge_amount + fee_amount. | 1.80, 2.20 | Calculation logic differs by transaction type |
| HASH | Hexadecimal string (48 characters) | Unique EBANX payment hash identifier. Generated at payment creation. | 54154bb...4e444a4ac | Always populated and unique; immutable after creation |
| CUSTOMER NAME | String (UTF-8 encoded) | Full name of the customer. Retrieved from customer.name; may be masked if mask_customer_data config is enabled. | CUSTOMER MOCKED, ********** | Can be masked with asterisks if merchant has data masking enabled |
| CUSTOMER DOCUMENT | String (document format varies by country) | Customer's government-issued document number. | 05444444927, ********** | Can be masked; format varies by country |
| INSTALMENT | Integer | Current instalment number (for instalment payments). | 1 | Always at least 1; represents current instalment in sequence |
| TOTAL INSTALMENTS | Integer | Total number of instalments for the payment. | 1, 3, 12 | Always at least 1; maximum varies by country |
| TOTAL AMOUNT | Decimal number with 2 decimal places | Total payment amount (for instalment context). | 2.00, 4.00 | Represents full payment amount regardless of instalment |
| RECIPIENT CODE | String | Code identifying the recipient of the transaction. | ME, ebanx-xb | Can be filtered out if merchant has shouldNotPrintXBRecipient config enabled |
| SINGLE TRANSACTION | String enumeration | Transaction type classification (FULL_LOCAL, MIXED, XB). Determined by recipient code and transaction flow. | FULL_LOCAL, MIXED, XB | MIXED indicates split between local and cross-border; XB is pure cross-border |
Payment-Specific Fields
| Field | Format | Description | Example | Edge Cases |
|---|---|---|---|---|
| REFUND CODE | String (empty for payments) | Merchant-provided refund code (empty for payments). Empty string for payment rows. | `` (empty) | Only populated for refund rows |
Optional Fields
| Field | Format | Description | Example | Edge Cases |
|---|---|---|---|---|
| ENTRY TYPE | String | Transaction type label (payment, refund, chargeback, reversal). Mapped from transaction entity type. | payment, refund, chargeback | Only included if print_entry_type optional field is configured |
| CHARGED FROM MARKETPLACE | String ("YES" or "NO") | Indicates if transaction was charged from marketplace balance. | YES, NO | Only included if charged_from_marketplace optional field is configured |
Example Single Transaction Calculation
Scenario: Brazilian merchant with mixed local and cross-border transactions
Base Data
Report Date: May 20, 2022
Merchant: EBANX Demo Merchant
Currency: BRL
Transaction Breakdown
Payments:
Local Payment: BRL 2.00 (charge) - BRL 0.20 (fee) = BRL 1.80 (net)
XB Payment: BRL 4.00 (charge) - BRL 0.40 (fee) = BRL 3.60 (net)
Refunds:
Local Refund: BRL -2.00 (charge) + BRL 0.20 (fee) = BRL -1.80 (net)
XB Refund: BRL -2.00 (charge) + BRL 0.20 (fee) = BRL -1.80 (net)
Chargebacks:
Local Chargeback: BRL -2.00
Still need help?
We hope this article was helpful. If you still have questions, you can explore the following options:
- Merchant support: Contact our support team at sales.engineering@ebanx.com for assistance.
- Not a partner yet? Please complete the Merchant Signup Form, and our commercial team will reach out to you.