SQ* charges

How to read SQ * lines

• Square’s Payments API documentation separates the facilitator prefix, business name and optional identifier. The business name comes from the seller’s dashboard. A number after it can be a seller-supplied identifier; do not assume it is a phone number, universal branch code or customer account.
• The description sent through the payment network can be shortened before it reaches the cardholder. Missing letters therefore require a better record rather than a guess. Ask whether the issuer has a fuller merchant name or reference. The bank’s displayed line and a processor’s underlying record need not be identical.
• SQU*, SQC* and GOSQ.COM remain on this page as existing lookup strings. The primary document inspected here establishes SQ *, not a product mapping for every variant. A Cash App interpretation or a specific transfer route needs its own account evidence; this page does not confirm either from the letters alone.
• Treat the amount as one comparison field. A small or irregular amount does not rule out recurring billing, and a round amount does not establish a subscription. Record the date shown by the bank separately from the purchase date on the receipt. Neither the exact timestamp nor a matching total proves that two records are one payment.
• Illustrative comparison: a $24.50 bank entry and a $24.50 receipt are a candidate match. If the receipt names a different seller or payment method, keep that discrepancy open. This is a constructed example of a lookup question, not a verified customer case or a rule that equal amounts identify a merchant.
• UnknownCharges cannot search Square’s private payment records. Square’s public receipt route redirects to a separate receipt-lookup application that requires JavaScript. Its existence is confirmed, but the form fields and lookup result were not inspected in this review. Opening it takes you to Square; any information supplied there is handled by that service.
• Keep an investigation note that distinguishes what you have established from what is still missing. For example: “The prefix matches a documented Square format; I have not found the seller receipt.” That phrasing preserves the useful clue without presenting the payment as legitimate or accusing a business on the strength of a label.
• A recognized processor name does not decide whether you authorized the charge. The CFPB advises prompt issuer contact for suspected unauthorized card activity. Use the number on your card or your banking app. Record the response and reference rather than waiting for a guessed descriptor identity before reporting the concern.

What to do, in order

1. Save the complete entry Copy the full string, amount, status and bank date. Note the card or account used and retain the statement. Keep an original screenshot or download rather than rewriting the descriptor from memory.
2. Compare an actual receipt Look for the seller’s name, amount, payment method and order reference. If an authorized household card user may have a receipt, ask for that record. Household use is a check, not an established explanation or a measured leading cause.
3. Ask for missing merchant details If no receipt fits, ask the issuer which fuller merchant name and transaction reference it can provide. If you have identified a business, ask it to compare your receipt and payment record; do not send your full card details in an ordinary message.
4. Report suspected unauthorized activity Contact your issuer promptly through its official channel if you did not authorize the payment. State which entry is unrecognized and what you checked. Request the applicable reporting instructions and retain the case reference; this page does not promise provisional credit or a successful dispute.

Quick questions