> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paymend.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transactions attempted

> All transaction attempts processed during the period, including declines.

One row per transaction attempt. Unlike [transactions succeeded](https://docs.paymend.com/reporting/transactions_succeeded.md),
this report also includes failed and declined attempts.

```
report_transactions_attempted-{merchant_name}-{period_start}_to_{period_end}.csv
```

Bounded on `event_processed_at`.

## Columns

| Column | Type | Description |
| - | - | - |
| `event_id` | string | Unique identifier for this transaction event. Joins to the settlement report when the attempt succeeded. |
| `event_processed_at` | timestamp | When the attempt was processed. UTC. |
| `event_type` | enum | `AUTH`, `CAPTURE`, `SALE`, `REFUND`, `VALIDATE` or `VOID`. |
| `event_status` | enum | Terminal status of the attempt. Values include `AUTHORIZED`, `CAPTURED`, `REFUNDED`, `VALIDATED`, `VOIDED` and `FAILED`. |
| `payment_id` | string | The payment this transaction belongs to. Matches `event_id` in the payments created report. |
| `merchant_name` | string | Your merchant identifier. |
| `store_id` | string | Store the payment belongs to, or `NA` where not configured. |
| `merchant_reference` | string | Your own reference from the payment request. |
| `authorization_code` | string | Authorization code returned by the issuer. Empty if not available. |
| `acquirer_reference_number` | string | ARN assigned by the acquirer. Empty if not available. |
| `event_amount` | decimal | Amount in major units, always positive. See the sign note below. |
| `currency` | enum | ISO 4217 currency. Values: `USD`. |
| `descriptor` | string | Billing descriptor presented to the consumer. |
| `consumer_first_name` | string | Consumer given name. |
| `consumer_last_name` | string | Consumer family name. |
| `consumer_email` | string | Consumer email address. |
| `card_brand` | enum | `MASTERCARD`, `VISA`, `AMEX`, `DISCOVER`, `JCB`, `DINERS`. |
| `card_bin` | string | First 6-8 digits of the card number. |
| `card_last_4_digits` | string | Last four digits of the card number. |
| `failure_code` | enum | Paymend [failure code](https://docs.paymend.com/api-reference/failure-codes.md) when the attempt failed. Empty when the attempt succeeded. |
| `failure_type` | enum | Classification of the failure (for example `SOFT`, `HARD` or `ROUTING_ERROR`). Empty when the attempt succeeded. |

> [!NOTE]
>
> `event_amount` is unsigned in this report — a refund of 97.00 appears as
> `97.00`, not `-97.00`. Use `event_type` to determine direction. The settlement
> report signs the same amount negative, because there the column feeds an
> arithmetic total.

> [!NOTE]
>
> Failed attempts (`event_status` = `FAILED`) do not appear in settlement. Only
> successful attempts join to [settlement paid out](https://docs.paymend.com/reporting/settlement_paid_out.md)
> on `event_id`.

## Refunds

Refunds need care, because two different identifiers are in play.

* `payment_id` is the **original payment** being refunded, prefixed `PAYM_`. It
  is the same value that appears on the corresponding `SALE` or `CAPTURE` row.
* `event_id` identifies the **refund itself**, prefixed `REFN_`.

> [!WARNING]
>
> Do not join refunds to sales on `payment_id` alone and assume a one-to-one
> result. A single payment can be refunded more than once, and both refund rows
> will carry the same `payment_id`. Always carry `event_id` through as the row
> identity.

The prefix tells you what a row is without reading `event_type`, but it is not a
substitute for it — match on `event_type` in your logic and treat the identifier
itself as opaque.

## Example

```csv report_transactions_attempted-my_merchant-20261001_to_20261031.csv theme={null}
event_id,event_processed_at,event_type,event_status,payment_id,merchant_name,store_id,merchant_reference,authorization_code,acquirer_reference_number,event_amount,currency,descriptor,consumer_first_name,consumer_last_name,consumer_email,card_brand,card_bin,card_last_4_digits,failure_code,failure_type
REFN_n3CMMmdk7L,2026-10-25 14:20:25.138982 UTC,REFUND,REFUNDED,PAYM_L14MTs4n5H,my_merchant,store_abc,ORD-88213,025939,,97.00,USD,8005550111acmewell,Teresia,Jamtgaard,t.jamtgaard@example.com,MASTERCARD,55243336,0789,,
SALE_P9SIEMpl09,2026-10-25 11:47:22.027755 UTC,SALE,FAILED,PAYM_uuZKvX0okL,my_merchant,store_abc,ORD-88214,,,97.00,USD,,Paul,Sherer,p.sherer@example.com,VISA,44924959,1126,INSUFFICIENT_FUNDS,SOFT
SALE_ygOxVurxn42,2026-10-25 11:24:55.608751 UTC,SALE,FAILED,PAYM_dkoJ2G3e4G,my_merchant,store_abc,ORD-88215,,,97.00,USD,,Lance,Paris,l.paris@example.com,MASTERCARD,54642700,9888,CARD_BLOCKED,HARD
SALE_Kv8dRnpp77,2026-10-25 11:49:03 UTC,SALE,CAPTURED,PAYM_Nc9wTd009i,my_merchant,store_123,ORD-88216,90210B,74921500219000012345679,129.50,USD,8005550111acmewell,Tomas,Lindqvist,t.lindqvist@example.com,MASTERCARD,555555,8081,,
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.