Charge Start Sources
About
Start sources are essential to identify how a charge was started, for example, charges started via the Monta iOS app will have the app-ios as the startSource, Charges started via partner-api are identified as server-api
This is an ever-growing list, and new values can be added, consumers should implement the necessary fallbacks.
Start Sources Types
| State | Description |
|---|---|
| api | Charge started from the app, this is a legacy value used before api-app and api-ios were introduced. |
| api-web | Charge started from https://map.monta.com. |
| api-app-clip | Charge started by scanning the QR Code seen on public and roaming charges. |
| api-ios | Charge manually swiped to start by the user, in the Monta App, using an iOS device. |
| api-android | Charge manually swiped to start by the user, in the Monta App, using an Android device. |
| hubject-cpo-api | Charge started by a user of another EMSP where Monta is the CPO, The connection with the EMSP goes over the Hubject. |
| hubject-cpo-auth-token | Charge started via charge key by a user of another EMSP on a charge point where Monta is the CPO, The connection with the EMSP goes over the Hubject. |
| hubject-emp-auth-token | Charge started via charge key where Monta is the EMSP on charge point of another CPO, The connection between Monta and the CPO goes over Hubject. |
| ocpi-cpo-api | Charge started by a user of another EMSP where Monta is the CPO, The connection with the EMSP goes over the OCPI protocol. |
| ocpi-cpo-auth-token | Charge started via charge key by a user from another EMSP on a charge point where Monta is the CPO, The connection with the EMSP goes over the OCPI protocol. |
| ocpi-emsp-auth-token | Charge started via charge key where Monta is the EMSP on charge point from another CPO, The connection between Monta and the CPO goes over OCPI. |
| cpi-auth-token | Charge started by scanning the RFID charge key. |
| vehicle-vid | Charge started by vehicle authentication. |
| instant-start | Charge started automatically via the autoStart functionality, the charge starts once the cable is plugged in. |
| instant-start-unknown-tag_id | Charge started by plugging in the vehicle but, authorization was not performed. |
| auto-start-instant | Charge started via AutoStart functionality, this needs to be enabled, and the charge starts once the cable is plugged in. |
| payter_start | Charge started via Payter terminal. |
| payter_rfid_start | Charge started via Payter terminal authorized via RFID card. |
| reschedule | Charge started via rescheduled action. |
| auto-start-smart | Charge started via the autoSmartCharge functionality, using a charging profile based on setup parameters before the user enables this feature. |
| auto-start-schedule | Charge started via the scheduled functionality. |
| server-api | Charge started via Partner-Api. |
| portal | Charge started via Portal. |
| system-missing-payment | Charge that is missing the relation between an idTag to a payment source. |
| transaction-syncer-owner | Charge was started and completed while the unit was in touch with the Monta backoffice syncs values once the connection was re-established. |
| charging-rule | Charge started by a set of defined charge rules. |
| unknown | Unknown start source, This value will be assigned when none of the above is possible. |
Updated 11 months ago