Adyen · Schema

TransferData

TransferData schema from Adyen API

PaymentsFinancial ServicesFintech

Properties

Name Type Description
accountHolder object The account holder associated with the balance account used in the transfer.
amount object The amount of the transfer.
balanceAccount object Contains information about the balance account involved in the transfer.
balancePlatform string The unique identifier of the balance platform.
balances array The list of the latest balance statuses in the transfer.
category string The category of transfer. Possible values: - **bank**: Transfer to a [transfer instrument](https://docs.adyen.com/api-explorer/#/legalentity/latest/post/transferInstruments__resParam_id) or a bank acc
categoryData object The relevant data according to the transfer category.
counterparty object The other party in the transfer.
creationDate string The date and time when the event was triggered, in ISO 8601 extended format. For example, **2020-12-18T10:15:30+01:00**.
description string Your description for the transfer. It is used by most banks as the transfer description. We recommend sending a maximum of 140 characters, otherwise the description may be truncated. Supported charact
direction string The direction of the transfer. Possible values: **incoming**, **outgoing**.
events array The list of events leading up to the current status of the transfer.
id string The ID of the resource.
paymentInstrument object Contains information about the payment instrument used in the transfer.
reason string Additional information about the status of the transfer.
reference string Your reference for the transfer, used internally within your platform. If you don't provide this in the request, Adyen generates a unique reference.
referenceForBeneficiary string A reference that is sent to the recipient. This reference is also sent in all webhooks related to the transfer, so you can use it to track statuses for both the source and recipient of funds. Supporte
sequenceNumber integer The sequence number of the transfer notification. The numbers start from 1 and increase with each new notification for a specific transfer. It can help you restore the correct sequence of events even
status string The result of the transfer. For example, **authorised**, **refused**, or **error**.
tracking object The tracking information for the transfer.
transactionRulesResult object Contains the results of the evaluation of the transaction rules.
type string The type of transfer or transaction. For example, **refund**, **payment**, **internalTransfer**, **bankTransfer**.
View JSON Schema on GitHub