Accept payments from AI agents with clear buyer permissions, card handoffs, stablecoin receipt and x402 verification, using documented GOAT Flow paths.
An agent can select a product and create a payment link while the purchase still waits for a person to pay. That is a useful sales path, but it differs from an agent completing an authorized payment itself. Merchants need to decide which experience they are accepting before promising an automatic purchase.
To accept payments from AI agents, provide a payment path the buyer can use, keep the amount and recipient under merchant control, and verify the result on your backend before delivering. A compatible crypto signer can make buyer-authorized payments within an enforced mandate. In GOAT Flow's documented hosted Card path, the agent can prepare the link, but the payer must complete the provider page.
Cards, wallets, stablecoins and x402 answer different questions. Cards provide payment credentials and a processing path; wallets expose credentials, balances or signing; stablecoins are assets; x402 coordinates payment with a resource request. GOAT Flow is a merchant product that applies configured payment paths and records their results. Combining these layers can make a purchase possible. None of the labels, by itself, establishes permission to spend.
Decide whether the agent pays or prepares a payment
Begin with the customer's mandate. Does the agent have permission only to find an offer, to prepare checkout for confirmation, or to spend within specific limits? These are different buying experiences even when the merchant uses the same checkout product.
For an assisted purchase, the agent can assemble the proposed order and return a hosted payment URL. The customer sees the final terms and completes payment. The merchant should preserve that handoff as a pending purchase rather than treating the agent's successful tool call as a completed sale. A link that nobody opens has collected no money.
For automatic crypto payment, the buyer integration needs a compatible signer, sufficient funds and authority to use them for this purchase. The merchant cannot grant that authority simply by accepting crypto. A model's instruction to pay also needs an enforcement boundary outside the model's discretionary response: the wallet or signing service should reject spending that exceeds the owner's mandate.
As an implementation recommendation, define allowed recipients, networks and assets, per-purchase and cumulative spending limits, expiry and revocation. Decide which changes require fresh customer approval. These are requirements to verify in the buyer integration, not a claim that GOAT Flow supplies a built-in policy engine for every agent wallet.
Consider a hypothetical buyer who permits an agent to purchase one digital report from a named seller up to an approved total. A different receiving address or a higher final amount should stop automatic signing and return the decision to the buyer. Holding the right token does not override the mandate. Nor should a repeated request create another allowance to buy the same report.
Three separate authorities matter here. The owner authorizes the agent's purchase. The payment system authenticates or processes the payer's action. The merchant decides whether authenticated payment evidence permits release of the product. A successful result at one boundary cannot stand in for the other two.
GOAT Flow's Merchant Guide makes the assisted Card boundary concrete: creating a card checkout link returns human_action_required: true. That is evidence that a customer action remains, not a payment receipt. Keep this distinction visible in the buyer experience so an agent reports "payment awaiting your confirmation" rather than "order paid" after link creation.
Cards and wallets can keep the customer in the purchase
A card route is appropriate when the buyer intends to use a card and the merchant has a supported processing integration. An agent can help prepare the purchase, but unattended charging requires a separately supported authorization arrangement. GOAT Flow's documented hosted Card path does not establish such an arrangement: the payer enters card details and finishes the hosted provider flow.
Stripe's card documentation separates checking card details, possible customer authentication, issuer authorization and capture. The issuer's authorization concerns the payment amount and available funds. It is not the customer's delegation of purchasing authority to an AI agent. Authentication may also introduce an action that the agent cannot complete on the customer's behalf.
That separation changes what the merchant should display. A checkout session can be ready while payer authentication remains outstanding. A bank authorization can also have a different meaning from captured payment in the selected integration. Use the provider's documented state contract for the release decision; a broad “success” label is too ambiguous to specify it.
The word “wallet” needs similar care. Stripe's wallet documentation describes consumer wallets that present a saved payment credential, such as a tokenized card, or use a stored wallet balance. The wallet typically authenticates the customer and passes payment details or a token to the processor. It can make customer checkout more convenient without turning the underlying purchase into a crypto transfer.
A crypto wallet performs a different job when it signs a token transfer. Accepting a consumer wallet does not establish support for that signing path, and adding a crypto-wallet connection does not establish support for card-backed wallets. When a vendor says it supports “agent wallets,” ask which credential or asset is used, where signing occurs, and whether a person must still confirm.
For the merchant, the tradeoff is concrete. Customer-confirmed card checkout can serve buyers who do not want to manage crypto assets, while preserving a human step in the documented Flow experience. Authorized crypto signing can remove that particular checkout interaction when the buyer integration supports it, but introduces funding, network and signer requirements instead.
Avoid describing the first path as a failed version of automation. For a buyer who has not delegated spending, returning a checkout link is the correct completion of the agent's permitted task. The merchant can accept agent-assisted sales without claiming the agent itself made an unattended card payment.
Stablecoins change the asset and the receipt obligation
A stablecoin is a crypto asset designed to track a reference value. Its intended price stability does not grant an agent spending permission or determine how a payment provider credits the merchant. The buyer's asset and the merchant's eventual receipt must be examined separately.
Stripe's documented stablecoin payment product illustrates this distinction. Customers choose a supported stablecoin, wallet and network, and payment confirmation is customer-authenticated. Completed payments settle in the merchant's Stripe balance in local currency. This is a documented product flow, not evidence that stablecoin checkout is inherently unattended.
GOAT Flow's documented crypto DIRECT path has a different receipt model: the payer transfers ERC-20 tokens to the merchant receiving address returned for the order. A merchant considering a stablecoin on that path must confirm that the exact network and token are accepted in the active configuration. The token arriving at the address is not the same outcome as a provider crediting a local-currency balance.
This contrast matters even if the buyer describes both experiences as “paying with stablecoins.” Direct token receipt leaves the merchant holding the received asset and responsible for the operational decisions that follow. A provider-managed local-currency balance changes that accounting and asset-handling outcome, subject to that provider's actual terms and eligibility. Neither receipt model can be inferred from a stablecoin logo on a checkout page.
For direct crypto acceptance, specify the complete payment combination. The receiving address, network, token and amount need to match the merchant's expected purchase. A familiar token symbol is not sufficient identification across networks. The buyer also needs the funding and execution requirements of the chosen payment path; do not assume that possessing the purchase token alone guarantees a successful transfer.
If the buyer cannot meet the offered terms, return an actionable incompatibility rather than improvising a different network or recipient. Changing where the money goes can exceed the owner's original mandate. A seller accepting one token configuration has not thereby promised to recognize every asset with the same ticker.
Stablecoins also do not automatically connect a card price to a crypto quote. GOAT Flow Checkout's current documentation says a session offering both rails supplies the crypto price and the fiat amount separately; neither is converted into the other. The merchant must decide and provide the payable terms for each offered method. Do not advertise an automatic conversion feature from the existence of two prices.
The practical choice is therefore about receipt as well as reach. If the business needs local-currency accounting through a particular provider, verify that provider's supported settlement arrangement. If it wants tokens delivered to its configured address, verify the direct-transfer configuration and the evidence used to recognize receipt. In both cases, separately resolve whether the buyer confirms the payment or delegates it to a signer.
x402 makes the HTTP request payable
x402 supplies a payment handshake for an HTTP interaction. In the documented pattern, a client requests a resource, the server responds with payment requirements, and the client returns a signed payment with its request. This lets a compatible buyer and seller negotiate payment as part of accessing an API or service.
The important difference from a payment link is the interaction being coordinated. A hosted link takes the payer to a checkout experience. An x402 integration lets software respond to advertised payment requirements inside a request flow. The buyer still needs a compatible payment capability and permission to use it; an ordinary HTTP client does not become a funded agent simply because an endpoint requests payment.
Coinbase's explanation of the x402 payment flow distinguishes verification from settlement. In its facilitator example, the server asks the facilitator to verify the payment, performs the requested work, asks for settlement, and then returns the resource after the settlement result. A verification result and a settlement result therefore represent different events in that documented sequence.
For a paid service, that ordering creates an implementation decision. If work begins before settlement is confirmed, the application must decide what to do when settlement fails after computation has started. It should also decide how to recover when payment succeeds but the client misses the response. The payment handshake does not, by itself, define whether a repeated request should run the work again or return an existing result.
The protocol is broader than one chain or token list. The seller advertises accepted payment combinations, and the buyer must choose a supported option. Broad protocol flexibility does not establish that a particular facilitator, SDK, deployment or GOAT Flow merchant supports every possible combination. Compatibility must hold across the actual buyer, seller and payment implementation.
For an API provider with a compatible paying client, per-request negotiation can be a direct fit. For a store shipping a physical product, payment still needs to connect to the order, stock and delivery destination. x402 does not replace those commerce records. Its role is to coordinate the payment-bearing interaction, not to supply every business meaning attached to the purchase.
Keep the implementation boundary equally clear when evaluating GOAT Flow. Coinbase's facilitator sequence is evidence about the documented x402 example; it is not a universal description of Flow's DIRECT crypto sequence. Flow's merchant documentation describes direct transfer and receipt verification for its current crypto path. The actual product contract determines how that merchant recognizes payment.
The benefit of a protocol handshake is useful machine-readable coordination. Its limit is that the surrounding application still owns buyer permission, the resource or order being bought, and recovery of an uncertain purchase. Choose x402 because that request-level interaction fits the service, while evaluating the asset and merchant product as separate decisions.
Apply the distinctions to GOAT Flow payment acceptance
GOAT Flow provides merchant payment surfaces including Checkout and QuickPay, with payment and order records for operations. Apply it to a specific purchase path rather than assuming that enabling a product enables every payment method or every degree of agent autonomy.
Payment path | Payer action | Documented merchant outcome | Acceptance condition |
|---|---|---|---|
Flow hosted Card, when enabled | Customer completes the provider page; an agent may prepare the link | Rail-specific result recorded by Flow | Verify enabled fiat configuration and trusted completion for that surface |
Flow crypto DIRECT | Buyer wallet sends the ERC-20 transfer; automation depends on authorized signing | Tokens sent to the configured receiving address | Match the active token/network terms and trusted payment status |
Compatible x402 request | Client responds to payment requirements using an authorized payment capability | Depends on the selected seller and payment implementation | Verify the advertised combination and the implementation's verification/settlement contract |
The last row is a protocol interaction that can be composed with payment infrastructure, not a third equivalent Flow rail. Keeping it separate prevents a protocol support claim from becoming an unsupported merchant availability promise.
Configure terms and the enabled payment method
The current Checkout documentation separates checkoutType: DIRECT from paymentRails. DIRECT selects the checkout subsystem. Rail settings select the methods offered. An enabled Card session can therefore use DIRECT; describing DIRECT as crypto-only would misstate the documented model. The ERC-20 transfer description applies specifically to its crypto branch.
For hosted Card, confirm deployment and merchant fiat enablement, the required connected Stripe account state, product settings where relevant, and test/live configuration. For crypto, confirm the receiving address and supported network/token combination. The examples in public documentation do not establish that those settings are active for your merchant.
Keep price authority on the merchant side. Use the configured product price or a backend-created Checkout Session with authoritative terms. Preserve the purchase reference alongside the returned order or session identifiers. Expose the payer-facing URL or supported public surface to the agent, while keeping merchant authentication secrets on the backend.
The product names also describe separate responsibilities. GOAT Flow is the merchant commerce product. x402 is the payment protocol used by relevant payment interactions. GOAT AgentKit is the agent action/runtime layer, where buyer tooling belongs; its existence does not prove that every Flow buyer has an enforced spend policy. GOAT Network provides the network execution and settlement layer. A Flow payment confirmation is not a claim of instant settlement on Bitcoin L1.
Verify the result for the exact surface
Session creation, a browser success return and a transaction hash are not sufficient fulfillment authority. Match a trusted backend result to the expected purchase and its amount, recipient and rail-specific terms before granting access or releasing an order. Card confirmation need not contain an on-chain transaction hash, so a crypto-only verification assumption can reject a legitimate card result.
Flow's merchant documentation says ordinary orders, payment sessions and Hosted Checkout use different status models. Use the successful state contract for the surface you integrated. Copying a status label from another example can leave the merchant waiting for the wrong condition or releasing value on an intermediate state.
If using notifications, obtain the actual deployment's webhook contract, including authentication, payload and replay/retry behavior. The retrieved public guide states that it does not contain a deployment-approved production notification sample or versioned webhook contract. Do not build fulfillment around a guessed signing header or assumed event name. Trusted backend reconciliation remains the required decision boundary while the notification integration is being established.
Resume an uncertain payment instead of paying again
A timeout after a transfer attempt is an unknown observation, not proof that no money moved. Preserve the original purchase reference, session/order identifiers and known transaction hash. Resume verification against that attempt before issuing another transfer or changing payment methods.
The Merchant Guide specifically warns against rebroadcasting solely because status polling or receipt verification failed. For retries of the same QuickPay intent, reuse the idempotency key so the integration resumes the existing session. That does not remove the merchant's separate obligation to make delivery repeat-safe.
On the merchant backend, make the transition from verified payment to fulfillment atomic and deduplicated against the relevant business record. Repeated notifications or an agent asking for the result again should not grant a second entitlement or ship another item. Likewise, a Card link awaiting payer completion should remain pending rather than triggering an automatic crypto fallback.
Before enabling automatic release, require evidence for both a completed payment and a recoverable unknown outcome. A merchant that cannot reconcile its first attempt should hold delivery and investigate that attempt; it should not ask the buyer to pay again simply to obtain a cleaner response.
FAQ
Does a successful card payment need an on-chain transaction hash?
No. Card confirmation need not include an on-chain transaction hash. Verify the authenticated result and successful state defined for the card payment surface, matched to the expected purchase.
Does offering card and crypto prices create automatic currency conversion?
No. GOAT Flow Checkout documents separate fiat and crypto amounts for a session offering both rails. The merchant supplies those terms; one amount is not automatically converted into the other.
Does x402 define the refund policy for a product purchase?
Do not assume it does. The merchant must specify the purchase's refund terms and the refund capability of the selected payment implementation. A payment handshake alone does not establish a completed refund or a customer entitlement.
Should a buying agent receive the merchant's API secret?
No. Keep merchant authentication credentials on the merchant backend. Give the buyer the supported public payment surface or payer-facing checkout URL, with the buyer's own payment authority handled separately.



