Delete scheduled transfer

Delete Scheduled Transfer

This endpoint removes a scheduled transfer that has not yet been executed. Once deleted, the transfer will not be processed on its scheduled date. Use this endpoint whenever a customer needs to cancel an upcoming scheduled payment or fund movement.

Endpoint

DELETE /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 or partner needs to cancel a scheduled transfer before it executes. This is applicable for both one-time and recurring scheduled transfers that are no longer needed. The transfer must be identified by its system-assigned integer ID obtained when the transfer was originally created.

Request Body

{
  "id": 10482
}

Response

200 OK

{
  "status": "success",
  "message": "Scheduled transfer deleted successfully."
}

Error Codes

Common Mistakes

• Passing a string or UUID for id instead of the integer assigned by Netevia at transfer creation time — the field must be an int32.
• Attempting to delete a transfer that has already been executed or has already been cancelled; such transfers will return 404.
• Omitting the id field entirely — it is the only required field and the request will fail with 400 if absent.
• Using a token belonging to a user who does not own the scheduled transfer — the API will return 403.

Related Endpoints

• POST /api/scheduledTransfer — Create a new scheduled transfer
• GET /api/scheduledTransfer — Retrieve a list of scheduled transfers for an account
• PUT /api/scheduledTransfer — Update an existing scheduled transfer

Example

curl -X DELETE https://api.banking.netevia.dev/api/scheduledTransfer \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 10482
  }'