Explore Problems

A borrower reports over $60,000 collected on a loan they characterize as predatory, with proceeds dispersed across multiple companies and no clear accounting of where funds went, and the lender refusing to cancel the balance.

A consumer had a collection account cleared by one credit bureau after a canceled contract, yet another bureau verified the same debt as unpaid months later. This shows collectors and bureaus failing to synchronize dispute outcomes, forcing repeat disputes.

Developers draft the specs and prompts that direct AI coding agents entirely alone; teammates only see the outcome once a PR is opened. The poster wants a collaborative environment where prompts and plans are visible and editable by the team in real time, similar to a prototype shown by GitHub Next.

Consumers disputing collection accounts report that the initial collection notice omits information needed to determine whether the underlying debt is even valid, forcing a manual back-and-forth dispute.

When someone else reports a received transaction as fraudulent, banks can restrict the recipient account access even though the transaction was authorized. Affected customers have no clear, fast way to prove legitimacy and restore access.

A borrower describes a credit union rejecting standard loss-mitigation options during a documented family financial hardship, while compounding junk fees and limiting account access through restrictive online banking design. The pattern reflects a structural failure in how lenders handle hardship-driven loss mitigation.

A debt collector reportedly texted a consumer's father with details of the consumer's debt amount and personal information, a disclosure the consumer says violates the Fair Debt Collection Practices Act's third-party disclosure restrictions.

During a post-forbearance loan modification evaluation, a servicer instructed the borrower to stop payments, then reported them delinquent for three consecutive months. This mirrors a broader pattern of mortgage servicers mishandling loss-mitigation-period credit reporting in violation of federal servicing rules.

A customer who completed the qualifying direct deposit for a $300 new-account bonus received only $100, and the bank has not resolved the shortfall. The gap between advertised and delivered promotional terms remains unexplained.

A customer who moved to a new bank to escape access restrictions found deposits routed to savings instead of the requested checking account, again blocking access to their own money. This points to unreliable deposit-routing controls at the teller/deposit level.

A customer who met the eligibility requirements for a $200 Xfinity promotional gift card received contradictory information from three different representatives, including a fabricated reference number, and had no resolution after repeated follow-up. This reflects inconsistent, unreliable customer service processes at the ISP.

A consumer's detailed CFPB complaint about a disputed debt received a generic collector response that ignored every substantive point raised. This is a structural pattern where collection agencies treat dispute responses as a formality rather than a real review.

Eligible servicemembers requesting SCRA-mandated annual-fee waivers are redirected to a back office with no visible process or timeline, leaving the request unresolved.

A customer disputes a failed transaction, receives a provisional credit, then has it reversed even though the merchant confirms a refund was issued, revealing gaps in how banks weigh dispute evidence.

Cardholders who formally dispute a billing error often find their issuer closes the case without a transaction-specific explanation. This forces consumers into repeated written demands and regulatory complaints just to get a substantive response.

A consumer discovered a credit inquiry and card account from a lender they never applied to, found only by reviewing their credit report. This points to weak identity verification at account origination.

A buy-now-pay-later borrower reports being overcharged on biweekly payments, contacted repeatedly despite do-not-call requests, and having their loan term extended from 6 months to 14 biweekly payments without consent. Reflects weak consent and billing controls in the fast-growing BNPL sector.

Early-stage SaaS builders are unsure whether to use expensive managed cloud databases or cheaper self-hosted Postgres, fearing the operational burden of backups, updates, and monitoring. They want clear, cost-conscious guidance on production-ready hosting without over-engineering too early.

A customer who paid for a premium account tier advertising fraud/mishap coverage up to $25,000 found the protection did not apply when a real issue with a disbursed settlement occurred. The marketed coverage terms and actual claim handling appear misaligned.

A user between jobs is forced by Microsoft Teams to sign in with an old employer's account ID to join unrelated personal or external meetings, since Teams offers no clean way to log out or switch identity, and browser-based joining redirects back to the desktop app. Reflects a structural identity-management gap affecting anyone using Teams across multiple organizational contexts.