pollybuzz.buzz

PolyBuzz Refund Requests: Match the Receipt Before You Submit

Prepare a clear PolyBuzz purchase record, route an Apple-billed request correctly, and distinguish a refund request from cancellation or approval.

Quick answer

Match the purchase to its receipt and billing provider before requesting a refund. Explain the transaction and issue accurately, then use that provider’s process. PolyBuzz’s terms restrict refunds subject to applicable law; neither cancellation nor submitting a request guarantees approval.

A PolyBuzz refund request should identify a particular purchase, not just the app name. Start with the receipt, the billing provider and a truthful description of the issue. Those details determine where a request belongs and what evidence can be checked.

The PolyBuzz Terms, section 9.9, describe restrictive refund terms subject to applicable law. This guide does not decide your legal entitlement or promise that a store or provider will approve a request.

Build a four-part purchase record

Keep the following privately:

  1. Transaction identity: receipt or order reference, date, amount and currency.
  2. Billing identity: the company that billed you and the account used for the purchase.
  3. Problem: what happened, when you noticed it and what outcome you are requesting.
  4. Prior action: any cancellation acknowledgment, support case or earlier refund decision concerning this same purchase.

Use the original transaction date rather than estimating from when you noticed the statement. If there are two similar charges, give each its own line. A vague statement that you were “charged twice” cannot show whether the entries are two purchases, two accounts or a different billing situation.

Do not send a full card number, password or sign-in code. Redact unrelated purchases from a screenshot. Keep enough information for the official channel to identify the transaction without turning a support request into an unnecessary disclosure of your financial history.

Use the provider that actually billed the purchase

For an Apple-billed transaction, Apple’s refund guidance directs eligible requests through its Report a Problem service. Match the Apple Account and purchase shown on the receipt. Apple says a pending charge cannot yet be submitted as a refund request through that process.

For Google Play billing, begin with Google’s subscription and refund guidance and follow the route for the purchase in your account. If another company billed you, its process applies instead. Installing an app from a store does not prove that the store handled every payment associated with that service.

For example, imagine one receipt covers a recurring subscription and another covers a separate purchase. Canceling renewal on the first does not explain what should happen to the second. Keep the two records separate and state which transaction your request concerns.

Describe the issue without inventing a category

Choose the reason that accurately matches what happened. Do not select “unauthorized” merely because you regret a purchase or because a refund seems easier under that label. If the available reasons do not fit, use the official support option to explain the facts.

A useful message can be short: “I am asking about order [reference], billed on [date] by [provider]. The issue is [specific factual description]. I have already [relevant prior action]. Please confirm the process and any additional evidence required.” Submit identifying details only inside the appropriate official channel.

Track three different states

Requested means the provider received your question. Approved or declined is the decision. Returned concerns the funds after approval. Keep each acknowledgment with its date; do not describe a submitted form as money already refunded.

If your separate aim is to stop renewal, complete and verify that action too. A refund request should not be assumed to cancel future billing. Preserve access to the records you need until the purchase question is resolved, and avoid repeating identical requests while an existing case is awaiting a response.

Sources and verification

This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.