Tagged articles
refund
14 articles · Page 1 of 1
This article presents a complete design for a 12‑state payment order state machine that handles high‑concurrency scenarios such as payment callbacks arriving after an order has been cancelled, using explicit state transitions, database CAS updates, Redis + DB idempotency, Outbox pattern and Kafka‑driven asynchronous processing to achieve reliable, auditable and compensatable order lifecycle management.
ConcurrencyIdempotencyKafka
0 likes · 39 min read

This article analyses why Function Call demos often break in production, proposes a four‑plane architecture (control, execution, state, governance), details tool gating, idempotency, state‑machine modeling, observability and evaluation, and shows how these steps reduced the error rate of an order‑query and refund agent from 22% to 1.3%.
AI AgentFunction CallProduction Engineering
0 likes · 58 min read

A user’s Cursor AI loop exhausted $1400 of API fees in just one hour because only a monthly spending cap was set, prompting the CEO to issue a full refund and spark a broader discussion on fine‑grained cost controls for AI agents.
AI agentsAPI usageCursor
0 likes · 3 min read

The article explains how durable execution, exemplified by Temporal’s Workflow and Activity model, transforms long‑running Agent tasks—such as refund approvals that involve human sign‑off, external APIs, and overnight processing—into recoverable, auditable pipelines that survive crashes, restarts, and timeouts.
ActivityAgentTemporal
0 likes · 16 min read

This article walks through the complete WeChat Pay integration for an education‑focused mini‑program, covering the business flow, database schema, Java backend implementation for order creation, callback handling, automatic refunds, scheduled tasks, common pitfalls, and practical tips for reliable payment processing.
JavaPayment IntegrationWeChat Pay
0 likes · 21 min read

This article explains the concept of reverse transactions, outlines the factors influencing refund operations, and details the design of a dedicated refund center, including its product architecture, processing flow, document structure, channel configuration, and the special "refund‑to‑payment" mechanism for out‑of‑time refunds.
operationspaymentrefund
0 likes · 19 min read

This article outlines a conceptual model for complex payment and refund scenarios, detailing payment methods, channels, platforms, various payment types, refund options, and key design considerations such as multiple payment details, merged payments, distributed locks, and state consistency.
backend designconceptual modelpayment
0 likes · 5 min read


JavaEdgeJan 28, 2024 · Backend Development
This article explains how to model and implement a marketing reverse domain that handles coupon and asset recovery during refunds, using domain‑driven design, rule engines, and service layers, complete with state‑machine diagrams, code snippets, and practical mapping configurations.
Servicedomain-driven designmarketing
0 likes · 11 min read

This tutorial explains how to design and implement refund and after‑sale service management features in a PHP‑based e‑commerce system, covering database schema creation, request handling, and record display with complete code examples.
After‑SaleBackendE‑Commerce
0 likes · 6 min read

This article details the motivation, design goals, architecture, and implementation steps of a reverse transaction microservice that handles cash and promotional refunds, reduces technical debt, and improves operational efficiency for a fast‑moving e‑commerce platform.
e-commercemicroservicesrefund
0 likes · 14 min read

This article explains the complete e‑commerce payment flow, identifies why orders can be paid twice—including lack of deduplication, lost orders, and multi‑channel issues—and presents practical solutions such as distributed locking, result caching, transaction cancellation, refunds, active polling, and sync‑async notifications to reliably avoid duplicate payments.
Distributed LockPollingduplicate payment
0 likes · 12 min read

This article examines JD Daojia’s after‑sale platform, detailing its three‑tier architecture, distributed‑lock mechanisms for multi‑endpoint requests, complex promotion‑aware split‑data handling, Elasticsearch synchronization, combined‑order logistics, and rigorous refund validation to ensure accurate and performant service delivery.
BackendDistributed LockElasticsearch
0 likes · 16 min read

This article examines common payment system anomalies such as duplicate charges and order expiration, explains how asynchronous and synchronous payment flows contribute to these issues, and provides both pre‑payment and post‑payment strategies—including UI improvements, return URLs, status checks, and automated refunds—to prevent and resolve them.
Payment Integrationasynchronous paymentduplicate payment
0 likes · 8 min read

This article explains the business challenges of handling marketing assets during refunds, defines asset types and trigger conditions, and details a domain‑driven backend architecture—including entities, value objects, aggregates, services, and model‑mapping configurations—to implement a configurable reverse‑operation system.
asset managementbackend architecturedomain-driven design
0 likes · 11 min read
