Skip to main content
CARD_TRANSACTION_FEES itemises what Reap billed you for that arose from card use: purchases, ATM withdrawals, refunds, wallet provisioning, and 3DS authentication. Request it as described on the statements overview.

What a row is

A row is one fee event, not one transaction. A single transaction produces several rows when it is authorized, captured in parts, refunded, or later corrected. Join them on transactionId. Some rows carry no transaction at all, because the fee is priced per occurrence: provisioning a card into Apple Pay or Google Pay, and non-financial ATM actions such as a PIN change or a balance enquiry. Those rows leave the event columns empty, and feeType says what happened. Their transaction amount columns read zero, which is their real value rather than a placeholder, and the fee Reap charged for the occurrence is in its fee column. A TRANSACTION row with no eventId is a zero-value authorization: a merchant checking that the card is valid, for example when it is saved for later payments. The network charges for the check, but no money moves, so it raises no card transaction event. The card and merchant columns identify it. Every row has an id that stays the same in every statement that includes it. Use it to tell a row you have already imported from a new one when you request an overlapping period, since rows with no eventId have nothing else unique to match on.

Adjustments

An ADJUSTMENT row corrects a fee assessed on an earlier transaction, and they are extremely rare. The original row is never rewritten. The adjustment records the difference instead, and carries the transactionId of the transaction it corrects. Its occurredAt is when the correction was issued, and its event columns are empty.

Signs

Amounts follow the cardholder’s money. Spend is positive, refunds and reversals are negative, so summing a column over a period gives you a net figure with no sign handling of your own. Fees you collected and interchange you earned are signed from your point of view: positive, and negative where they were given back. The fees Reap charged you are positive as charged, and negative only where one was credited back to you. ADJUSTMENT rows are corrections issued against a fee assessed earlier, and they carry whichever sign undoes the original. Include them in every total.

Currencies

Two denominations coexist in one file. currency is your card program currency, and governs amount, billAmount, originalAmount, fxFee, atmVariableFee, and atmFixedFee. Columns whose names end in Usd are US dollars on every program, whatever your program currency. billAmountUsd is billAmount converted at the rate for the day the transaction happened.

Amounts

Three amount columns describe the same transaction from different angles:
  • billAmount is the transaction before the fees you applied.
  • amount is what the cardholder was charged, so it equals billAmount plus fxFee, atmVariableFee, and atmFixedFee. It matches what the transactions API returns.
  • billAmountUsd is billAmount in US dollars.
The difference between amount and billAmount is exactly the fees you collected from your cardholder.

Fees Reap charged you

The columns from authorizationFeeUsd to atmNonFinancialFeeUsd, and digitalCommerceServiceFeeUsd, carry what Reap charged you on each row, in US dollars. A fee that your pricing does not charge separately reads zero. Each fee sits on the row for the network message it was assessed on:
  • authorizationFeeUsd, digitalCommerceServiceFeeUsd, fraudMonitoringFeeUsd and threeDsFeeUsd are on authorization-side rows: AUTHORIZATION, and the REVERSAL or DECLINE that follows it. The share of tokenFeeUsd charged for authorizing with a wallet token is on the AUTHORIZATION row.
  • settlementFixedFeeUsd, settlementVariableFeeUsd, applePayFeeUsd and interchange are on clearing-side rows: CLEARING and REFUND.
  • Provisioning a card into a wallet and non-financial ATM actions have rows of their own, as described in What a row is.
applePayFeeUsd is charged per Apple Pay transaction. The monthly fee for each card added to Apple Pay is not tied to a transaction, so it is not in this statement. A 3DS authentication is charged on the authorization the cardholder authenticated, not on a row of its own. That row’s feeType is 3DS_FRICTIONLESS, 3DS_SMS or 3DS_FORWARDING, unless a more specific category applies: a 3DS authorization made with Apple Pay reads TOKEN_TXN_APPLE_PAY. Count 3DS charges by summing threeDsFeeUsd, not by counting feeType values.

Interchange

Interchange is reported in full, as earned on the transaction. grossInterchangeUsd is before scheme deductions and netInterchangeUsd is after them. On a small transaction the scheme fees can exceed the gross figure, so netInterchangeUsd can be negative on a purchase. Neither is your share of it: the share is a percentage set out in your pricing schedule, which the file does not carry.

Scale and ordering

Card-currency columns carry two decimal places. Usd columns carry seven, which is the scale Reap computes and bills at, so round once at the end rather than per row. Rows are ordered by occurredAt, oldest first. See the file format for the dialect every statement shares.

Columns

Every column is listed below, in file order. Request a subset with fields and you get exactly these names, in the order you asked for.

One row of a CARD_TRANSACTION_FEES file, in file order. Every value is a CSV field; a column that is not required may be empty.

id
string<uuid>
required

Identifier of this row. It stays the same in every statement that includes the row, so use it to tell a row you have already seen from a new one, including rows with no eventId.

Example:

"01a0c3e2-5b7d-4f19-8e2a-6c4d8b1f3a01"

occurredAt
string<date-time>
required

When the network event occurred, UTC. Statement periods are bucketed on this column. On an ADJUSTMENT row it is when the correction was issued.

Example:

"2026-09-01T09:00:00.000Z"

feeType
enum<string>
required

Fee category the row was assessed under, and what explains a row with no transaction event. A row takes the single most specific category that applies: a wallet or other token over 3DS, and 3DS over an ATM action. Total a fee from its fee column rather than by counting a category.

  • TRANSACTION: A card transaction no more specific category applies to: a purchase, refund or other card use made without a wallet or other token, 3DS authentication or an ATM
  • ATM_WITHDRAWAL: A cash withdrawal at an ATM
  • ATM_PIN_CHANGE: A PIN change at an ATM. Carries no transaction; the fee is in atmNonFinancialFeeUsd
  • ATM_BALANCE_ENQUIRY: A balance enquiry at an ATM. Carries no transaction; the fee is in atmNonFinancialFeeUsd
  • TOKEN_PROVISIONING: A card added to a wallet such as Apple Pay or Google Pay. Carries no transaction; the fee is in tokenFeeUsd
  • TOKEN_TXN: A transaction made with a token other than Apple Pay or Google Pay, for example Samsung Pay or a card a merchant saved for later payments
  • TOKEN_TXN_APPLE_PAY: A transaction made with Apple Pay
  • TOKEN_TXN_GOOGLE_PAY: A transaction made with Google Pay
  • 3DS_FRICTIONLESS: An authorization that passed 3DS without challenging the cardholder
  • 3DS_SMS: An authorization where the cardholder completed 3DS with a one-time code sent by SMS
  • 3DS_FORWARDING: An authorization where the cardholder completed 3DS in their banking app
  • ADJUSTMENT: A correction to a fee assessed on an earlier transaction. Include it in every total
Available options:
TRANSACTION,
ATM_WITHDRAWAL,
ATM_PIN_CHANGE,
ATM_BALANCE_ENQUIRY,
TOKEN_PROVISIONING,
TOKEN_TXN,
TOKEN_TXN_APPLE_PAY,
TOKEN_TXN_GOOGLE_PAY,
3DS_FRICTIONLESS,
3DS_SMS,
3DS_FORWARDING,
ADJUSTMENT
Example:

"TRANSACTION"

locality
enum<string>
required

Whether the merchant sits in your card program market. The international transaction fee and the ATM rates split on this column.

Available options:
DOMESTIC,
CROSS_BORDER
Example:

"CROSS_BORDER"

hasFx
enum<string>
required

Whether the transaction involved a currency conversion. The FX fee line sums the volume of these rows.

Available options:
true,
false
Example:

"true"

currency
string
required

Currency of amount, billAmount, fxFee, atmVariableFee and atmFixedFee: your card program currency, as an ISO 4217 alphabetic code.

Example:

"HKD"

amount
string
required

What the cardholder was charged, in the card currency. Equals billAmount plus fxFee, atmVariableFee and atmFixedFee, and matches the transaction amount the API returns. Zero on a row that carries a fee but no transaction.

Decimal with 2 decimal places.

Example:

"201.30"

billAmount
string
required

Transaction amount before the fees you applied, in the card currency. The difference between this and amount is exactly the fees you collected.

Decimal with 2 decimal places.

Example:

"200.75"

billAmountUsd
string
required

billAmount - not amount - converted to US dollars at the transaction-day rate. Every percentage line on your invoice is computed on this column, whatever your card program currency.

Decimal with 7 decimal places.

Example:

"25.7364198"

fxFee
string
required

Foreign exchange fee you collected from the cardholder, in the card currency.

Decimal with 2 decimal places.

Example:

"0.55"

atmVariableFee
string
required

Percentage-based ATM fee you collected from the cardholder, in the card currency.

Decimal with 2 decimal places.

Example:

"0.00"

atmFixedFee
string
required

Per-withdrawal ATM fee you collected from the cardholder, in the card currency.

Decimal with 2 decimal places.

Example:

"0.00"

authorizationFeeUsd
string
required

Authorization fee Reap charged you on this row, in US dollars. Where your pricing includes 3DS, fraud monitoring or tokenization in the authorization fee, it is included here and those columns read zero. The digital commerce service fee is never included: it has its own column.

Decimal with 7 decimal places.

Example:

"0.0000000"

settlementFixedFeeUsd
string
required

Per-settlement fee Reap charged you on this row, in US dollars.

Decimal with 7 decimal places.

Example:

"0.1200000"

settlementVariableFeeUsd
string
required

Percentage-based settlement fee Reap charged you on this row, in US dollars, computed on billAmountUsd. Where your pricing has an international transaction fee, this is that fee, and it is charged on cross-border settlements only.

Decimal with 7 decimal places.

Example:

"0.2573642"

threeDsFeeUsd
string
required

3DS authentication fee Reap charged you on this row, in US dollars. Charged on the authorization the cardholder authenticated, whatever its feeType.

Decimal with 7 decimal places.

Example:

"0.0000000"

fraudMonitoringFeeUsd
string
required

Fraud monitoring fee Reap charged you on this row, in US dollars.

Decimal with 7 decimal places.

Example:

"0.0000000"

tokenFeeUsd
string
required

Tokenization fee Reap charged you on this row, in US dollars: provisioning a card into a wallet, and authorizing with a wallet token.

Decimal with 7 decimal places.

Example:

"0.0000000"

applePayFeeUsd
string
required

Apple Pay fee Reap charged you on this row, in US dollars.

Decimal with 7 decimal places.

Example:

"0.0000000"

atmNonFinancialFeeUsd
string
required

Fee Reap charged you for an ATM non-financial action such as a PIN change or a balance enquiry, in US dollars.

Decimal with 7 decimal places.

Example:

"0.0000000"

grossInterchangeUsd
string
required

Interchange earned on this settlement before scheme deductions, in US dollars. This is the full figure, not your share of it.

Decimal with 7 decimal places.

Example:

"0.5147284"

netInterchangeUsd
string
required

Gross interchange less the scheme settlement fees attributable to it, in US dollars. This is the full figure; your revenue share is the percentage set out in your pricing schedule.

Decimal with 7 decimal places.

Example:

"0.4318766"

digitalCommerceServiceFeeUsd
string
required

Digital commerce service fee Reap charged you on this row, in US dollars: the Visa fee on a card-not-present authorization, such as an online purchase. Zero on a card-present transaction.

Decimal with 7 decimal places.

Example:

"0.0000000"

eventType
enum<string>

Lifecycle event the fee was assessed on. Empty on rows with no card transaction event, which feeType explains.

Available options:
AUTHORIZATION,
CLEARING,
REVERSAL,
REFUND,
DECLINE,
DISPUTE_REFUND
Example:

"CLEARING"

eventId
string<uuid>

Card transaction event this fee was assessed on, as returned by the API.

Example:

"5d4f7c64-0b8f-4a5e-9c1d-3e4f5a6b7c8d"

transactionId
string<uuid>

Card transaction the event belongs to. Several rows share one transaction: multiple captures, refunds and adjustments.

Example:

"6e5f7c64-0b8f-4a5e-9c1d-3e4f5a6b7c8d"

cardId
string<uuid>

Card the fee is attributed to. Present on rows with no transaction event, which is what makes a per-occurrence fee traceable. Empty only if the card could not be resolved.

Example:

"2a1f7c64-0b8f-4a5e-9c1d-3e4f5a6b7c8d"

cardLast4
string

Last four digits of the card number. Empty when cardId is.

Example:

"4242"

accountId
string<uuid>

Account the card belongs to. Empty when cardId is.

Example:

"4c3f7c64-0b8f-4a5e-9c1d-3e4f5a6b7c8d"

channel
enum<string>

How the transaction was initiated. ATM invoice lines filter on this column.

  • ATM: Cash withdrawal at an ATM
  • POS: In-store, card present
  • ECOMMERCE: Online or card-not-present
  • VISA_DIRECT: Visa Direct transfer. On an authorization, a funding transfer that debits the card, such as topping up a wallet
Available options:
ATM,
POS,
ECOMMERCE,
VISA_DIRECT
Example:

"ECOMMERCE"

originalAmount
string

Amount in the currency the merchant charged. Empty on rows with no merchant.

Decimal with 2 decimal places.

Example:

"24.99"

originalCurrency
string

Currency the merchant charged in.

Example:

"USD"

merchantName
string

Merchant as named in the network message.

Example:

"Northwind Supplies"

merchantCountry
string

Two-letter ISO 3166 country code of the merchant.

Example:

"GB"

mcc
string

Merchant category code of the merchant's business.

Example:

"5411"

settlementDate
string<date>

Day the transaction settled, UTC. Empty while it is still authorized.

Example:

"2026-09-03"