v1
latestOpenAPI 3.0.22026-08-061303782.1 MBCreate a Custom Fee
Create a custom (i.e. one-time) Fee.
Headers
Specify the API version of your request. For more details, see Versioning.
The data type being sent in the request body must be application/json.
Request body
The total amount that will be debited in cents (e.g. 100 cents to debit $1.00).
ISO 4217 3-letter currency code.
The display name of the Fee that can be used for filtering purposes.
Subtype of the fee. Set to CUSTOM.
The type of the fee. Must be set to CUSTOM.
The ID of the Merchant resource used to create the Fee.
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)
Example request
{
"amount": 5000
}Response
Single Custom Fee object
The ID of the resource.
Timestamp of when the object was created.
Timestamp of when the object was last updated.
Represents the total amount. The value may be returned as either:
- an integer (int32) in cents (e.g., 100 = $1.00), or
- a double for fractional amounts (e.g., 2.393).
ID of the Application the resource was created under.
The Fee category.
ISO 4217 3-letter currency code.
It is used for subscription fees and allows free-form text to be passed from the subscription fee product. Note that this product is mostly deprecated.
The ID of the Fee Profile used to calculate fees for the Transfer related to this Fee. The specific Transfer is identified by the linked_to field.
The subtype of the Fee.
The type of Fee. Finix may return more enums than those provided. Ensure your code accepts additional enums returned by Finix.
It is used for subscription fees and allows free-form text to be passed from the subscription fee product. Note that this product is mostly deprecated.
The ID of the linked resource. Note that this field will be deprecated soon, use linked_to instead.
The ID of the linked resource.
The type of entity the Fee is linked to.
The ID of the Merchant resource that was charged the fee.
The timestamp indicating when the Transfer related to this Fee is ready to be settled. The specific Transfer is identified by the linked_to field.
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)
Example response
{
"amount": 2.393
}