FUTURE Charge Pricings

future__charges__charge_pricings

Note: This model will be published on or before 2025-06-15.

Note: This documentation table is subject to change up to 2025-06-15

This table works with charges table merged on charges.id = charges__charge_pricings.charge_id

A charge pricing is included in this table if the following condition is met:

  • the associated charge_id is in your charges table

Column Name

Data Type

Description

id

integer

Unique identifier for the charge pricing record

charge_id

integer

Foreign key reference to the charge session

tariff_id

integer

Identifier of the tariff applied to the charge

created_at

timestamp_ntz

Timestamp when the charge pricing record was created

updated_at

timestamp_ntz

Timestamp when the charge pricing record was last updated

currency_id

integer

Identifier of the currency used for pricing

price

float

In original currency.
This column gets regularly updated with the current (and later final) price billed.

reservation_price

float

In original currency.
Price of the fee for reserving the charge point for reservation_min minutes

estimated_price

float

In original currency.
Price estimated based on the amount of KWh, expected starting time, charge rate of the charge point and pricings configured for the charge.Stylized example: 35 KWh expected to be charged on an 11 KW charge point starting at 11.00 would result in a calculation of:

  • 11 KWh charged from 11-12
  • 11 KWh charged from 12-13
  • 11 KWh charged from 13-14
  • 2 KWh charged from 14-15
    Each hour's price is calculated based on the spot price, additionals, tariffs etc. that may be configured for the charge, and summed for the total estimate.

original_price

float

In original currency.
Total price calculated before any adjustments or modifications made by e.g. regulations, bilateral agreements or protections against negative spot prices.

cost

float

In original currency.
The cost value.

payment_method

string

The "business" method by which the payment is done. By "business" method we mean that the payment_method column does not refer to a physical/virtual way of executing a transaction (eg, credit card, apple-pay etc). For that, see payment_method_type.Possible values are:

  • free
  • team-has-fund
  • team-has-auto-refill
  • source
  • payment

payment_method_type

string

The "physical" way of executing a payment. For example: - card - apple-pay - google-pay - free - adyen - payment-terminal - team-wallet

payment_type

string

In the database, it's a path to the respective php Model (Class). In practice, it gives us a way of knowing if it's a:

  • Stripe charge
  • Generic payment session
  • Payter payment session
  • Wallet payment
  • Adyen payment

cost_price_group_id

integer

Identifier of the cost price group applied

estimated_charge_minutes

integer

Estimated duration of the charge in minutes

paying_team_id

integer

Identifier of the team responsible for payment

payment_failed

string

Reason for payment failure if applicable

price_group_id

integer

Identifier of the price group applied to the charge

price_limit

integer

Maximum price limit set for the charge

promotion_code_id

integer

Identifier of any promotion code applied

paying_at

timestamp_ntz

Timestamp when the payment was processed

paying_operator_id

integer

Identifier of the operator receiving the payment

source_failed

string

Reason for source failure if applicable

source_type

string

Type of payment source that source_id is referencing - e.g. Stripe.

sponsor_team_id

integer

Identifier of the team sponsoring the charge if applicable