# ReceiptCardSummaryDto

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

DTO for card/payment method summary displayed on a receipt.
Contains only non-sensitive data.

## Fields
- `lastFour` (string): Last four digits of the card number (e.g. "4242"). (nullable)
- `cardBrand` (string): Card brand (e.g. "Visa", "Mastercard"). (nullable)
- `cardholderName` (string): Cardholder name. (nullable)
- `entryMode` ([EntryModes](https://devportal.signapay-sbx.winkpg.io/docs/api/models/EntryModes.md)): Card entry mode. (nullable)
  Values:
  - `Unknown`: The entry mode is unknown.
  - `NotApplicable`: The entry mode is not applicable for this transaction.
  - `Manual`: The transaction details were entered manually.
  - `UnencryptedCardReaderSwipe`: The card was swiped through an unencrypted card reader.
  - `EncryptedCardReaderSwipe`: The card was swiped through an encrypted card reader.
  - `Icc`: The transaction was processed using an ICC (Integrated Circuit Card) or chip card.
  - `Proximity`: The transaction was processed using a proximity or contactless payment method.
  - `Fallback`: The transaction was processed using a fallback method when the primary method failed.
  - `TechnicalFallback`: The transaction was processed using a fallback method when the primary method failed.
  - `EmptyCandidateFallback`: The transaction was processed using a fallback method when the primary method failed.
  - `DigitalWallet`: The transaction was processed using a digital wallet.
- `avsResponseCode` (string): AVS response code. (nullable)
- `avsResponseText` (string): Human-readable AVS response. (nullable)
- `paymentType` (string): Payment type derived from BIN data (e.g. "Credit", "Debit"). Printed so the receipt says whether the card was a credit or a debit card, which processor receipt rules require. (nullable)
- `tenderType` ([CardTenderType](https://devportal.signapay-sbx.winkpg.io/docs/api/models/CardTenderType.md)): Card-rail tender used for the transaction. Surfaces this on receipts so EBT SNAP / EBT Cash / WIC transactions render program-appropriate language even when the BIN-derived `paymentType` would label them generically (e.g. "Debit"). Null when the transaction recorded no tender; the receipt then uses the generic credit/debit layout. (nullable)
  Values:
  - `CreditDebit`: Standard credit/debit card. The current card-rail behaviour. isDebitRouting modulates whether the request prefers debit-network routing within this rail.
  - `EbtSnap`: EBT SNAP (food benefits). Routes through the EBT SNAP processor lane and requires PIN + card-present per program rules.
  - `EbtCash`: EBT Cash (cash benefits). Distinct rail from SNAP; supports cashback where SNAP does not. PIN + card-present required.
  - `Ewic`: eWIC (Women, Infants, and Children). Distinct rail from EBT, with item-level eligibility / voucher-select flow handled in the eWIC follow-up epic.
- `ebtBalanceAvailable` (number(double)): EBT balance available after the transaction, when the processor returns it on the authorization response. `null` when not applicable (credit/debit) or not provided by the processor. receipts render this value on a dedicated "EBT Balance Available" line for EBT SNAP / EBT Cash transactions. (nullable)
- `tenderLabel` (string): Human-readable label for the tender (e.g. "Credit / Debit", "EBT SNAP", "EBT Cash", "WIC"). Pre-formatted by the receipt assembler so renderers don't need to localize the enum themselves. (nullable)

## See also

- [All documentation](https://devportal.signapay-sbx.winkpg.io/llms.txt): the machine-readable index of every public page on this site.