recipient
The recipient is deemed to be the person or party who has the contractual relationship with the merchant / financial institution. This may be different from the cardholder, e.g., in the case of a parent topping up a child's savings account. Therefore, the fields should not be collected on the same page as cardholder information, but instead be passed in the background from the merchant's records.
Note: You can include recipient elements in your authorization request only if your Merchant Category Code is 6012 and your registered trading address is in the United Kingdom. All fields are optional. However, scheme fines may apply if data is consistently not supplied and chargebacks persist. If you have any questions, contact your account manager. If you are using a payment token for an Authorization request and there is already recipient data for the consumer profile associated with the payment token, then if you include the recipient object in the Authorization, this data will override the recipient data already in the profile.
If you look up an authorization request that used the visaAdditionalAuthData parameter (now deprecated), the response will contain the relevant data in both the recipient and the visaAdditionalAuthData objects.
dateOfBirth
object
This is the recipient's date of birth.
Possible values: <= 31
This is the day of birth.
Possible values: <= 12
This is the month of birth.
Possible values: >= 1900
This is the year of birth.
Possible values: <= 10 characters
This is the zip/postal code of the recipient.
Note: The last 3 characters are not sent to the banking network.
Possible values: <= 255 characters
This is the recipient's last name.
Note: Only the first 6 characters are sent to the banking network.
Possible values: <= 25 characters
This is the recipient's account number, e.g., a loan agreement number or customer ID. In the case where the recipient account is a prepaid card, the card number may be sent in full.
Note: Only the first 6 and last 4 characters are sent to the banking network and will be masked accordingly within the back office and any other reports, to comply with PCI regulations.