7.8.2 ObjectType definition
| Attribute | Value | ||||
| BrowseName | PaymentServiceType | ||||
| IsAbstract | False | ||||
| References | Node Class | BrowseName | DataType | TypeDefinition | Other |
|---|---|---|---|---|---|
| Subtype of the 0:BaseObjectType | |||||
| 0:HasComponent | Object | 2:Identification | IdentificationType | M | |
| 0:HasComponent | Object | Delivery | PaymentServiceDeliveryType | M | |
| 0:HasComponent | Object | Configuration | BaseConfigurationType | M | |
| 0:HasComponent | Object | PriceInformation | PriceInformationType | M | |
| 0:HasComponent | Object | PaymentModes | PaymentModesType | O | |
| 0:HasComponent | Object | PaymentDevices | PaymentDevicesType | O | |
| 0:HasComponent | Object | Status | PaymentServiceStatusType | M | |
| 0:HasComponent | Object | Components | BaseComponentsType | O | |
| 0:GeneratesEvent | ObjectType | VendingAuditEventType | |||
| 0:GeneratesEvent | ObjectType | ConfigurationChangedEventType | |||
| Conformance Units | |||||
|---|---|---|---|---|---|
| UnattendedRetail PaymentService | |||||
The 2:Identification Object provides Properties describing the identification of the payment service (see 7.2 for details).
The Delivery Object provides the functionality to trigger a delivery by the UI (see 7.9 for details). In order to support a BasketId (see 6.3.2.3), the Delivery Object needs to be of type PaymentServiceBasketDeliveryType (see 7.10 for details).
The Configuration Object provides the configuration information of the payment service (see 7.3 for details).
The PriceInformation Object provides the prices for the selections of the machine engines, managed by the payment service (see 7.11 for details).
The optional PaymentModes Object contains one Object of PaymentModeType per payment mode supported by the payment service. It shall reference at least one Object of PaymentModeType (see 7.13 for details).
The optional PaymentDevices Object contains one Object of PaymentDeviceType per payment device provided by the payment service. It shall reference at least one Object of PaymentDeviceType (see 7.15 for details). Several payment devices may support the same payment mode. For example, there may be the payment mode "Cash" and the payment devices "Coin" and "Bill".
The PaymentModes and PaymentDevices Objects are optional and should be included only if the vending machine charges a price for any of the offered products; otherwise, they should be omitted.
The Status Object provides the status of the payment service and thereby of the overall Vending Machine (see 7.22 for details).
The optional Components Object is the entry point to information about subcomponents of the payment service (see 7.4 for details).
The GeneratesEvent Reference to the VendingAuditEventType indicates that instances will generate Events of that EventType (see 7.27 for details).
The GeneratesEvent Reference to the ConfigurationChangedEventType indicates that an instance may generate Events of that EventType (see 7.29). Such an Event shall be generated when Objects gets added or removed from the Components, PaymentModes or PaymentDevices Objects, or when the values of Variables of the Configuration change. Multiple changes may be reported by a single Event.
Note: Changes of Variables of the PaymentModes like AvailableCredit or the PaymentDevices do not trigger the creation of a ConfigurationChangedEvent. Clients interested in changes of those Variables need to subscribe to them.