Customers represent end users of your platform—whether individuals or businesses—who are issued a payment alias under your namespace. These aliases act as persistent identifiers that your users can use to send and receive payments across the Paylias network. Each customer is created and scoped within a namespace, and upon registration, they can choose a unique alias. This alias cannot be modified once issued and must be globally unique within the namespace. It serves as the primary reference for all transaction activity, enabling seamless routing of payment instructions between different participants in the network. Customers onboarded to Paylias can represent either individuals or businesses. If the customer is a business, you are required to assign them a valid 4-digit Merchant Category Code (MCC) that accurately reflects the nature of their business. Importantly, Paylias does not perform any KYC (Know Your Customer) or KYB (Know Your Business) checks. It is your responsibility as the platform operator to ensure that any customers you onboard meet your internal risk, compliance, and regulatory requirements. Paylias assumes that all participants have been properly vetted by your infrastructure before they are issued an alias. You can think of a customer in Paylias as analogous to a cardholder being issued a payment credential like a credit or debit card, where the namespace acts similarly to a BIN (Bank Identification Number). When a payment is submitted or admitted, Paylias uses the alias to resolve which namespace the customer belongs to, and routes the transaction accordingly.