# Update specific SEPA Instant limits for an account Partially update the SEPA Instant limits. This allows partners to set a daily and a per-transaction limit. By default, the account has no limit set. Only the limits specified in the request will be modified; other limits will remain unchanged. Endpoint: PATCH /v1/accounts/{account_id}/sepa_instant_limits Version: 1.0 ## Path parameters: - `account_id` (string, required) ## Request fields (application/json): - `daily_limit` (object) - `daily_limit.value` (integer, required) Maximum amount allowed per day Example: 1000000 - `daily_limit.unit` (string, required) Unit of the amount Example: "cents" - `daily_limit.currency` (string, required) Currency code Example: "EUR" - `per_transaction_limit` (object) - `per_transaction_limit.value` (integer, required) Maximum amount allowed per transaction Example: 500000 ## Response 200 fields (application/json): - `daily_limit` (object) - `daily_limit.value` (integer) Daily limit amount Example: 1000000 - `daily_limit.unit` (string) Unit of the amount Example: "cents" - `daily_limit.currency` (string) Currency code Example: "EUR" - `daily_used` (object) - `daily_used.value` (integer) Amount used today Example: 350000 - `daily_remaining` (object) - `daily_remaining.value` (integer) Remaining amount for today Example: 650000 - `per_transaction_limit` (object) - `per_transaction_limit.value` (integer) Maximum amount per single transaction Example: 500000 ## Response 400 fields (application/json): - `errors` (array, required) Example: [{"id":"b805c37f-75e9-4445-974c-12d28e7584ee","status":400,"code":"invalid_json","title":"Invalid JSON","detail":"The provided JSON was not properly formatted."}] - `errors.id` (string) A unique identifier for this error message. Example: "b805c37f-75e9-4445-974c-12d28e7584ee" - `errors.status` (integer) The HTTP status code of the response (typically in the range 4xx–5xx). Example: 400 - `errors.code` (string) A machine-readable representation of the error type. Example: "invalid_json" - `errors.title` (string) The human-readable name of the error type. Example: "Invalid JSON" - `errors.detail` (string) A human-readable description of the error. Example: "The provided JSON was not properly formatted." ## Response 404 fields (application/json): - `errors` (array, required) Example: [{"id":"b805c37f-75e9-4445-974c-12d28e7584ee","status":400,"code":"invalid_json","title":"Invalid JSON","detail":"The provided JSON was not properly formatted."}] - `errors.id` (string) A unique identifier for this error message. Example: "b805c37f-75e9-4445-974c-12d28e7584ee" - `errors.status` (integer) The HTTP status code of the response (typically in the range 4xx–5xx). Example: 400 - `errors.code` (string) A machine-readable representation of the error type. Example: "invalid_json" - `errors.title` (string) The human-readable name of the error type. Example: "Invalid JSON" - `errors.detail` (string) A human-readable description of the error. Example: "The provided JSON was not properly formatted." ## Response 500 fields (application/json): - `errors` (array, required) Example: [{"id":"b805c37f-75e9-4445-974c-12d28e7584ee","status":500,"code":"generic_error","title":"Generic Error","detail":"There was an error."}] - `errors.id` (string) A unique identifier for this error message. Example: "b805c37f-75e9-4445-974c-12d28e7584ee" - `errors.status` (integer) The HTTP status code of the response (typically in the range 4xx–5xx). Example: 400 - `errors.code` (string) A machine-readable representation of the error type. Example: "invalid_json" - `errors.title` (string) The human-readable name of the error type. Example: "Invalid JSON" - `errors.detail` (string) A human-readable description of the error. Example: "The provided JSON was not properly formatted."