Update Scheduled Transfer

This endpoint updates the details of an existing scheduled transfer identified by its unique ID. Modifications may include the transfer amount, next execution date, frequency, memo, active status, or other transfer attributes. A valid one-time security code is required to authorize the update operation.

Endpoint

PUT /api/scheduledTransfer

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a customer needs to modify a previously scheduled transfer — for example, changing the transfer amount, rescheduling the next execution date, adjusting the recurrence frequency, or deactivating the transfer without deleting it. This is applicable for both internal transfers (between a customer's own accounts) and ACH transfers to external accounts. All updates require two-factor verification via a one-time code.

Request Body

{
  "id": 1042,
  "fromFinancialAccountId": "fa-src-abc123def456",
  "toFinancialAccountId": "fa-dst-xyz789ghi012",
  "amount": 25000,
  "currencyCode": 840,
  "nextDate": "2026-07-01T09:00:00Z",
  "endDate": "2027-06-30T23:59:59Z",
  "frequency": "1m",
  "transferType": "TransferBetweenOwnAccounts",
  "isActive": true,
  "name": "Monthly Savings Transfer",
  "memo": "Automated monthly savings",
  "minAmount": 50000,
  "oneTimeCode": "482931",
  "secureOperationType": "ShortMessageCode"
}

Response

200 OK

{
  "id": 1042,
  "name": "Monthly Savings Transfer",
  "fromFinancialAccountId": "fa-src-abc123def456",
  "toFinancialAccountId": "fa-dst-xyz789ghi012",
  "isActive": true,
  "transferType": "TransferBetweenOwnAccounts",
  "amount": 25000,
  "currencyCode": 840,
  "frequency": "1m",
  "lastDate": "2026-06-01T09:00:00Z",
  "nextDate": "2026-07-01T09:00:00Z",
  "endDate": "2027-06-30T23:59:59Z",
  "memo": "Automated monthly savings",
  "minAmount": 50000,
  "isRejected": false
}

Error Codes

Common Mistakes

• Providing an id that does not belong to a scheduled transfer owned by the authenticated customer — returns 404
• Omitting nextDate or sending it in a non-ISO 8601 format — returns 400
• Using an expired or already-consumed oneTimeCode — returns 401; request a fresh code before retrying
• Sending frequency in an incorrect format (e.g., monthly instead of 1m) — must match pattern ^(\d+)([ymwd])$
• Sending amount as a decimal (e.g., 250.00) instead of an integer in cents (e.g., 25000) — returns 400
• Forgetting that updating fromFinancialAccountId or toFinancialAccountId still requires both fields to be present and valid

Related Endpoints

• POST /api/scheduledTransfer — Create a new scheduled transfer
• GET /api/scheduledTransfer — Retrieve a list of scheduled transfers for the authenticated customer
• DELETE /api/scheduledTransfer/{id} — Delete an existing scheduled transfer
• POST /api/transfer — Execute an immediate (non-scheduled) transfer

Example

curl -X PUT https://api.banking.netevia.dev/api/scheduledTransfer \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 1042,
    "fromFinancialAccountId": "fa-src-abc123def456",
    "toFinancialAccountId": "fa-dst-xyz789ghi012",
    "amount": 25000,
    "currencyCode": 840,
    "nextDate": "2026-07-01T09:00:00Z",
    "endDate": "2027-06-30T23:59:59Z",
    "frequency": "1m",
    "transferType": "TransferBetweenOwnAccounts",
    "isActive": true,
    "name": "Monthly Savings Transfer",
    "memo": "Automated monthly savings",
    "minAmount": 50000,
    "oneTimeCode": "482931",
    "secureOperationType": "ShortMessageCode"
  }'