Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Odoo API Data Model

Navigation: Schema: payment > Tables

transaction

Payment Transaction

Catalog: Odoo

Schema: payment

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 transaction are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

amount

decimal

Amount

☑

 

callback_hash

string

Callback Hash

☐

 

callback_is_done

boolean

Callback Done

☐

Whether the callback has already been executed

callback_method

string

Callback Method

☐

 

callback_model_id_label

string

 

☐

 

callback_model_id

string

 

☐

 

callback_res_id

int32

Callback Record ID

☐

 

child_transaction_ids

string

 

☐

The child transactions of the source transaction.

company_id_label

string

 

☐

 

company_id

string

 

☐

 

create_date

datetime

Created on

☐

 

create_uid_label

string

 

☐

 

create_uid

string

 

☐

 

currency_id_label

string

 

☐

 

currency_id

string

 

☐

 

display_name

string

Display Name

☐

 

fees

decimal

Fees

☐

The fees amount; set by the system as it depends on the provider

id

int32

ID

☐

 

invoice_ids

string

 

☐

 

invoices_count

int32

Invoices Count

☐

 

is_donation

boolean

Is donation

☐

 

is_post_processed

boolean

Is Post-processed

☐

Has the payment been post-processed

landing_route

string

Landing Route

☐

The route the user is redirected to after the transaction

last_state_change

datetime

Last State Change Date

☐

 

operation

string

Operation

☐

 

partner_address

string

Address

☐

 

partner_city

string

City

☐

 

partner_country_id_label

string

 

☐

 

partner_country_id

string

 

☐

 

partner_email

string

Email

☐

 

partner_id_label

string

 

☐

 

partner_id

string

 

☐

 

partner_lang

string

Language

☐

 

partner_name

string

Partner Name

☐

 

partner_phone

string

Phone

☐

 

partner_state_id_label

string

 

☐

 

partner_state_id

string

 

☐

 

partner_zip

string

Zip

☐

 

payment_id_label

string

 

☐

 

payment_id

string

 

☐

 

provider_code

string

Code

☐

The technical code of this payment provider.

provider_id_label

string

 

☐

 

provider_id

string

 

☐

 

provider_reference

string

Provider Reference

☐

The provider reference of the transaction

reference

string

Reference

☑

The internal reference of the transaction

refunds_count

int32

Refunds Count

☐

 

renewal_allowed

boolean

Renewal Allowed

☐

 

sale_order_ids_nbr

int32

# of Sales Orders

☐

 

sale_order_ids

string

 

☐

 

source_transaction_id_label

string

 

☐

The source transaction of related refund transactions

source_transaction_id

string

 

☐

The source transaction of related refund transactions

state_message

string

Message

☐

The complementary information message about the state

state

string

Status

☑

 

token_id_label

string

 

☐

 

token_id

string

 

☐

 

tokenize

boolean

Create Token

☐

Whether a payment token should be created when post-processing the transaction

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