{"section":"tracks","requestedLocale":"en","requestedSlug":"use-cases","locale":"en","slug":"use-cases","path":"docs/en/tracks/payment-solutions/clustered-payment-conditions/use-cases.md","branch":"main","content":"Let’s look at some practical examples of how cluster conditions work.\n\n## Exclusive payment conditions\n\nThe store can apply such a payment condition to only one customer in its database.\nTo this end, you can create a cluster from a property that is exclusive to each customer.\n\n## Custom Fields  \nThe store does not need to only use Master Data’s native fields but can also create the properties that suit the desired business strategies.\n\nLet's think about this from a customer credit perspective, in which a store grants credit to its customers. Every purchase made with this credit generates an invoice that needs to be paid.\n\nNo matter how much the store trusts its clients, unforeseen events happen, and these invoices are not always paid on time.\n\nThe store can segment customers according to the moment they pay such invoices. In this case, the store would create a property called \"Payment\", which would be filled with the following values:\n\n- “in advance”\n- “on-time”\n- “delayed”\n\nThis way, it would be possible to apply a payment condition to only those clients that correspond to the values \"in advance\" and \"on-time\".\n\nCreate two conditions - \"Payment + is + in advance\", \"Payment is on-time\" - and set the deadline and installment rule to apply to both."}