---
title: "CustomerPaymentMethodByCustomerIdCustomerPaymentMethodId (Visma.net Financials)"
description: "Customer Payment Method by Customer ID Customer Payment Method ID"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.CustomerPaymentMethod.CustomerPaymentMethodByCustomerIdCustomerPaymentMethodId
original: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.CustomerPaymentMethod.CustomerPaymentMethodByCustomerIdCustomerPaymentMethodId
updated: 2026-11-01T17:49:50Z
license: https://documentation.invantive.eu/en/
---

# CustomerPaymentMethodByCustomerIdCustomerPaymentMethodId: Visma.net Financials Customer Payment Method by Customer ID Customer Payment Method ID

`read only` `REST`

- Catalog: `VismaNet`
- Schema: `CustomerPaymentMethod`
- Label: Customer Payment Method by Customer ID Customer Payment Method ID

Get one specific Customer payment method for one specific customer. ScreenId=AR303010
Data for Customer payment method 
The response headers include an ETag after a successful GET operation.

Can only retrieve data.

## Summary

Data for Customer payment method <br></br>
The response headers include an ETag after a successful GET operation.

## API Source

- Endpoint: `/v1/customerpaymentmethod/{customerId}/{customerPaymentMethodId}`
- Operation: `get /v1/customerpaymentmethod/{customerId}/{customerPaymentMethodId}`

## Performance Characteristics

| Characteristic | Value |
|---|---:|
| Average access latency (ms) | 155 |
| Full scan rows per minute | 29,100 |
| Point query rows per minute | 387 |

The result can be cached on the client.

## Parameters

| Name | Data Type | Required | Default | Documentation |
|---|---|:---:|---|---|
| `customerId` | `` | [x] |  | Identifies the Customer |
| `customerPaymentMethodId` | `` | [x] |  | Identifies the Customer payment method |

## Table Columns

The columns of the table `CustomerPaymentMethodByCustomerIdCustomerPaymentMethodId` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `COMPANY_CODE` | `varchar2(30)` | Company Code | [x] | writable | Partition code, segmenting the data. |
| `COMPANY_NAME` | `varchar2(240)` | Company Name | [x] | writable | Name of the partition. |
| `active` | `char` | Active | [ ] | filters on the platform, writable, `active` | The top part &gt; Active &gt; A check box that indicates (if selected) that the selected customer payment method is active (that is, available for recording payments). |
| `cardOrAccountNo` | `varchar2` | itgen_vnet_cardoraccountno | [ ] | filters on the platform, writable, `cardOrAccountNo` | The top part &gt; Card/account no. &gt; The identifier for the customer's payment method. |
| `cashAccount_description` | `varchar2` | Cash Account Description | [ ] | filters on the platform, writable, `cashAccount.description` | Click on the magnifier. &gt; The description. |
| `cashAccount_id` | `varchar2` | itgen_vnet_cashaccount_id | [ ] | filters on the platform, writable, `cashAccount.id` | Click on the magnifier. &gt; The identifier. |
| `customer_id` | `varchar2` | itgen_vnet_customer_id | [ ] | filters on the platform, writable, `customer.id` |  |
| `customer_name` | `varchar2` | Customer Name | [ ] | filters on the platform, writable, `customer.name` | Click the magnifier &gt; The displayed name |
| `paymentMethod_description` | `varchar2` | Payment Method Description | [ ] | filters on the platform, writable, `paymentMethod.description` | Click on the magnifier. &gt; The description. |
| `paymentMethod_id` | `varchar2` | Payment Method ID | [ ] | filters on the platform, writable, `paymentMethod.id` | Click on the magnifier. &gt; The identifier. |
| `timeStamp` | `blob` | Timestamp | [ ] | filters on the platform, writable, `timeStamp` | Identifier that represents a specific version of the resource. It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers) |



## Release Notes

What changed per release in the tables, columns, attributes and capabilities of the driver:

- [Visma.net Financials](/en/release-notes/drivers?driver=visma-net-financials)

