# Update a scheduled transfer

Initiates an update to the specified scheduled transfer.  This action requires 2FA confirmation. The endpoint will create a change request and return a 202 Accepted response. The requested updates will only be applied once the customer successfully confirms the change request challenge.

Endpoint: PATCH /v1/accounts/{account_id}/scheduled_transfers/{id}
Version: 1.0

## Path parameters:

  - `id` (string, required)
    The ID of the scheduled transfer to update.

  - `account_id` (string, required)
    The ID of the account associated with the scheduled transfer.

## Request fields (application/json):

  - `amount` (object)

  - `amount.value` (integer)
    The monetary value of the transaction in Euro cents.
    Example: 1000

  - `amount.currency` (string)
    The currency of the given value. Only EUR is currently supported.
    Example: "EUR"

  - `description` (string)
    A textual description or reference for the scheduled transfer.
    Example: "Rent"

  - `active_to` (string)
    The expiration date of the scheduled transfer. The final transfer will execute on or before this date.
    Example: "2018-04-01"

## Response 200 fields (application/json):

  - `id` (string)
    Unique ID of the scheduled transfer.
    Example: "f874b3102718a4d757a6b6e4d599607csctr"

  - `account_id` (string)
    The account ID of the account that the scheduled transfer is associated with.
    Example: "236f9042a19b65c0867e10c922b93502cacc"

  - `status` (string)
    The status of the scheduled transfer.
    Enum: "AUTHORIZATION_REQUIRED", "ACTIVE", "CANCELED", "CONCLUDED"

  - `transfer_type` (string)
    The type of the scheduled transfer.
    Enum: "SCT", "SCT_INSTANT"

  - `creditor_iban` (string)
    The recipient's IBAN.
    Example: "DE87110101001000057123"

  - `creditor_name` (string)
    The recipient's name.
    Example: "Hans Mustermann"

  - `creditor_bic` (string)
    The recipient's BIC.
    Example: "COBADEFFXXX"

  - `initiator_reference` (string)
    Reference provided by the transaction initiator. It needs to be unique for the initiator.
    Example: "dsf2r3raedfs3fsf342fctrx"

  - `amount` (object)
    The amount of the scheduled transfer transaction (in Euro cents).

  - `amount.value` (integer)
    Amount described in smallest currency unit (e.g. cents).
    Example: 1000

  - `amount.currency` (string)
    The currency of the given value. Only EUR is currently supported.
    Example: "EUR"

  - `description` (string)
    Optional description for the transaction, which will be visible to the recipient. Limited to 140 characters.

  - `active_from` (string)
    The date on which the scheduled transfer will become active. The first transfer will be executed on this date.
    Example: "2025-09-01"

  - `active_to` (string)
    The date by which the scheduled transfer will become concluded. The last transfer will be executed before or on this date. For one-time transfers this field will default to the active_from date.
    Example: "2026-09-01"

  - `execution_schedule` (string)
    The frequency at which to execute the scheduled transfer.
    Enum: "WEEKLY", "EVERY_TWO_WEEKS", "MONTHLY", "QUARTERLY", "EVERY_SIX_MONTHS", "ANNUALLY", "ONE-TIME"

  - `end_to_end_id` (string)
    SEPA identifier provided by the transaction initiator, which will be routed throughout the whole payment process.
    Example: "END2ENDREJ"

  - `next_execution_date` (string)
    Next execution_schedule for this scheduled transfer
    Example: "2025-10-01"

  - `authorizer_id` (string)
    The ID of the person who authorized the scheduled transfer.
    Example: "cf67beb032b2abbfc444f1641fa669bccper"

  - `verification_of_payee_id` (string)
    The ID of the verification of payee process that was used to verify the recipient's name and IBAN.
    Example: "f874b3102718a4d757a6b6e4d5996078veop"

  - `created_at` (string)
    UTC timestamp from the time the scheduled transfer was created.
    Example: "2022-04-21T13:59:52+00:00"

  - `updated_at` (string)
    UTC timestamp from the last time the scheduled transfer was updated.
    Example: "2022-04-21T13:59:52+00:00"

## Response 202 fields (application/json):

  - `id` (string)
    The ID of the scheduled transfer.
    Example: "f874b3102718a4d757a6b6e4d599607csctr"

  - `change_request` (object)

  - `change_request.id` (string)
    ID of the change request.
    Example: "d6c778822b2d7bd3b778935bcfd0d1d3csc"

  - `change_request.status` (string)
    The current status of the change request.
    Enum: "ACCEPTED", "AUTHORIZATION_REQUIRED", "CONFIRMATION_REQUIRED", "COMPLETED", "FAILED"

  - `change_request.updated_at` (string)
    UTC timestamp from the last time the change request was updated.
    Example: "2022-04-21T13:59:52+00:00"

  - `change_request.url` (string)
    URL to use to authorize the change request.
    Example: "https://example.com/authorize"

## Response 400 fields (application/json):

  - `errors` (array)
    Example: [{"id":"ab9bc911-d5bb-481e-bdf5-ce006d96fa0c","status":400,"code":"validation_error","title":"Validation Error","detail":"The request could not be processed due to invalid input.","error_code":"invalid_request","source":{"field":"key","message":"One or more request parameters are missing or malformed."}}]

  - `errors.id` (string)
    Unique identifier for this error occurrence. Include it when contacting support.

  - `errors.status` (integer)
    The HTTP status code.

  - `errors.code` (string)
    The error category.

  - `errors.title` (string)
    Human-readable summary of the error category.

  - `errors.detail` (string)
    Human-readable explanation of this specific error.

  - `errors.error_code` (string)
    Machine-readable code identifying the specific failure. Use this rather than parsing detail. Not returned on every error.

  - `errors.source` (object)
    The request field that caused the error. Returned for validation errors; omitted where no specific field applies.

  - `errors.source.field` (string)
    Name of the request field that failed the validation.

  - `errors.source.message` (string)
    Human-readable explanation of why this specific field was rejected.

## Response 401 fields (application/json):

  - `errors` (array)
    Example: [{"id":"5e8c7961-643a-4c9c-89cc-cdfc1f367000","status":401,"code":"invalid_token","title":"Invalid Token","detail":"Token is invalid"}]

  - `errors.id` (string)
    Unique identifier for this error occurrence. Include it when contacting support.

  - `errors.status` (integer)
    The HTTP status code.

  - `errors.code` (string)
    The error category.

  - `errors.title` (string)
    Human-readable summary of the error category.

  - `errors.detail` (string)
    Human-readable explanation of this specific error.

  - `errors.error_code` (string)
    Machine-readable code identifying the specific failure. Not returned on every error.

  - `errors.source` (object)
    Returned as an empty object for authentication errors, which are not attributable to a request field.

  - `errors.source.field` (string)
    Name of the request field that failed the validation.

  - `errors.source.message` (string)
    Human-readable explanation of why this specific field was rejected.

## Response 403 fields (application/json):

  - `errors` (array)
    Example: [{"id":"c47d8b21-6e3f-4a82-b715-2d9e4f8a1c56","status":403,"code":"unauthorized_action","title":"Unauthorized Action","detail":"The authenticated client is not permitted to perform this action."}]

  - `errors.id` (string)
    Unique identifier for this error occurrence. Include it when contacting support.

  - `errors.status` (integer)
    The HTTP status code.

  - `errors.code` (string)
    The error category.

  - `errors.title` (string)
    Human-readable summary of the error category.

  - `errors.detail` (string)
    Human-readable explanation of this specific error.

  - `errors.error_code` (string)
    Machine-readable code identifying the specific failure. Not returned on every error.

## Response 404 fields (application/json):

  - `errors` (array)
    Example: [{"id":"1365d465-71e9-44a0-a2da-b02f090ff760","status":404,"code":"not_found","title":"Not Found","detail":"No resource exists at the given identifier.","error_code":"not_found"}]

  - `errors.id` (string)
    Unique identifier for this error occurrence. Include it when contacting support.

  - `errors.status` (integer)
    The HTTP status code.

  - `errors.code` (string)
    The error category.

  - `errors.title` (string)
    Human-readable summary of the error category.

  - `errors.detail` (string)
    Human-readable explanation of this specific error.

  - `errors.error_code` (string)
    Machine-readable code identifying the specific failure. Not returned on every error.

## Response 500 fields (application/json):

  - `errors` (array)
    Example: [{"id":"1365d465-71e9-44a0-a2da-b02f090ff760","status":500,"code":"generic_error","title":"Generic Error","detail":"An unexpected error occurred while processing the request.","error_code":"generic_error"}]

  - `errors.id` (string)
    Unique identifier for this error occurrence. Include it when contacting support so the failure can be traced.

  - `errors.status` (integer)
    The HTTP status code.

  - `errors.code` (string)
    The error category.

  - `errors.title` (string)
    Human-readable summary of the error category.

  - `errors.detail` (string)
    Human-readable explanation of this specific error.

  - `errors.error_code` (string)
    Machine-readable code identifying the specific failure. Not returned on every error.