Please enable JavaScript to view this site.

Odoo API Data Model Odoo Forums

Navigation: Schema: pos > Tables

payment_method

Point of Sale Payment Methods

Catalog: Odoo

Schema: pos

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table payment_method are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

active

boolean

Active

☐

 

company_id_label

string

 

☐

 

company_id

string

 

☐

 

config_ids

string

 

☐

 

create_date

datetime

Created on

☐

 

create_uid_label

string

 

☐

 

create_uid

string

 

☐

 

display_name

string

Display Name

☐

 

hide_use_payment_terminal

boolean

Hide Use Payment Terminal

☐

 

id

int32

ID

☐

 

image

byte[]

Image

☐

 

iot_device_id_label

string

 

☐

 

iot_device_id

string

 

☐

 

is_cash_count

boolean

Cash

☐

 

journal_id_label

string

 

☐

Leave empty to use the receivable account of customer.Defines the journal where to book the accumulated payments (or individual payment if Identify Customer is true) after closing the session.For cash journal, we directly write to the default account in the journal via statement lines.For bank journal, we write to the outstanding account specified in this payment method.Only cash and bank journals are allowed.

journal_id

string

 

☐

Leave empty to use the receivable account of customer.Defines the journal where to book the accumulated payments (or individual payment if Identify Customer is true) after closing the session.For cash journal, we directly write to the default account in the journal via statement lines.For bank journal, we write to the outstanding account specified in this payment method.Only cash and bank journals are allowed.

name

string

Method

☑

Defines the name of the payment method that will be displayed in the Point of Sale when the payments are selected.

open_session_ids

string

 

☐

Open PoS sessions that are using this payment method.

outstanding_account_id_label

string

 

☐

Leave empty to use the default account from the company setting.Account used as outstanding account when creating accounting payment records for bank payments.

outstanding_account_id

string

 

☐

Leave empty to use the default account from the company setting.Account used as outstanding account when creating accounting payment records for bank payments.

payment_terminal_ids

string

 

☐

 

receivable_account_id_label

string

 

☐

Leave empty to use the default account from the company setting.Overrides the company's receivable account (for Point of Sale) used in the journal entries.

receivable_account_id

string

 

☐

Leave empty to use the default account from the company setting.Overrides the company's receivable account (for Point of Sale) used in the journal entries.

split_transactions

boolean

Identify Customer

☐

Forces to set a customer when using this payment method and splits the journal entries for each customer. It could slow down the closing process.

type

string

Type

☐

 

use_payment_terminal

string

Use a Payment Terminal

☐

Record payments with a terminal on this journal.

write_date

datetime

Last Updated on

☐

 

write_uid_label

string

 

☐

 

write_uid

string

 

☐

 

 

01-03-2023 15:29 Version 22.1.135-BETA+3826

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer