> For the complete documentation index, see [llms.txt](https://docs.triton.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.triton.one/account-management/payments.md). # Payments Here is a step-by-step guide on how to sign up and process payments on Hel.io via the Triton One customer site: 1. Open your preferred web browser and go to and login to your Triton One account.
2. You will be prompted that your RPC account is still inactive. To activate the account, make a payment via Hel.io web3 payment. You can opt to click on the account name (follow step #3) or click on "here" or the banner on the link (directly proceeds to step #4).
3. You will be routed to the account dashboard, which shows the account is still inactive. Click on the "Inactive Pay Stream" banner.
4. You see the Hel.io Pay Stream page. Click on "Connect Wallet”.
5. Select "Web" or "Extension" if prompted.
6. Tap on "Connect".
7. Click "Approve".
8. Check the settings for duration and price. If all entries are correct click "Pay".
9. The page will show "Approving transaction".
10. Payment is done! To stop the pay stream, click on "Stop Pay Stream".
11. Click "Approve".
12. Payment confirmation is sent via email.
13. Navigate back to . You may need to refresh the page to display the activated RPC account.
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.triton.one/account-management/payments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.