payment.token: fields, relations and API
The payment.token model ("Payment Token") is a persistent model declared by the Payment Engine module, then extended by 8 other modules. It exposes 23 fields, 17 of them declared directly on the model; 5 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.
Model identity
- Technical name
payment.token- Label
- Payment Token
- Type
- Persistent (models.Model)
- SQL table
payment_token- Origin module
- Payment Engine (
payment) - Extended by
- payment_adyen, payment_authorize, payment_demo, payment_flutterwave, payment_mercado_pago, payment_razorpay, payment_stripe, website_sale
- Default order (_order)
partner_id, id desc
Model fields
17 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
23 of 23 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| active | Active | boolean | |
| adyen_shopper_reference | Shopper Reference The unique reference of the partner owning this token | char | read-only added by Payment Provider: Adyen ( |
| authorize_profile | Authorize.Net Profile ID The unique reference for the partner/token combination in the Authorize.net backend. | char | added by Payment Provider: Authorize.Net ( |
| company_id | Company | many2one | related: |
| demo_simulated_state | Simulated State The state in which transactions created from this token should be set. | selection | Values: added by Payment Provider: Demo ( |
| flutterwave_customer_email | Flutterwave Customer Email The email of the customer at the time the token was created. | char | read-only added by Payment Provider: Flutterwave ( |
| mercado_pago_customer_id | Mercado Pago Customer | char | read-only added by Payment Provider: Mercado Pago ( |
| partner_id | Partner | many2one | required |
| payment_details | Payment Details The clear part of the payment method's payment details. | char | |
| payment_method_code | Payment Method Code | char | related: |
| payment_method_id | Payment Method | many2one | requiredread-only |
| provider_code | Provider Code | selection | related: |
| provider_id | Provider | many2one | required |
| provider_ref | Provider Reference The provider reference of the token of the transaction. | char | required |
| stripe_mandate | Stripe Mandate | char | read-only added by Payment Provider: Stripe ( |
| stripe_payment_method | Stripe Payment Method ID | char | read-only added by Payment Provider: Stripe ( |
| transaction_ids | Payment Transactions | one2many | inverse: |
| create_date | Created on | datetime | read-onlyautomatic |
| create_uid | Created by | many2one | read-onlyautomatic |
| display_name | Display Name | char | read-onlycomputedautomatic |
| id | ID | integer | read-onlyautomatic |
| write_date | Last Updated on | datetime | read-onlyautomatic |
| write_uid | Last Updated by | many2one | read-onlyautomatic |
Relations
Models linked from this model
- payment.method: payment_method_id
- payment.provider: provider_id
- payment.transaction: transaction_ids
- res.company: company_id
- res.partner: partner_id
Fields of other models pointing here
- account.payment: payment_token_id, suitable_payment_token_ids
- account.payment.register: payment_token_id, suitable_payment_token_ids
- payment.transaction: token_id
Reading this model through the API
Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.
curl -X POST "https://your-instance.odoo.com/json/2/payment.token/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["partner_id","payment_method_id","provider_id","provider_ref","company_id"],"limit":5}'import requests
BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}
res = requests.post(
f"{BASE_URL}/payment.token/search_read",
headers=headers,
json={"domain": [], "fields": ["partner_id","payment_method_id","provider_id","provider_ref","company_id"], "limit": 5},
)
res.raise_for_status()
print(res.json())- External API access requires Odoo's Custom plan.
- XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
- The access rights and record rules of the key's user apply.
Cite this tool
Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.
<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/payment-token">payment.token (Odoo 19.0)</a>Sources
Data verified on September 23, 2026 · Odoo 19.0 Community
Have an Odoo project, or want to put your ERP to work with AI? Let's talk
Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.