v1
latestOpenAPI 3.0.22026-08-061303782.1 MBFetch a Transfer
Retrieve a Transfer.
Headers
Specify the API version of your request. For more details, see Versioning.
Response
A single Transfer object.
The ID of the resource.
Timestamp of when the object was created.
Timestamp of when the object was last updated.
Details the results of the address verification checks.
The total amount that will be debited in cents (e.g. 100 cents to debit $1.00).
The amount that was requested to get debited from the source when the transaction was created, in cents (e.g., 100 = $1.00).
ID of the Application associated with the resource.
ISO 4217 3-letter currency code.
Gives more information about the product flow that was used to create the resource. Finix retains the right to add additional enums for this field without it being a breaking change.
ID of the Payment Instrument where funds will be sent.
The ID of the Device resource the Transfer was created under.
Details if the Transfer will be settled externally by card processors.
The code of the failure so the decline can be handled programmatically. For more info on how to handle the failure, see Failure Codes.
A human-readable description of why the transaction was declined. This will also include a suggestion on how to complete the payment.
The minimum amount of the Transfer you'd like to collect as your fee in cents. Defaults to zero (must be less than or equal to the amount).
- If the fees applied by the 'Fee Profile' are higher than the value passed in 'fee', 'fee' will not be applied and have no effect.
- If the fees applied by the 'Fee Profile' are lower than the value passed in 'fee', an additional fee is be applied, in addition to the fees generated by the Fee Profile.
- The additional fee is equal to the difference between the value passed in 'fee' and the fees generated by the Fee Profile.
The ID of the Fee Profile that will be used for calculating fees for this transfer.
The type of disbursement to perform. Defaults to GENERAL_PAYOUT.
Pass any randomly generated or internal ID to idempotently identify Transfers, Authorizations, or refund requests.
Always returns null.
The ID of the Merchant resource the Transfer was created under.
The ID of Identity resource used by the Merchant the Transfer was created under.
Details the operation that's performed in the transaction.
ID of the original parent Transfer. Only present when type is REVERSAL.
The trace_id of the original parent Transfer. Only present when type is REVERSAL.
The ID of the corresponding pull Transfer linked in a ME_TO_ME transaction.
The timestamp indicating when the Transfer is ready to be settled.
Timestamp when the receipt was last printed.
Details the results of the Card Verification Code check.
The ID of the Payment Instrument that will be debited and performing the Transfer.
Array containing the resource IDs of the Split Transfers generated from the Transfer.
For standard split transactions, this contains IDs of Split Transfers created from the parent Transfer.
For dispute adjustment transfers on split transactions:
- When a MERCHANT_DEBIT or MERCHANT_CREDIT adjustment Transfer is created for a Dispute on a split transaction, this array contains the IDs of Split Transfers created for each participant.
- The Split Transfers are created proportionally based on each merchant's share of the original sale.
For more information, see Split Transactions - Disputes.
The status of the Transfer.
The description of the Merchant that appears on the buyer's bank or card statement.
Additional information describing the payment_type.
For dispute adjustment transfers (type: DISPUTE):
- MERCHANT_DEBIT: Funds are pulled from the merchant(s) when a chargeback occurs. For split transactions, this creates Split Transfers with type: DISPUTE_MERCHANT_DEBIT.
- MERCHANT_CREDIT: Funds are returned to the merchant(s) when a Dispute is ruled in their favor. For split transactions, this creates Split Transfers with type: DISPUTE_MERCHANT_CREDIT.
Amount in cents for which an additional fee will be created in addition to any fees created from the assigned fee profile.
Include up to 50 key: value pairs to annotate requests with custom metadata.
- Maximum character length for individual keys is 40.
- Maximum character length for individual values is 500. (For example, order_number: 25, item_type: produce, department: sales)
The tip amount included in the total amount.
Trace ID of the Transfer. The processor sends back the trace_id so you can track the Transfer end-to-end.
Type of Transfer.
Example response
{
"amount": 5000,
"amount_requested": 100,
"merchant": "MUxxxxxxxxxxxxxxxxxxxxxxx",
"merchant_identity": "IDxxxxxxxxxxxxxxxxxxxxxxxx",
"network_details": {
"brand": "VISA"
}
}