https://stackonward.com/tags/webhook/Recent content in Webhook on StackOnwardHugoen-USFri, 11 Sep 2026 12:00:00 +0800https://stackonward.com/posts/payment-sandbox-to-production-launch/Fri, 11 Sep 2026 05:24:00 +0800https://stackonward.com/posts/payment-sandbox-to-production-launch/<p>The checkout page already uses a live key, but the subscription still cites a test Price. After the customer pays, the production webhook fails signature checks because it still uses the sandbox secret. Mixed config does not fail together: some errors stop before payment, others wait until money has moved, then order, entitlements, and finance stop in different states.</p> <p>The cutover order is: fence entries that create captures and refunds; attach account, keys, Price, webhook, domain, workers, and finance to live together; use read-only requests, test events, and return-URL checks to catch environment errors; then open the first real order under provider rules. If that first order fails, close new transactions. Webhooks, lookups, and reconciliation keep running.</p>https://stackonward.com/posts/payment-domain-object-model/Fri, 11 Sep 2026 05:20:00 +0800https://stackonward.com/posts/payment-domain-object-model/<p>A purchase can capture successfully while the workspace stays “provisioning.” Charging again does not fix that. Find the fulfillment record for the original order, and why it did not finish.</p> <p>A payment domain model stores sale terms, execution, and money results as separate identities. Quote freezes the payable amount. Order stores what both sides confirmed. CheckoutSession and execution records manage the collection process. Payment is the local payment. Transaction stores the result of a specific money action. Provider objects attach through their own identity map. Refunds and fulfillment then point at confirmed purchase and money records. One <code>paid</code> field cannot replace those links.</p>