Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
4.6.4.21 — Payment Mode
2 technical records havebeen identified at this reference: 2 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
GSMESRV touchpoint
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS4.6.4.21 · item PaymentMode.value.PaymentMode
PaymentMode - value PaymentMode
Credit(TRUE),Prepayment(FALSE)
- Object
PaymentMode- Attribute / method
value.PaymentMode- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- Credit(TRUE),Prepayment(FALSE)
Documented touchpoints
- ReadsGCS21j
0x00BFGSMESRV 6.2.9
SMETS4.6.4.21 · item SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode.value
SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode - value
See SMETS
- Object
SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode- Attribute / method
value- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- See SMETS
Documented touchpoints
- ReadsGCS21j
0x00BFGSMESRV 6.2.9
How to read this page
Evidence is kept at record level
A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.