# Reward Programmes The $VOW ecosystem does not try to recruit End Users itself. That would take too long and cost too much to get to scale. Instead, companies within the ecosystem using technology solutions provided by participating MVDs, are able to provide large organisations (which have a core product or value proposition) the ability to attract new customers and retain existing customers by launching a Reward Programme. It provides them with *ready to go*, fully branded mobile applications and websites, stuffed full of Retailer funded Voucher Currency offers. The host organisation simply performs the marketing function of promoting these offers to its customers, who in turn sign up by linking their payment cards or devices. For organisations which prefer a more integrated solution, APIs are delivered which plug into existing mobile applications and websites, delivering the same high calibre content at scale. By providing these organisations either exclusively, or alongside, existing incentives, these higher value rewards, at more locations than anyone else, $VOW provides an irresistible commercial offering. Because Rewards are always a % of spend, they are desirable and easily understandable for End Users. No new cards or change of behaviour is necessary. End Users simply link their payment cards and devices once and collect automatic rewards at all participating Retailers. They can then use the rewards to discount any product or service offered by participating Retailers. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://vow-2.gitbook.io/white-paper/the-vow-ecosystem/the-worlds-largest-rewards-economy/reward-programmes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.