> For the complete documentation index, see [llms.txt](https://openvpp.gitbook.io/openvpp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openvpp.gitbook.io/openvpp-docs/technology-overview/device-payment-rails-and-stablecoin-customization-service.md). # Device Payment Rails & Stablecoin Customization Service OpenVPP is creating the payment rails to enable utilities to connect to, account for, and settle device transactions as if they were their own electric meters. By leveraging the on-chain connectivity OpenVPP provides, combined with stablecoin and price oracle infrastructure, OpenVPP can create trusted stablecoins for customized utility use cases. \ \ To help achieve this vision, OpenVPP has partnered with a leading stablecoin provider (to be announced immediately after launch) to bring dollar‑denominated, 24/7 liquidity directly onto energy payment rails. \ \ Utilities can settle surplus generation from rooftop solar or pay out demand‑response incentives within seconds, eliminating multi‑day clearing cycles and charge‑back risk. Because the stablecoin-based solution is natively cross‑chain, the same stablecoin balance can move between public chains, private consortia networks, or a utility’s preferred side‑chain without friction, which is crucial for multinational grid operators. By puggling these tokens into OpenVPP’s purpose-built oracles and encapsulating those assets in smart contracts that track kilowatt‑hours, carbon intensity, or time‑of‑use windows, OpenVPP lets participants denominate value in the unit that best aligns with their program objectives while still preserving a 1:1 stablecoin reserve. OpenVPP has also partnered with a leading electric utility provider (to be announced immediately after launch) that providers validated metering, measurement & verification (M\&V) of total and disaggregated energy to generated utility bills. The time between production and consumption is a math equation that equates to net output, putting the end-customer at a minimum of a 30-day delay on what their electric utility bill will consist of in-terms of renewable energy production and utility program participation. This is why OpenVPP is providing an on-chain oracle pricing mechanism that can peg to an electric utility use-case specific stablecoin to provide accurate and instantaneous crediting and debiting based on the exact use case. For example:\ \ A customer with roof-top solar is enrolled within a Net-Energy-Metering tariff within their regulated utilities distribution territory. This person would typically receive a bill at the end of the month which is inclusive of their energy credits, which would then get applied to the following month’s utility bill. With OpenVPP, this renewable energy prosumer can now receive stablecoins pegged to their credit, informed by the real-time rate of renewable energy production and export into their local grid’s distribution system. This token might be called $SOLAR, $NEM, or even be $UtilityXYZ based on their grid provider’s preference. This use-case specific stablecoin would settle in real-time and earn APY as long as it’s held within the utility account holders on-chain wallet account. The owner of the roof-top solar will be free to off-ramp it via OpenVPP’s regulated payment rails. Such other use-cases might exist for Demand Response or $DR, or even Virtual Power Plants or $VPPs, based on their local utilities rate-base preference and approval. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://openvpp.gitbook.io/openvpp-docs/technology-overview/device-payment-rails-and-stablecoin-customization-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.