# Automatic Transaction Processing (ATP) ## Automatic Transaction Processing (ATP) Automatic Transaction Processing (ATP) is a core feature of the Managed Guardian Service (MGS) that allows you to use the platform without managing blockchain infrastructure, wallets, or cryptocurrency. The name ATP is inspired by adenosine triphosphate, the molecule responsible for energy transfer in living systems. In biology, ATP converts energy into a usable form that powers cellular activity. Cells do not interact directly with raw energy sources. Instead, ATP acts as the intermediary that enables energy to be consumed efficiently and reliably. In MGS, ATP plays the same role. ATP converts traditional payment methods such as USD into HBAR, which is then used to power transactions on the Hedera network. This conversion happens seamlessly within the platform, allowing your applications to function without requiring you to manage cryptocurrency directly. *** ### A Simple Way to Think About It You can think of ATP like going to an arcade. Instead of interacting directly with each machine’s internal system, you purchase credits at the front desk. Those credits are then used to play games across the arcade. * You pay in dollars * The system converts that into credits * Each action consumes credits automatically ATP works the same way: * You pay in USD * MGS converts that into HBAR * Each blockchain transaction consumes HBAR behind the scenes You never need to manage the underlying system. You simply use the platform. *** ### What ATP Does With ATP enabled, MGS manages all Hedera-related operations required to run your Guardian environment. This includes: * Converting USD into HBAR * Funding and managing Hedera accounts * Signing and submitting transactions * Handling network fees automatically * Maintaining account balances * Managing key custody through secure infrastructure As a result, you can focus entirely on building policies, managing data, and operating your workflows. *** ### Why ATP Matters Traditionally, working with blockchain-based systems requires: * Creating and managing wallets * Safely storing private keys * Purchasing and holding cryptocurrency * Monitoring balances to avoid failed transactions ATP eliminates all of these requirements. You do not need to purchase, hold, or manage HBAR when ATP is enabled. The platform ensures that all required resources are available when needed. *** ### How Payments Work ATP abstracts the relationship between fiat and Hedera network execution. * You are billed in USD * MGS converts that value into HBAR as needed * Transactions are executed automatically in the background This ensures that your Guardian environment remains continuously operational without manual intervention. *** ### ATP vs Self-Managed MGS supports two modes of operation: #### MGS Managed (ATP) * No wallet setup required * No private key management * No direct interaction with blockchain * Automatic USD to HBAR conversion * Fully managed transaction processing #### Self-Managed * Requires your own Hedera account * Requires private key management * Requires maintaining HBAR balances * Full control over transaction execution ATP is the recommended approach for most users. *** ### Getting Started with ATP ATP is configured at the tenant level and can be enabled by a Tenant Admin during tenant creation. #### Enable ATP 1. Navigate to **Tenants** 2. Click **Add New Tenant** 3. Under **Consumption Management**, select **MGS Managed (ATP)** 4. Complete tenant setup Once enabled, all users within that tenant will operate under ATP. No additional blockchain setup is required. *** #### Free Trial Access ATP is available by default during the free trial with the following conditions: * ATP is enabled automatically * Usage is limited to **Testnet only** * Testnet accounts are funded and managed by MGS This allows you to fully explore the platform without any setup or cost. *** #### Mainnet Usage To use ATP on Mainnet: * An active MGS subscription is required * ATP can be enabled for Mainnet environments * Usage will incur a service cost based on consumption MGS handles the conversion from USD to HBAR and manages all transaction execution on your behalf. *** #### Permissions * Only **Tenant Admins** can create tenants and configure ATP * All users within a tenant inherit the selected configuration *** ### Transitioning to ATP (Self-Managed to ATP) If you are currently using a Self-Managed setup, you can transition to ATP without recreating your Guardian assets. This process involves two steps: * Updating the tenant configuration * Migrating individual user accounts #### Step 1: Enable ATP at the Tenant Level 1. Navigate to **Tenants** 2. Open your tenant 3. Go to **Settings** 4. Change **Consumption Management** to **MGS Managed (ATP)** #### Step 2: Migrate User Accounts 1. Navigate to **Profile** 2. Locate the **MGS Account** section 3. Click **Migrate to ATP** 4. Confirm the migration #### Important Requirements * Your Hedera account balance must be **zero (0 HBAR)** * Any remaining HBAR must be transferred before migration #### Network Behavior **Testnet** * Migration is allowed * Remaining HBAR will be retained within MGS for testnet usage **Mainnet** * Migration requires a zero balance * Migration will fail if balance is greater than zero #### Result * Account type switches to ATP * MGS takes over all transaction management * No further wallet or key management is required *** If you are using ATP and want to return to a Self-Managed setup, you can offboard by switching the tenant configuration and migrating your account keys. This process allows you to move from a fully managed environment to one where you control your own keys and infrastructure. *** #### Step 1: Switch Tenant to Self-Managed 1. Navigate to **Tenants** 2. Open the tenant 3. Go to **Settings** 4. Change **Consumption Management** to **Self-Managed** Once updated, the tenant is configured for Self-Managed usage. *** #### Step 2: Migrate Keys to a Vault Each user must migrate their account to a supported key management solution. 1. Navigate to **Profile** 2. Locate the **MGS Account** section 3. Select **Migrate Keys to Vault** 4. Choose a supported vault 5. Complete the setup and connection process *** #### Supported Vaults * HashiCorp Vault * GCP Secrets * Azure Key Vault *** #### Important Notes * On **Mainnet**, a compatible external vault for Self-Managed is always required * On **Testnet**, onboarding directly into Self-Managed mode allows you to skip external vault setup and use the MGS-managed vault, however: * When **offboarding from ATP to Self-Managed**, the skip vault option is not currently supported * Users must configure and connect their own compatible external vault in order to complete the transition *** #### Why This Matters ATP manages keys and transaction execution on your behalf. When transitioning to Self-Managed mode, you must take full control of key custody. As a result, a properly configured external vault is required during offboarding, regardless of network. *** Transitioning from ATP to Self-Managed requires: * A Tenant Admin to switch the tenant configuration * Each user to migrate their keys to a supported external vault This ensures a secure and controlled transition from managed infrastructure to user-managed key ownership. *** ### Summary ATP converts fiat into blockchain execution power. * USD in * HBAR managed automatically * Transactions executed seamlessly No crypto management\ No key management\ No infrastructure setup Just build, test, and deploy. --- # 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://docs.guardianservice.app/technical-information/automatic-transaction-processing-atp.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.