Create earmark (deprecated)

Creates an earmark.
An account holder can use an earmark to hold funds in reserve until a specified release date and time.
Optionally, the account holder can schedule a payout for the release date and time. An automatic process then releases the earmarked funds and settles the payout.
If no release_datetime is set, the earmarked amount is held indefinitely until the customer cancels the earmark.
It's possible to force the creation of an earmark by not performing any regular validations, such as account status, account balance, or flex controls validations.

This endpoint generates the follow events:

• Authorization created
• Account balance changed
• Account balance changed (Availables)
• Transaction created
• Earmark created, updated, or canceled with CREATED action.

NOTES:

• This endpoint requires an account-specific access token. Getting an account token requires you to call the Get OpenID access token endpoint with an external account ID. Tokens can expire quickly, which can result in an unauthorized message.
• The events Authorization created and Transaction created include "corporate_metadata" in the "metadata" and "details" fields respectively. The "corporate_metadata" contains the following fields:
  • debit_external_account_id: The debited account in the creation operation.
  • earmark_id: The created earmark id.
• The Authorization created, which is generated in response to the hold funds operation related to the earmark balance, does not include currency information like a typical payment transaction. However, it's important to note that the earmark operates within the same currency configuration as the account.
• The event Earmark created, updated, or canceled only contains internal_operation that refers to the operation performed (Earmark creation).
• If the account has any reason-based force debit restrictions, the force earmark creation fails. The reasons that restrict force debit operations are:
  • Credit only — No force debit allowed
  • Any — No force allowed
  • Manual — No force allowed
• To find the correct reason IDs, refer to the List account status reasons endpoint.