Charge Pricings (🧭 FUTURE)
✨ NEW TABLE - November 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
charges__charge_pricings.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
⚠️ Note table name change: Please note the table name change from
charges__charge_pricingsto standardise table naming
Contains pricing and payment information for charging sessions. This model combines charge pricing data with related financial attributes like costs, payment methods, and pricing details.
SQL: FUTURE__charge_pricings
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| charge_id | INTEGER | References the associated charging session |
| tariff_id | INTEGER | References the applied pricing tariff |
| currency_id | INTEGER | References the currency for the charge price |
| cost_price_group_id | INTEGER | References the cost price group configuration |
| paying_team_id | INTEGER | References the team responsible for payment |
| paying_operator_id | INTEGER | References the operator responsible for payment |
| sponsor_team_id | INTEGER | References the team sponsoring or subsidizing the charge |
| promotion_code_id | INTEGER | References any applied promotional discount code |
| price_group_id | INTEGER | References the price group determining the rate structure |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the pricing record was created |
| updated_at | TIMESTAMP_NTZ | Timestamp when the pricing record was last modified |
| paying_at | TIMESTAMP_NTZ | Timestamp when payment was processed |
| Attributes | ||
| price | NUMBER | Final price charged for the session |
| reservation_price | NUMBER | Price allocated for the charging reservation |
| estimated_price | NUMBER | Projected cost before charging session completion |
| original_price | NUMBER | Base price before any adjustments or discounts |
| cost | NUMBER | Actual cost incurred for providing the charging service |
| payment_method | VARCHAR | Method used for payment (e.g., 'free', 'team_has_funds', 'team_has_auto_refill', or 'payment') |
| payment_method_type | VARCHAR | Further categorization of the payment method (e.g., 'team_wallet', 'free', 'card', 'google_pay', 'apple_pay', 'adyen', etc) |
| payment_type | VARCHAR | Further classification of payment types if applicable (e.g., stripe charge, wallet payment, adyen payment, etc.) |
| estimated_charge_minutes | INTEGER | Projected duration of charging session in minutes |
| payment_failed | BOOLEAN | Indicates whether the payment transaction failed |
| price_limit | NUMBER | Maximum price threshold set for the charging session |
| source_failed | BOOLEAN | Indicates whether the payment source encountered an error |
| source_type | VARCHAR | Classification of the payment source or origin (e.g., stripe source) |
Changes from Last Version
- Note the change in table name
FUTURE__charge_pricingswill becomecharge_pricingsafter the migration as opposed to the table it replaces which wascharges__charge_pricings - No changes were made to the schema
Inclusion Criteria
-- requires that charge_idis among ids in FUTURE__charges
where charge_id in select (id from FUTURE__charges)Data Flow
| Upstream tables | Upstream tables |
|---|---|
FUTURE__charges | none |
Alignment
The charges__charge_pricings table
charges__charge_pricings table-- is downstream of FUTURE__charges which has relaxed inclusion criteria
-- one needs to align FUTURE__charges and use that id list to filter this table
Updated 15 days ago