Connect a selected AI purchase to buyer-approved checkout, verified payment, order confirmation and recoverable delivery on your merchant website.
AI agents complete checkout and payments by acting on current merchant terms, obtaining buyer authorization, initiating a supported payment, and letting the merchant verify the result before fulfilling the order. Appearing in AI search establishes none of those later commitments. Once a buyer selects a product, the merchant needs a purchase flow that can finish even if the agent closes its connection immediately after payment.
The useful completion standard is a recoverable order: what the buyer approved, what the merchant received, and what the merchant owes the buyer remain connected. A checkout success screen covers only part of that obligation.
GOAT Flow provides a documented example of hosted checkout, payment records and merchant reconciliation. The walkthrough below interprets its documentation alongside merchant design requirements. It is not a live payment test, a customer case, or evidence that Flow automatically manages stock, agent spending policies or delivery.
Refresh the purchase commitment
Start with the selected purchase. The agent already knows which item the buyer wants; the merchant must now decide whether it can honor that purchase on current terms. Recheck the chosen variant, quantity, availability, total price and applicable delivery conditions against the merchant's authoritative systems. An AI answer may describe a valid product while showing terms that no longer apply at checkout.
The total presented for approval should account for the commercial charges the buyer will actually owe, including shipping and tax where applicable. If those depend on a destination or eligibility check, resolve that dependency before requesting final approval. A product price without those decisions is not yet a complete purchase commitment.
Consider a hypothetical merchant selling a downloadable license. The selected offer must specify the license tier, permitted use, quantity and delivery destination. The merchant's backend checks that the offer remains available and calculates the current total. This example illustrates the decisions; it does not describe an observed GOAT Flow transaction or imply built-in license management.
For physical goods, the additional question is whether stock is reserved during approval or rechecked before payment. Reservation can protect availability while tying up inventory for buyers who never finish. Rechecking avoids that hold but may interrupt the buyer when the last unit sells. The merchant must choose a policy its inventory system can enforce and communicate what the checkout actually guarantees.
GOAT Flow's documented server-priced session can carry payment terms and display line items. Those fields do not establish inventory reservation, variant validation or shipping calculation. Your commerce backend remains responsible for the commercial checks unless a separately verified integration supplies them.
Make the quote's validity clear. If the item, quantity, total or delivery promise changes materially, pause and obtain approval for the revised purchase. A short-lived quote reduces exposure to stale terms but can expire while a person reviews it. Longer validity needs a merchant commitment to honor those terms or a clearly defined revalidation step. Session expiry alone does not define that commercial policy.
Authorize the spend before opening a payment path
The merchant's permission to create checkout is different from the buyer's permission to spend. Merchant API credentials identify the seller to a payment service. They do not prove that a particular customer authorized an agent to debit a wallet or complete a purchase.
Before payment initiation, define what the agent may do for this buyer. A useful authorization binds the purchase to the intended merchant or recipient, the approved goods, an acceptable total, the payment asset or currency, and a validity period. For a crypto payment, account for the network and relevant gas costs as well. These are recommended controls; their enforcement must exist in the chosen wallet, runtime or approval layer. They are not established GOAT Flow budget-enforcement features.
An instruction such as “find the right license” may permit research without permitting payment. Even “buy this license” needs a clear interpretation when the price changes or the receiving address differs from the expected merchant. The agent should stop at the limit of its actual authority rather than infer permission from its ability to reach checkout.
There are also different ways to finish the payment. In the documented GOAT Flow Crypto DIRECT path, the payer's wallet sends an ERC-20 transfer to the merchant-configured receiving address. An agent-controlled wallet still needs enforceable buyer authorization. A hosted Card path, where enabled for the deployment and session, requires the payer to complete the provider's flow. Creating or opening that checkout is not an unattended card purchase.
DIRECT names the checkout subsystem; the payment rail is separate. Describing DIRECT as universally crypto-only would miss the enabled hosted Card path. Conversely, the existence of Card documentation does not establish availability for every merchant, currency or region.
For the hypothetical license purchase, a buyer might approve a particular tier up to a stated total and require another approval if the terms change. The workflow can pause for that approval or proceed within an enforceable delegated policy. Human approval adds an interruption; delegated execution reduces that interruption but depends on controls where payment is actually authorized. Neither approach makes an expired or altered purchase automatically acceptable.
Create a payable session without losing the merchant order
With validated terms and an authorized payment path, the merchant backend can create a checkout session. In the GOAT Flow Hosted Checkout documentation, creation uses an HMAC-authenticated merchant request. The backend supplies authoritative pricing, while the buyer receives an opaque checkout URL. Merchant secrets stay on the server.
The documented response includes a checkout identifier, URL and expiry. Persist those returned values with the merchant's purchase record. The merchant should be able to explain which intended purchase produced that session without depending on an agent's chat history or an open browser tab.
Keep the records' meanings distinct:
Record | What it establishes | What remains unresolved |
|---|---|---|
Merchant purchase record | Selected goods, current terms and the buyer's intended order | Whether payment was initiated or received |
Checkout session | A payable path with session terms and lifecycle | Whether the merchant has verified funds |
Verified payment record | A payment matched to the expected merchant and order | Whether the goods or access were delivered |
Fulfillment record | The merchant's delivery action and its outcome | Any remaining delivery exception or buyer support need |
These need not be four separate databases. They do need separate meanings, linked through durable references. The merchant's business order, Flow checkout handle and linked payment order are not interchangeable identifiers. Retain the identifiers returned by the relevant surface rather than deriving one from another.
The hosted page then presents the rails enabled for that session. The buyer or authorized agent completes the applicable payer action. For an enabled Card flow, that can mean a handoff to the person; for Crypto, it involves the wallet and eligible payment terms. A generic ability to browse merchant pages does not establish compatibility with every payment flow.
Treat the opaque checkout handle carefully: the documentation describes it as a bearer capability. Avoid unnecessary logging and do not place secrets or sensitive customer details in public line items or metadata. GOAT Flow distinguishes private metadata from the public session view, but that does not remove the merchant's responsibility to limit what it exposes.
At this point the merchant has offered a way to pay. It has not yet established a paid order, and a successful session-creation response should not trigger delivery.
Verify payment on the merchant backend
A browser success callback, return-page visit or message from the agent is a user-interface signal. None is sufficient evidence to release a license, ship goods or activate service. Verification belongs on a trusted backend path that checks the actual payment record.
GOAT Flow's merchant documentation calls for an authenticated backend status check or a verified webhook, followed by matching the expected payment details. For the documented Crypto flow, check the merchant and order identifiers, chain, token, amount, receiving address and transaction identity. A transfer can exist on-chain and still be for the wrong recipient, asset or purchase. A transaction hash supplied by the payer does not perform those checks for the merchant.
State names require equal care. Hosted checkout sessions have their own lifecycle, including COMPLETED; the linked order has a separate payment status model. GOAT Flow's documented order waiters accept PAYMENT_CONFIRMED or INVOICED as successful states. A DIRECT order can advance to INVOICED before a poller observes PAYMENT_CONFIRMED. Waiting only for the intermediate label can therefore leave a successful payment looking unresolved.
That does not make an INVOICED order proof of shipment or license delivery. It is an order-payment state in this documented model. The merchant still verifies attribution and records its own fulfillment outcome. Apply the rail-specific contract for the active environment rather than expecting every Card payment to expose crypto transaction fields.
There is a further trap in the API reference: the historical order-proof field named signature is an unsigned digest, not a signed attestation. It does not cover the status field. A merchant must not treat its name or hash-like appearance as authentication. The documentation directs independent verification to the on-chain transaction when independent proof is required.
If using webhooks, verify the deployment's actual event, payload, authentication and retry contract before relying on it. The reviewed public documentation does not define one universal production event name and signature scheme. Until those details are established, do not invent a handler from a similarly named event in another provider's system. Choose a documented trusted verification path and keep an unresolved payment pending rather than promoting a browser signal into proof.
Turn verified funds into a confirmed, fulfillable order
After matching payment to the purchase, the merchant can confirm the paid order and begin fulfillment under its commercial rules. The confirmation should tell the buyer what was bought, the approved total, a stable order reference and the current delivery status. If delivery is pending, say so. An acknowledgment that the request was received should not read like proof that a download or shipment is already available.
For the hypothetical license, the merchant would record the verified payment against the approved tier, create or recover the corresponding entitlement, and expose a retrievable delivery result. The customer might receive an account entitlement or a controlled download route, depending on the merchant's design. Neither is demonstrated as an automatic GOAT Flow feature by the checkout documentation.
Fulfillment must also tolerate repeated triggers. If a webhook is retried or the merchant polls the same payment again, the second invocation should recover the existing entitlement or shipment task rather than create another one. This is idempotent fulfillment: repeating the same business action does not duplicate its effect. Payment verification and delivery execution need to share a stable order reference for that protection to work.
Stripe's fulfillment guidance provides an independent reason to put this work on the server: a customer can pay and fail to reach the return page. Its guidance also addresses repeated fulfillment calls. Those principles support the recovery design here; Stripe's particular event names and APIs are not GOAT Flow integration instructions.
A confirmation sent only to an agent's temporary conversation is fragile. Give the buyer a recoverable order reference through the merchant's appropriate customer channel, with access to delivery status or support. Avoid placing payment capabilities or private credentials in that confirmation. The buyer needs evidence of the commercial obligation, not the merchant's internal secrets.
For physical goods, “paid,” “accepted for fulfillment” and “shipped” can occur at different times. For a digital product, entitlement creation and successful access can also differ. Choose status language that reflects the obligation and observed result. The payment system can establish receipt of funds while the merchant still owes delivery; the customer record should preserve that distinction.
Recover the original purchase when the happy path breaks
Recovery starts by asking which commitment is uncertain. A timeout during session creation, a late payment and a failed delivery require different actions. Retrying the whole purchase treats all three as if nothing happened, which can create another payable session or charge without resolving the first obligation.
If session creation times out, preserve the original business intent and reconcile the request. GOAT Flow documents that reusing the same nonempty clientReferenceId for the same merchant returns a conflict; it does not return the original checkout handle or URL. This is duplicate protection, not a recovery lookup. The public server SDK does not establish lookup by that reference.
When the original response was received, the persisted checkoutId and URL give the merchant something concrete to recover. When the response was lost, use merchant records or deployment support to resolve the original attempt. Do not invent a lookup endpoint or automatically generate a new reference to bypass the conflict. An unresolved creation response is not evidence that no payable session exists.
If payment arrives after expiry, inspect both the payment and the commercial obligation. GOAT Flow's merchant reconciliation distinguishes late payments received after expiry. Expiry therefore cannot be treated as proof that no funds arrived. The original quote or stock commitment may no longer be valid even though the merchant received money.
Hold that case for a merchant-defined exception decision. Recheck availability and whether the approved terms can still be honored. If they cannot, follow the merchant's applicable resolution policy and communicate the outcome to the buyer. The reviewed documentation does not establish an automatic refund, replacement session or inventory-restoration guarantee. Opening a fresh checkout before reconciling the old payment risks asking the buyer to pay twice.
If payment is verified but delivery fails, keep the paid order and the undelivered obligation visible. Retry the delivery operation against the same fulfillment reference, checking whether it already succeeded before issuing anything new. If the result remains uncertain, route the order to support or an exception queue with the payment and delivery evidence intact. Do not charge again to compensate for a lost browser response.
For the hypothetical license, an agent disconnecting after payment should leave a recoverable paid order. If entitlement creation completed but its response was lost, recovery should retrieve that entitlement. If creation failed, the merchant can retry it safely or resolve the obligation under its policy. These are recommended application behaviors, not reported Flow test results.
Before enabling a purchase path, establish who owns each exception and what record they can inspect. The merchant should be able to answer the buyer's practical question: “Did I pay, what will I receive, and how do I recover it?” If answering requires starting another checkout, the original purchase is not yet recoverable.
FAQ
Can the agent change the delivery destination after the buyer approves?
Treat a destination change as a purchase change that may affect eligibility, shipping, tax or delivery rights. Revalidate the terms and obtain renewed approval when the change exceeds the buyer's existing authorization. A payment session alone does not grant permission to redirect the order.
What if the agent disconnects immediately after payment?
The merchant should verify payment through a trusted backend path and continue or recover fulfillment using the original order reference. The buyer needs a retrievable confirmation and delivery status independent of the agent's connection. Do not require a second payment merely because the agent missed the response.
Does an expired checkout guarantee a refund?
No automatic refund guarantee was established by the reviewed documentation. GOAT Flow's merchant reconciliation distinguishes payments received after expiry. Reconcile the original payment and apply the merchant's resolution policy before creating another payable session or promising an outcome.



