# PutPaymentInformationSepaByPaymentInformationSepaId change the details of a payment information sepa __Activity name :__ PutPaymentInformationSepaByPaymentInformationSepaId Edit an existing SEPA payment-record (for an employment). For each unique payroll component there can only be one payment record per employment. Possible values for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the URL Select loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepa/{paymentInformationSepaId} Insert loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepa/{paymentInformationSepaId} Update loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepa/{paymentInformationSepaId} Delete loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepa/{paymentInformationSepaId} Select loket.nl (REST) API Operation: put /providers/employers/employees/employments/paymentinformationsepa/{paymentInformationSepaId} - Catalog: `LoketNlRest` - Schema: `PaymentInformation` - Field Selection Method: NotRequired - Base Path: `content` This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API. ## Parameters of Table Function | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `body` | `string` | ☑ | | SEPA payment record to edit | | `If-Match` | `string` | ☐ | | Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations). | | `paymentInformationSepaId` | `guid` | ☑ | | The unique identifier of the SEPA payment record | ## Columns of Table Function The columns of the table function `PutPaymentInformationSepaByPaymentInformationSepaId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `beneficiary_city` | `string(24)` | | ☐ | City name of beneficiary. | | `beneficiary_name` | `string(70)` | | ☐ | Name of beneficiary. | | `bic` | `string(11)` | | ☐ | BIC /SWIFT code. Only applicable for a non-Dutch IBAN | | `description1` | `string(32)` | | ☐ | Description 1. Both description field values will be a line in the (unstructured) description of the SEPA file. | | `description2` | `string(32)` | | ☐ | Description 2. Both description field values will be a line in the (unstructured) description of the SEPA file. | | `iban` | `string(35)` | | ☐ | International Bank Account Number (IBAN). Only IBAN without spaces are accepted. | | `id` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `payrollComponent_description` | `string(50)` | | ☐ | | | `payrollComponent_key` | `int32` | | ☐ | | | `visibleOnPayslip` | `boolean` | | ☐ | Indicates whether the payment-component is visible on a payslip. |