sender_lastName

Last name of sender when the sender is an individual.
The TC 33 capture file contains information about the payments and credits that a merchant submits to
Cybersource
. The processor creates the TC 33 capture file at the end of the day and sends it to the merchant’s acquirer. The acquirer uses this information to facilitate end-of-day clearing processing with payment networks.
This field is available only on these processors:
  • Barclays
  • Chase Paymentech Solutions
  • FDC Compass
  • LloydsTSB Cardnet International
  • First Data Merchant Solutions
  • Streamline
  • Visa Platform Connect
These processors have specific requirements:
Barclays
For a Mastercard Payment of Winnings (indicated when you set the
ccCreditService_refundReason
 field to
pow
), you can use this field to specify a merchant last name in a Mastercard Payment of Winnings
stand-alone credit
 request.
For an Account Funding Transactions (AFT), this field must be alphanumeric and special characters must be in ASCII format. You must not exceed 30 characters for the concatenated value of
sender_firstname
,
sender_middlename
, and
sender_lastname
 fields.
Chase Paymentech Solutions
When the sender is a business or government entity, use the
sender_name
 field.
This field is required for Original Credit Transactions (OCTs) when the sender is a when the sender is an individual. It is supported only for Mastercard transactions that use the Payouts.
Visa Platform Connect
The value for this field corresponds to this data in the TC 33 capture file.
  • Record: CP09 TCR3
  • Position: 75-109
  • Field: Account Owner Last Name

Specifications

  • Data Type:
     String
  • Data Length:
     35
    • Barclays
      : See field description.
    • First Data Merchant Solutions
      : 25
    • LloydsTSB Cardnet International
      : 25

Mapping Information

  • REST API Field:
    senderInformation.lastName
  • SCMP API Field:
    sender_lastname
  • Simple Order API Field:
    sender_lastName