# Frequently Asked Questions
What is goodPayments and how does it work? goodPayments is a service that enables your business to accept cryptocurrency payments. For each invoice, the system generates a unique payment address, monitors incoming funds in real time, and automatically forwards them directly to the merchant’s wallet – without storing any funds on its side.
Do I need to complete KYC to use the service? No. Registration and use of the service do not require KYC. You simply fill out the registration form, access your dashboard, and add your own payout address.
Which chains and cryptocurrencies are supported? At the current stage, goodPayments supports payments on the Tron blockchain using TRX and USDT (TRC-20). Additional networks and tokens will be added over time.
How do I create an invoice? An invoice can be created either from the merchant dashboard or via API. You specify the amount, allowed payment currencies, invoice expiration time, optional comments, and – if needed – URLs for webhook notifications and post-payment redirects. Once created, the system generates a payment page and a temporary (one-time) address for receiving funds.
What is a temporary address and why is it needed? A temporary address is a one-time blockchain address generated specifically for an invoice. It is active only for the duration of the invoice and is used solely to receive the payment. It is not intended for storing funds.
What is a static address and how is it different from a temporary one? A static address is a permanent address that stays active until manually deactivated by the merchant. Unlike a temporary address, a static address can receive an unlimited number of incoming payments.
What is a forwarding address and who controls it? The forwarding address is the merchant’s own address where goodPayments automatically forwards the received funds. This wallet belongs entirely to the merchant – the service has no access or control over it.
How are addresses activated and why is activation required? New Tron addresses are inactive by default. To send transactions from them, they must be activated by sending the minimum amount of TRX (0.000001 TRX). * If the payer sends **TRX**, the address is activated automatically. * If the payer sends **USDT**, the system activates the address using the merchant’s Activation Balance.
What fees does the service charge? The processing fee is **6.5 TRX** or **13 TRX**, depending on the payment token and whether the merchant’s payout address contains USDT: * **6.5 TRX** – payment made in TRX OR payment made in USDT and the merchant’s payout address already holds USDT * **13 TRX** – payment made in USDT and the merchant’s payout address does not hold USDT The fee is **not deducted from the payment amount** – it is charged from the merchant’s TRX balance.
Can the service fee be included in the invoice amount? Yes. When creating an invoice, the **«Include fees in the invoice amount»** flag is available. If enabled, the service fee is added to the invoice total and paid by the payer – they pay more than the original order amount. The fee is still debited from the merchant's forwarding balance as usual: the merchant recovers it through the amount included in the invoice.
What happens if the TRX balance runs out? If the merchant does not have enough TRX to cover processing fees, payment handling is paused until the balance is topped up. Existing invoices may fail to process until sufficient balance is restored.
What happens if the payer sends more than the invoice amount? The service processes the entire payment and forwards **the full amount** to the merchant. The invoice is marked as **Overpaid**. Refunds or compensation for overpayments must be handled directly between the payer and the merchant – the service does not split or return excess amounts.
What if the payer sends less than required? The service processes the received amount immediately upon the first incoming transaction and forwards all received funds to the merchant in full. The invoice is marked as **Underpaid**. Any compensation for the shortfall must be handled directly between the payer and the merchant – the service does not participate in this process.
What if the payer sends a different cryptocurrency than specified in the invoice? Such payments cannot be processed. The invoice will be marked as **Error**, since the system cannot reliably identify or handle the unexpected token. Support is required to resolve the issue.
Can a payer use another supported token to pay the invoice? No. Even if the token is supported by the service, the payer must use **only the currencies allowed for that specific invoice** (TRX, USDT, or both). Sending any other token results in an error.
What are AML checks and why are they needed? AML (Anti-Money Laundering) is a screening of assets received in incoming transactions for links to illegal activity. When the AML feature is enabled, every incoming payment is analyzed for risk. The feature can be managed in the merchant dashboard.
What are Mass Payouts and how do they work? Mass Payouts is a tool for sending bulk payments in TRX or USDT TRC-20 to multiple addresses simultaneously. The recipients list and amounts can be uploaded as an XLSX, CSV, or TXT file, or entered manually. The process consists of three steps: input data → preview → confirmation. On the third step, the service generates a temporary payout address – once funds are received, payouts start automatically. The history of all mass payouts is available in the **«Invoices»** section, filtered by address type **«Mailings»**.
How does the Referral Program work? Every merchant has access to a personal referral link. When a new merchant registers through that link, they are attributed to the referrer. A bonus of **5%** is credited for every top-up of the referred merchant's main (forwarding) wallet. The amount is applied immediately to the referrer's forwarding balance and is available for use in the service. Activation-wallet top-ups, invoice payments, and other operations do not count toward the bonus.
Where can I get help with technical issues? For any questions related to goodPayments, contact our support on Telegram: [**@goodp\_manager**](https://t.me/goodp_manager).
--- # 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://goodpayments.gitbook.io/docs/faq/frequently-asked-questions.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.