{"section":"tracks","requestedLocale":"en","requestedSlug":"how-clustered-conditions-work","locale":"en","slug":"how-clustered-conditions-work","path":"docs/en/tracks/payment-solutions/clustered-payment-conditions/how-clustered-conditions-work.md","branch":"main","content":"The Clustered Payment Conditions uses conditions to create client clusters. \n\nThese conditions are based on the data that Master Data saves on a store’s customers.\n\nThe deadline and installment rules will thereby be applied to the consumer(s) that fit the condition(s). \n\n> ❗ **Warning**: you can only create five client clusters per payment condition.\n\nTo configure these clusters, choose a property and then select the parameters to create a cluster.\n\n## Property\n\nThe property is filled with one of the [Master Data](/en/tutorial/entendendo-o-funcionamento-das-consultas-no-master-data--tutorials_4629) fields. Think of these fields as the customer’s information that is stored by VTEX’s system. \n\nAs some fields are native to Master Data, these are created in advance and already exist once retailers gain access to their store’s Admin. However, these fields are not of consequence. \n\nBesides these native fields, retailers can [create any field they want](/en/docs/tutorials/how-can-i-create-a-field-in-master-data). \n\nHence, retailers can create the properties - which can be text, numeric, true/false, by date - that they find most suitable to apply to the special payment condition for each cluster. \n\nAs an example, in the image below, the property used is \"Location\". But other fields that could be used are \"Email\" and \"Phone\".  \n\n## Operator \n\nThe operator is what determines how properties and values segment customers.\n\nIn the image below, the rule will be applied to all customers that correspond to the condition \"Location is New York\". But this is not the only operator option.\n\nIf the store sets the condition to \"Location is not São Paulo\" - with \"is not\" as operator - the payment rule would be applied to all customers within the database whose location is not New York.\n\nThere are many types of operators, depending on the type of property. \n\n### Value\n\nLastly, the final field is filled with a value related to the chosen property. Consider the example where the condition is \"Location is New York\". \n\nThe \"Location\" information alone is not enough for the system to create a cluster. Therefore, we add an additional piece of information, the value, that specifies the chosen property. In layman terms, a value is a characteristic of a property. \n\nIn this case, the system segments customers that correspond to the \"New York\" location and applies the set deadline and installment rule. \n\nIn case there is only one customer that corresponds to the \"Location is New York\" cluster, this rule will only apply to that customer."}