# PutPaymentInformationNonSepaByPaymentInformationNonSepaId Change the details of a payment information non-SEPA __Activity name :__ PutPaymentInformationNonSepaByPaymentInformationNonSepaId Edit an existing payment information non-SEPA record (for an employment). For each unique payroll component there can only be one payment record per employment. __Metadata :__ 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/paymentinformationnonsepa/{paymentInformationNonSepaId} Insert loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationnonsepa/{paymentInformationNonSepaId} Update loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationnonsepa/{paymentInformationNonSepaId} Delete loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationnonsepa/{paymentInformationNonSepaId} Select loket.nl (REST) API Operation: put /providers/employers/employees/employments/paymentinformationnonsepa/{paymentInformationNonSepaId} - Catalog: `LoketNlRest` - Schema: `PaymentInformationNon-SEPA` - 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` | ☑ | | | | `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). | | `paymentInformationNonSepaId` | `guid` | ☑ | | The unique identifier of the SEPA payment record | ## Columns of Table Function The columns of the table function `PutPaymentInformationNonSepaByPaymentInformationNonSepaId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `bank_address` | `string(35)` | | ☐ | Address of beneficiary bank | | `bank_bankIdentifierCode` | `string(11)` | | ☐ | BIC /SWIFT code for the bank | | `bank_city` | `string(35)` | | ☐ | City name of beneficiary bank | | `bank_country_isoCode` | `string(2)` | | ☐ | The ISO 3166-1 alpha-2 value for the country | | `bank_country_key` | `int32` | | ☐ | The key for the country. Posible values can be aquired via the metadata endpoint | | `bank_country_value` | `string(50)` | | ☐ | The name of the country | | `bank_name` | `string(35)` | | ☐ | Name of benificiary bank | | `bankAccountNumber` | `string(34)` | | ☐ | The bank account number | | `beneficiary_address` | `string(35)` | | ☐ | Address of beneficiary | | `beneficiary_city` | `string(35)` | | ☐ | City name of beneficiary | | `beneficiary_country_isoCode` | `string(2)` | | ☐ | The ISO 3166-1 alpha-2 value for the country | | `beneficiary_country_key` | `int32` | | ☐ | The key for the country. Posible values can be aquired via the metadata endpoint | | `beneficiary_country_value` | `string(50)` | | ☐ | The name of the country | | `beneficiary_name` | `string(35)` | | ☐ | Name of the beneficiary | | `id` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `payrollComponent_key` | `int32` | | ☐ | The number for the payroll component | | `payrollComponent_value` | `string(14)` | | ☐ | The description of the payroll component |