Currency Mismatch Bug Would Have Silently Killed Auto Top-Up for All Users

·1 views

A software team discovered a critical bug in their automatic top-up feature before it reached any real users, catching it during integration testing against Stripe's test environment. The defect stemmed from a currency conflict: invoices inherited the Dutch business's default EUR currency from the Stripe account, while all product prices were set in USD, causing every automatic top-up attempt to fail at invoice finalisation. Customers would have been falsely told their card was declined, potentially wasting time troubleshooting a perfectly functional payment method, while production integrations could have silently run out of credit. The manual top-up path was unaffected because Checkout Sessions derive currency from the first line item rather than the customer record, masking the bug behind an otherwise functional payment flow. The flaw was ultimately found not by chance but because a documented testing gap was formally closed, with a full end-to-end test against real Stripe test-mode infrastructure exposing the conflict on its very first run.

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)

Developer Removes ColorCopy App from macOS App Store

A developer has announced the decision to pull their app, ColorCopy, from the macOS App Store. The announcement was made via a personal blog post at abeautifulsite.net. The specific reasons behind the removal have not been provided in the available text. Without further article content, the full context and circumstances of this decision cannot be reported accurately.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

gRPC vs REST: How to Choose the Right Protocol for Service Communication

A technical comparison published on DEV Community breaks down the key differences between REST and gRPC for service-to-service communication. REST transmits human-readable JSON over HTTP/1.1 and is universally supported by browsers, making it well-suited for public APIs and external clients. gRPC uses binary Protocol Buffers over HTTP/2, delivering roughly 5–10 times better performance and native bi-directional streaming, which makes it ideal for internal microservice communication. The guide recommends a hybrid architecture where an API gateway handles external REST traffic while internal services communicate via gRPC for speed and type safety. Developers are advised to avoid gRPC when browser clients need direct access or when teams lack familiarity with the required .proto schema format.

0 comments Read more at DEV Community

ProgrammingHacker News ·

NASA Extends Voyager 2 Mission by Another Year Despite Probe Being 48 Years Old

NASA has found a way to keep its Voyager 2 spacecraft operational for at least one more year, extending one of the longest-running missions in space exploration history. The probe, launched in 1977, is now 48 years old and continues to operate far beyond its original mission parameters. Engineers devised a solution to address the power and operational challenges that come with the aging spacecraft. Voyager 2 remains one of only a handful of human-made objects to have traveled into interstellar space.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

LangGraph Tutorial Part 5: Agent Learns to Balance Shared Driver Pools Across Two Zones

A developer tutorial series on building a ride-share zone-balancing AI agent concludes with its fifth and final installment, focusing on coordinating two zones simultaneously rather than evaluating each in isolation. Previous parts assumed an unlimited driver pool, but the new installment addresses the reality that regional driver supplies are finite and shared between zones. Each zone gains two additional supply channels: a local dormant driver pool and a cross-zone pull request that draws from a neighboring zone's surplus. A human approval step is triggered only when a zone's cross-zone request exceeds what the adjacent zone can comfortably spare, keeping most automated cycles uninterrupted. The tutorial also explains key architectural decisions in LangGraph, including why each zone's logic is wrapped as a compiled sub-graph to ensure reliable parallel fan-in behavior.

0 comments Read more at DEV Community