CRYPTOCURRENCY PAYMENTS, ACTIVATION AND REFUNDS POLICY

1. Scope, agreement, and definitions

1.1. This Policy forms part of the Terms of Service at /terms and applies to Checkout, invoices, blockchain transfers, payment detection, confirmations, activation, fixed access periods, payment errors, online withdrawal, refunds, disputes, and text-only payment-support records.

1.2. By initiating a purchase or sending a cryptocurrency payment, the User confirms that the User is at least 18 years old, has legal capacity to make the purchase, may lawfully use the Service and the selected payment method, and has reviewed the binding Checkout information.

1.3. If a material purchase term displayed at Checkout conflicts with a general statement in this Policy, the specific Checkout term controls for that purchase only, except that Checkout cannot remove a mandatory legal right or impose a recurring payment.

1.4. Nothing in this Policy excludes, restricts, or waives a right, remedy, guarantee, liability, refund, withdrawal right, or consumer protection that cannot lawfully be excluded or restricted.

• Checkout: The final purchase interface showing the price, cryptocurrency asset, blockchain network, destination address or payment route, access period, invoice expiration, payment status, material limitations, and confirmation that the purchase is one-time and non-recurring.
• Invoice: A unique payment request or reference generated for a particular purchase, Account or session, amount, asset, network, and payment window.
• Paid Access: Access to the features and for the fixed period displayed at Checkout. Paid Access does not transfer ownership of the Service, an AI Character, a model, software, data, or Service Content.
• Required Amount: The exact amount of the exact cryptocurrency asset shown as payable for the Invoice.
• Supported Network: The exact blockchain network displayed for the Invoice. A token with the same name or ticker on another network is not the same payment method.
• Confirmation: A blockchain confirmation or another reliable settlement signal required before the payment is treated as sufficiently final for activation.
• Activation: The moment Aefia records the purchase as paid and enables the corresponding Paid Access.
• Payment Record: The Invoice identifier, transaction hash, asset, network, amount, timestamps, confirmation status, activation status, access period, refund status, and related reconciliation or support information.
• Durable Medium: A format that allows the User to store information addressed personally to the User, access it for an adequate period, and reproduce it unchanged, such as an email or a downloadable receipt that Aefia cannot unilaterally alter after delivery.
• Withdrawal Function: The prominently displayed online function labelled “Withdraw from contract here” or an equally unambiguous phrase, made available throughout an applicable withdrawal period and followed by a separate confirmation step.

2. Checkout, pricing, and one-time purchase

2.1. Before the User sends funds, Checkout must clearly display the total amount payable, accepted cryptocurrency asset, Supported Network, destination address or payment route, fixed access period, Invoice expiration, material feature limitations, and the fact that the purchase does not renew automatically.

2.2. The current primary payment asset is USDT. Only the exact asset, token contract where relevant, and Supported Network displayed for the particular Invoice are accepted. A reference to USDT does not mean that every network carrying a token with that ticker is supported.

2.3. The User must review the complete destination address, network, asset, token contract where relevant, amount, memo or tag where applicable, and Invoice expiration before authorizing the transfer. Browser autofill, wallet address books, copied data from an earlier Invoice, search-engine results, AI Character messages, advertisements, and third-party messages are not authoritative payment instructions.

2.4. A price is binding only during the payment window stated at Checkout. Aefia may change future prices, access periods, plans, or supported payment methods, but a later change does not alter a transaction validly completed under an unexpired Invoice.

2.5. Optional extras, donations, tips, recurring mandates, and preselected paid additions are not part of the current payment model. No payment beyond the amount affirmatively authorized for the displayed Invoice may be initiated by Aefia.

2.6. Where applicable consumer law requires pre-contract information, a request for immediate performance, an acknowledgment concerning withdrawal rights, an online Withdrawal Function, or confirmation on a Durable Medium, Checkout and the post-purchase process must provide the required information and obtain every required separate affirmative action.

3. Sending and confirming a cryptocurrency payment

3.1. The User initiates the blockchain transfer through a wallet, exchange, custodian, payment provider, or other third-party service chosen by the User. Aefia does not control that third party's availability, identity verification, withdrawal limits, fees, processing times, security, or terms.

3.2. A payment is not complete merely because a wallet displays “sent,” “pending,” or a locally generated transaction hash. Aefia may wait until the transaction is visible on the Supported Network, transfers the Required Amount to the correct destination, is associated with the correct Invoice, and has reached the number or quality of Confirmations reasonably required for that network and transaction.

3.3. Confirmation requirements may vary by blockchain conditions, asset, payment provider, transaction size, security risk, chain reorganizations, outages, congestion, and other settlement factors. The current status displayed by Checkout or payment support controls for the specific transaction.

3.4. Aefia may delay activation while a transaction is unconfirmed, replaced, reversed, invalidated, associated with conflicting transfers, affected by a chain reorganization, or reasonably requires payment reconciliation or security verification.

3.5. Aefia will never request a seed phrase, private key, full wallet or exchange password, one-time authentication code, remote access to the User's device, or complete payment credentials. A person requesting any such secret is not following Aefia's legitimate payment-support procedure.

• Authoritative payment details: Only the live Checkout for the specific Invoice and an authenticated payment-support response relating to that Invoice.
• Blockchain visibility: A transaction hash may be used to locate and verify a payment but does not by itself prove that the correct asset, network, amount, and destination were used.
• Third-party delays: A wallet or exchange may mark a withdrawal complete before the Supported Network has provided sufficient settlement confirmation.
• No cash or card payment: The current Service does not treat bank-card, bank-transfer, cash, gift-card, or unofficial person-to-person transfers as payment unless Checkout expressly introduces and identifies that method.

4. Activation and fixed-term access

4.1. Paid Access is normally activated after the correct transaction is detected, sufficiently confirmed, matched to the correct Invoice and Account or session, and accepted by the payment and access systems.

4.2. The fixed access period begins at Activation unless Checkout clearly states a later start time. The time at which the User sent the transaction does not start the access period unless Checkout expressly states otherwise.

4.3. If a correct payment is confirmed but automatic activation fails, the User should submit the Invoice identifier and transaction hash through /feedback. After verification, Aefia may activate access, restore the missing time, extend the access period, provide an equivalent remedy, or issue a refund where required.

4.4. Temporary blockchain congestion, provider latency, reasonable confirmation requirements, or a brief reconciliation review does not by itself constitute permanent non-supply. This does not permit Aefia to delay supply beyond a mandatory deadline or a time expressly stated as essential at Checkout.

4.5. Aefia may correct an erroneous activation that resulted from a reversed, invalid, double-spent, unpaid, underpaid, fraudulent, or mismatched transaction. Any correction remains subject to mandatory consumer rights and a good-faith review of available evidence.

• Activation record: Aefia must record the Invoice, transaction, Activation time, fixed access period, access expiration, and any subsequent extension, termination, or refund required for reconciliation and support.
• Receipt: After Activation, the User must receive or be able to download a confirmation on a Durable Medium showing the purchase, amount, asset, network, transaction or Invoice reference, fixed access period, Activation time, non-recurring status, applicable withdrawal information, and the text of any immediate-performance request or withdrawal acknowledgment.
• No ownership transfer: Activation grants only the limited fixed-term access described at Checkout and in the Terms of Service.

5. Incorrect, late, missing, or duplicate transfers

5.1. Cryptocurrency transfers can be difficult or impossible to reverse. The outcome of a payment error depends on whether Aefia or its provider controls the destination, supports the asset and network, can identify the transfer, can technically recover the funds, and may lawfully process a recovery or refund.

• Wrong destination address: Funds sent to an address not displayed for the Invoice and not controlled by Aefia or its payment provider may be permanently lost. Aefia cannot recover funds it never received or controlled.
• Wrong blockchain network: A token sent on a network other than the Supported Network may not be detected or accessible. Recovery is not guaranteed even where the destination appears similar across networks.
• Wrong asset or token contract: A different token, bridged asset, wrapped asset, counterfeit token, unsupported contract, or similarly named asset does not satisfy the Invoice unless Checkout expressly accepts it.
• Missing or incorrect memo or tag: Where a memo, destination tag, reference, or similar identifier is required, omitting or altering it may prevent automatic matching and require textual verification through payment support.
• Underpayment: A transfer below the Required Amount does not complete the purchase. Checkout may permit a timely top-up. If it does not, Aefia may request additional payment, decline activation, or return a recoverable amount where appropriate and legally required.
• Overpayment: A transfer above the Required Amount does not purchase extra access unless Checkout expressly says so. Aefia will use reasonable efforts to identify a material excess and, after verification, may return it or apply another remedy agreed with the User. If the external cost of returning a small excess would consume most or all of it, Aefia will seek the User's instructions where reasonably practicable.
• Duplicate payment: If the same intended purchase is paid more than once, the User should report every transaction hash. After verification, Aefia may reverse unused duplicate access, apply the duplicate amount to a separately requested purchase only with the User's agreement, or refund the duplicate transaction, subject to mandatory law and actual use.
• Expired Invoice or late transfer: A transaction first broadcast, received, or confirmed after the Invoice expiration may not activate automatically and may be reviewed using the price, asset, network, availability, and access terms applicable to the expired Invoice.
• Insufficient network fee: A transaction that remains unconfirmed because the sending wallet selected an insufficient fee is not treated as settled until it is confirmed or otherwise accepted by Aefia's payment system.
• Exchange or custodial transfer: The User is responsible for obtaining the actual blockchain transaction hash and for ensuring that any refund address can receive the exact asset on the Supported Network. An exchange deposit address may expire, require a memo, or reject third-party refunds.
• Aefia or Checkout error: If the live Checkout displayed an incorrect destination, asset, network, amount, or access term and the User reasonably followed that information, Aefia will investigate and provide the remedy required by applicable law, which may include activation, correction, replacement, price reduction, or refund.

5.2. Where recovery of a User-caused incorrect transfer requires exceptional technical work, an external provider, or an additional blockchain transaction, Aefia may offer recovery subject to the User's prior express agreement to actual, reasonable, itemized, and disclosed recovery and network costs, but only where applicable law permits. No fee is charged merely for submitting or reviewing a standard payment-support request.

5.3. Aefia is not required to attempt a recovery that would be technically impossible, unsafe, unlawful, disproportionate, likely to compromise another person's funds, or unsupported by the relevant wallet, network, token, or provider.

6. Cancellation and statutory withdrawal rights

6.1. Outside a mandatory withdrawal right or an express Checkout guarantee, Aefia does not promise a general change-of-mind refund after Paid Access has been activated.

6.2. A consumer in a jurisdiction providing a cooling-off period may submit an unequivocal withdrawal statement through the Withdrawal Function, the Payment Support Form, or /feedback before the applicable deadline. No special wording is required where applicable law permits any clear statement of the decision to withdraw.

6.3. Where an applicable withdrawal right exists for a distance contract concluded through an online interface, Aefia must make a prominently displayed and easily accessible Withdrawal Function continuously available throughout the withdrawal period. It must allow the User to identify the User, identify the purchase, specify an electronic confirmation method, and submit the statement through a separate function labelled “Confirm withdrawal” or an equally unambiguous phrase.

6.4. After the User confirms an online withdrawal, Aefia must send acknowledgment without undue delay on a Durable Medium, including the submitted statement and its date and time. A timely online statement is treated as submitted within the withdrawal period when the User confirms it before that period expires.

6.5. Where the User asks Aefia to begin a paid digital service during an applicable withdrawal period, Checkout may require a separate express request for immediate performance and a separate acknowledgment of the legal consequences. Those controls must not be preselected, bundled with payment accuracy, or combined with unrelated consent.

6.6. Where applicable law treats the purchase as a service supplied over time, a User who validly withdraws after expressly requesting immediate performance may be responsible only for a proportionate amount corresponding to the service lawfully supplied before the withdrawal request. The right may be lost after full performance only where applicable law permits and the required prior request, acknowledgment, and confirmation were properly obtained.

6.7. Where applicable law instead treats a particular item as digital content not supplied on a tangible medium, any loss of the withdrawal right requires every condition imposed by that law, including any required prior express consent, acknowledgment, and contractual confirmation. Merely starting a chat, passing the age gate, accepting the Terms, or sending cryptocurrency is not treated as a waiver by itself.

6.8. If Aefia failed to provide legally required withdrawal information, failed to make a required Withdrawal Function available, or failed to obtain a legally required immediate-performance request or acknowledgment, the User retains the rights, extended periods, and cost protections provided by applicable law.

6.9. On a valid withdrawal or termination, Aefia may disable the affected Paid Access and the User must stop using any paid feature to the extent required by applicable law. Locally stored private chat history remains controlled through the User's browser and is not itself a paid access entitlement.

6.10. A withdrawal request does not require the User to disclose a seed phrase, private key, wallet password, exchange password, one-time authentication code, or any file or media upload.

7. Service failures, mandatory remedies, and refunds

7.1. If Paid Access is not supplied, is materially different from the binding Checkout description, or materially fails to conform to applicable contractual or statutory requirements, the User should report the issue and allow a reasonable opportunity to investigate and restore conformity where the law permits.

7.2. Depending on the nature and severity of the problem, applicable law, and technical feasibility, the available remedy may include activation, restoration, correction, a reasonable substitute accepted by the User, an extension of the access period, Account credit accepted by the User, a proportionate price reduction, termination, or refund.

7.3. Aefia will not require a User to accept Account credit, replacement access, or another non-monetary remedy where applicable law entitles the User to a monetary refund and does not permit substitution without agreement.

7.4. A brief interruption, planned maintenance, a disclosed fair-use limit, an unsupported device, a User-side network failure, an AI reply the User dislikes, ordinary probabilistic model behavior, or a restriction caused by the User's material breach does not automatically create a refund right. A sustained or material failure affecting the paid service will be assessed in light of the Checkout description, duration, severity, available restoration, and mandatory law.

7.5. Where a fixed-term service was conforming for part of the period and materially non-conforming for another part, a price reduction or refund may be calculated proportionately by reference to the affected period and decrease in value, unless applicable law requires a different calculation.

7.6. Where the User validly terminates for material non-supply or non-conformity, Aefia will refund the amount required by applicable law, including any prepaid amount attributable to a remaining period that will no longer be supplied.

7.7. An approved voluntary refund is normally initiated within 14 calendar days after approval and after Aefia has the minimum information required to send it safely. A statutory reimbursement must be initiated without undue delay and within every applicable mandatory deadline. Blockchain confirmation time after valid broadcast is outside Aefia's direct control.

7.8. A refund is initiated when the refund transaction is validly broadcast to the agreed compatible network and destination. Aefia must provide the refund transaction hash or equivalent confirmation where available. A refund must not be treated as completed internally before the transaction is broadcast.

• Ordinarily refundable: Verified duplicate payment; verified material overpayment; confirmed payment that Aefia cannot match or activate despite sufficient evidence; qualifying non-supply or material non-conformity; a valid statutory withdrawal; or another refund required by law or expressly promised at Checkout.
• Ordinarily not refundable by itself: A change of mind after activation outside a mandatory withdrawal right; dissatisfaction with a lawful AI response; failure to use Paid Access; forgetting the expiration date; loss of locally stored chat history; User-side browser, device, wallet, exchange, or network problems; or market-price changes in the cryptocurrency.
• Case-by-case review: Wrong network, wrong token, omitted memo, underpayment, expired Invoice, claimed unauthorized wallet use, suspected compromise, prolonged outage, enforcement action, or any technically recoverable User error.
• No arbitrary forfeiture: The Operator will not retain a verified refundable amount merely because payment was made in cryptocurrency. Any refusal or deduction must have a contractual, technical, security, evidentiary, or legal basis.

8. Fraud, policy violations, and access restrictions

8.1. Aefia may delay activation, restrict Paid Access, preserve relevant payment records, or decline a payment or refund request where reasonably necessary to investigate suspected fraud, a stolen or unauthorized transaction, false payment evidence, double spending, manipulation of an Invoice, Account compromise, binding legal restrictions, abuse of the refund process, or a material violation of the Terms or Acceptable Use Policy at /acceptable-use.

8.2. The User must not submit a fabricated or altered transaction hash, wallet record, blockchain-explorer link, payment-provider message, refund address, identity statement, or ownership claim; seek duplicate activation or reimbursement for one transaction; knowingly exploit an activation or reconciliation error; or use funds that the User is not authorized to transfer.

8.3. A restriction or termination caused by the User's material breach does not create a voluntary refund right. This does not eliminate a refund or other remedy that applicable law makes mandatory.

8.4. Aefia may request proportionate textual information reasonably necessary to verify the Invoice, transaction, Account or session, safe reply contact, control of a refund address, or authority to act. File and media uploads are not supported. Government identification should not be requested unless reasonably necessary for a specific legal obligation or material fraud risk and permitted by applicable law.

8.5. Where a transaction or refund cannot lawfully be processed, Aefia may suspend the transaction while seeking a lawful resolution and may provide information to a competent authority or provider where legally required.

8.6. A User may challenge a payment-related enforcement decision through /feedback and should provide the decision or support reference and material evidence.

9. Network fees, exchange rates, taxes, and refund method

9.1. The User's wallet, exchange, custodian, blockchain, or payment provider may charge withdrawal, network, conversion, spread, custody, or service fees. Those third-party charges are not received or controlled by Aefia unless Checkout expressly says otherwise.

9.2. Checkout must show the total amount payable to Aefia. Any tax or mandatory charge collected separately by Aefia must be disclosed before the User sends payment. The User remains responsible for taxes or reporting obligations imposed directly on the User by the User's jurisdiction, wallet, exchange, or activity.

9.3. Cryptocurrency values may fluctuate. A price change after a valid payment does not by itself increase or reduce the purchased access period and does not create a refund right.

9.4. Unless applicable law requires another method or the parties expressly agree otherwise without additional cost to the User, an approved refund is ordinarily sent using the same cryptocurrency asset and blockchain network as the accepted payment, to a verified compatible address supplied or confirmed by the User.

9.5. The refund amount is determined by the binding Checkout record, the amount actually received, the reason for the refund, the portion of service supplied, and applicable law. The User is not entitled to a speculative gain because the cryptocurrency's exchange value changed after payment, and Aefia may not reduce a mandatory refund merely because the cryptocurrency's exchange value changed.

9.6. A mandatory refund must not be reduced by a fee where applicable law requires reimbursement without cost to the consumer. For a voluntary recovery of a User-caused incorrect transfer, Aefia may deduct only actual, reasonable, itemized, previously disclosed external recovery or network costs expressly accepted by the User and permitted by law.

9.7. The User must provide a refund address that supports the exact asset and network. Aefia is not responsible for a refund lost because the User supplied an incorrect, expired, incompatible, custodial, or memo-dependent address after receiving a clear verification request, except to the extent applicable law provides otherwise.

9.8. Aefia will not ask the User to pay an additional “release fee,” “verification deposit,” “tax deposit,” or similar advance payment merely to receive an approved refund. A request of that kind should be treated as suspicious and reported through /feedback.

10. Payment support, evidence, records, and changes

10.1. Payment, Activation, withdrawal, and refund requests must be submitted through the text-only Payment Support Form on this page, the online Withdrawal Function where applicable, or the official contact mechanism at /feedback. An AI Character chat, advertisement, social-media message, or blockchain memo is not an official support channel.

10.2. The User should provide the Invoice identifier, transaction hash, exact asset and network, amount, approximate transfer time, relevant Account or session reference, safe reply contact, and a concise textual explanation. A public blockchain-explorer URL or textual description of the wallet or exchange record may support the request but does not replace an independently verifiable transaction hash.

10.3. Provide a refund address only after the form or an authenticated support response requests one. File and media uploads are not supported. Never provide a seed phrase, private key, complete wallet or exchange password, one-time authentication code, or remote device access.

10.4. Aefia aims to acknowledge or substantively respond to a complete standard payment-support request within approximately 15 days, depending on urgency, blockchain conditions, provider involvement, verification, complexity, and mandatory legal deadlines. This operational target does not extend a shorter statutory deadline or delay an acknowledgment required without undue delay.

10.5. Payment Records may be retained as described in the Privacy Policy at /privacy for activation, reconciliation, accounting, fraud prevention, support, statutory rights, legal claims, and compliance. Public blockchain transactions are maintained independently and cannot be erased by Aefia.

10.6. Aefia may update this Policy for legal, security, blockchain, provider, technical, operational, or product reasons. An update will not retroactively create a recurring payment, alter a completed valid purchase, remove an accrued mandatory right, or change the governing policy version stored with an existing purchase.

10.7. The current Policy should be read together with the Terms at /terms, Privacy Policy at /privacy, Cookie Policy at /cookies, Acceptable Use Policy at /acceptable-use, Copyright and Illegal Content Policy at /copyright, and AI Content and 2257 Compliance Statement at /2257.

• Payment support: /feedback
• Payment and refund policy: /payments-refunds
• Privacy and payment records: /privacy
• Content or advertisement reports: /feedback
• Service: https://aefia.com