# Building a QR Payment Checkout? Plan for Failed Connections

Complete PC World — Thu, 29 Oct 2026 11:36:40 +0000

Displaying a QR code is easy. Building a checkout that handles delayed notifications, duplicate events, and uncertain payment outcomes takes care.

For developers exploring Asian payment technology, the starting point is the transaction lifecycle.

Create the Order Before the Payment

Store an order identifier, amount, and currency before requesting payment.

Associate each payment attempt with its provider reference. Keep separate attempts distinguishable so support staff can investigate what happened.

Never assume that scanning a code means the customer has paid.

Define Clear Payment States

Start with states such as created, pending, confirmed, failed, and expired. Map them to your provider's documented behavior.

Treat refunds separately because a confirmed transaction may later be partially refunded.

For each transition, specify:

Which provider event can trigger it.
Which transaction reference must match.
Whether the amount and currency match.
How repeated events are handled.

A browser redirect should not independently mark an order paid.

Make Duplicate Events Harmless

Design event processing so repeated notifications cannot trigger repeated fulfillment.

Authenticate callbacks using the provider's documented method. Store event identifiers where available and update transaction records atomically.

If your application times out, check the original transaction before starting another attempt. Missing confirmation does not necessarily mean failure.

Reconcile What Actually Happened

Connect order records with payment attempts, refunds, and settlement reports.

Give staff a reliable merchant view instead of relying on customer screenshots.

Test delayed callbacks, mismatched amounts, expired codes, and interrupted connections in the provider's sandbox.

I publish explanations of Asian banking and payment technology at FTAsiaStockTechnologies, which I run.

A reliable checkout needs more than a successful demo. It needs predictable behavior when systems disagree.

Which failure case would you test before letting your customer pay?

# Building an AI Stock Research Tool? Make Every Number Traceable

Complete PC World — Thu, 29 Oct 2026 11:32:58 +0000

An AI assistant can summarize a company in seconds. The harder engineering problem is making its answers reproducible.

Before adding another prompt, build a pipeline that preserves the evidence behind every financial claim.

Start With Structured Inputs

Use company filings as your starting point. The SEC provides APIs for submission histories and extracted financial data.

Keep the response alongside your normalized records. Each observation should retain its company identifier, reporting period, unit, filing date, and source reference.

A revenue figure without a period is an incomplete input.

Keep Arithmetic Outside the Model

Calculate ratios and growth rates in application code. Let the model explain validated results.

For example, revenue increasing from $100 million to $110 million represents 10% growth. However, that comparison becomes misleading if one figure covers a quarter and the other covers a year.

Validate:

Matching currencies and units.
Comparable reporting periods.
Missing or revised observations.
Zero denominators.

Return an explicit unavailable result when validation fails.

Treat Citations as Data

Store document references with retrieved passages. Require generated factual statements to reference those passages.

Then check whether the evidence actually supports the claim. A working link alone does not establish accuracy.

Separate reported facts, interpretations, and unanswered questions in the interface.

Test Failure Cases First

Try conflicting figures, missing data, repeated filings, and questions your dataset cannot answer.

The expected behavior should be visible uncertainty, rather than an unsupported conclusion.

For background on interpreting company decisions, I publish investing explainers at BetterThisWorldStocks, which I run.

Start with one narrow question and a reviewable answer. Expand only when your pipeline can show where every number came from.

What would you build first: the ingestion layer, calculation engine, or evidence viewer?

DEV Community: Complete PC World