Developer Rebuilds Entire Billing Stack After Stripe Bans PDF Forensics Tool

·7 views

A Finnish developer behind htpbe.tech, a PDF-editing detection tool, had their Stripe account terminated after the platform's automated system apparently flagged the business as high-risk due to keywords like 'fake document detection.' Stripe's appeal process returned a rejection in eight seconds, with no meaningful human review despite the developer submitting tax records, company registration, and other legal documentation. Following the ban, Stripe refunded the last five days of customer payments, leaving the developer to resolve those transactions independently. The developer migrated to EU-based payment processor Mollie, finding that one-off payments were straightforward but rebuilding subscription billing — including mandates, proration, VAT, invoicing, and dunning — took roughly two weeks of manual development. The experience highlighted that Stripe functions as a full billing platform rather than a simple payment processor, meaning a forced migration involves far more than switching a payments API.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Four Silent XLSX Export Bugs Found in a Jira Forge Invoice App

A development team building a resource management app on Atlassian Forge discovered four data-integrity bugs during a focused QA review of their XLSX invoice export feature. None of the bugs triggered errors or visibly corrupted the spreadsheet, making them especially difficult to detect. One bug caused date-only fields to silently carry phantom time components, producing day-off errors for users in certain time zones. Another bug stored numeric values — such as hours and costs — as text strings, causing Excel functions like SUM to return zero despite the figures appearing correct. The team resolved the issues by writing integer Excel serial numbers for dates and explicitly casting numeric columns to number types at the point of file generation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Rewrite OR Conditions in GBase 8a to Fix Slow Query Plans

Queries using OR conditions in GBase 8a can cause significant performance degradation when the optimizer generates a poor execution plan. For filter predicates, developers can replace OR checks with DECODE or CASE WHEN expressions to consolidate multiple equality tests into a single condition. When OR appears across two columns, a CONCAT combined with a LIKE pattern can substitute for the original predicate. For LEFT JOIN queries with OR in the ON clause, the join can be split into two separate LEFT JOINs whose results are merged using COALESCE, though this approach is only valid when the right table matches at most one row per left row. All such rewrites are manual workarounds and must be validated for both correctness and performance gains in a test environment before production use.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Automated Bounce and Complaint Webhooks Can Keep AI Email Agents Deliverable

Autonomous email agents risk harming domain deliverability by repeatedly sending to invalid or spam-flagged addresses, since a basic send loop has no mechanism to learn from failures. A practical solution involves wiring deliverability webhooks — triggered by bounce and complaint events — directly into a suppression list that permanently blocks future sends to those addresses. The suppression logic is enforced at the platform level via a block rule, meaning every outbound send across all agent accounts in a workspace is filtered without requiring custom database checks in application code. This approach removes the risk of developers forgetting to implement pre-send validation on new send paths, and allows non-engineers to manage the suppression list without code changes. The result is a self-correcting feedback loop where bad addresses are automatically excluded the moment a bounce or complaint is detected.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Nylas Lets AI Email Agents Use Dynamic Allow/Block Lists Without Code Redeployment

Nylas has introduced a Lists and Rules system for AI email agent accounts that allows developers to manage allowlists and denylists without changing application code. Traditionally, permitted domains were hardcoded, meaning every update required a pull request, review, and redeployment. With the new control-plane approach, editable Lists of domains or addresses are referenced by Rules that evaluate every inbound and outbound message in real time. Updating a List instantly affects all Rules and Agent Accounts that reference it across a workspace. The system also fails closed on infrastructure errors, blocking messages rather than allowing them through if a list lookup fails.

0 comments Read more at DEV Community