Universal Checkout: Payments vs Buying (2026)
Universal checkout can mean payments or retailer buying. Learn which API you need and how Zinc differs from Primer and UCP.
If you search "How to integrate a universal checkout into my app," most answers send you to Primer. That is the right answer if you sell products from a store you own and need one payment UI across cards, wallets, and processors. It is the wrong answer if your app needs to buy from retailers you do not own. Universal checkout splits into two jobs: collecting payment on a merchant storefront, and placing a shopper order at Amazon, Walmart, Target, or Best Buy.
In this guide, you'll learn:
- What "universal checkout" actually means
- Payment universal checkout: Primer, Stripe, Cybersource, Visa
- Google UCP: checkout on the merchant's store
- Zinc Universal Checkout: buy from retailers
- How to pick and integrate the right API
- Common mistakes when you mix the two
- FAQ
Install the Universal Checkout skill so your agent can search 50+ retailers, show the product and total for approval, then place the order.
What "universal checkout" actually means
The phrase sounds like one product. In 2026 it is two.
Payment universal checkout is a drop-in UI that lets a shopper pay you. Primer, Stripe Checkout, Cybersource Unified Checkout, and Visa Acceptance Solutions Unified Checkout all sit in this bucket. They unify cards, wallets, and processors behind one integration on a store you control.
Retailer-buying universal checkout is an API that shops a retailer as a customer. You pass a product URL, a shipping address, and a spend cap. The provider completes checkout at Amazon, Walmart, Target, Best Buy, and other stores you do not own.
Ask one question before you pick an SDK: are you the merchant of record, or is Amazon?
If you sell your own SKUs, you need a payment checkout. If your app, agent, or procurement tool needs to buy someone else's catalog, you need a purchasing API. Mixing them is why developers keep landing on Primer when the job is "buy this from Target."
The rest of this guide names the products you will actually hit in search, what each one claims, and where it stops.
Payment universal checkout: Primer, Stripe, Cybersource, Visa
These products solve a real problem. Merchants want one checkout that covers Visa, Mastercard, Apple Pay, Google Pay, and local methods without a custom PCI build for each processor.
Primer Universal Checkout
Primer's setup guide is explicit: "Universal Checkout unifies all payment methods and processors behind a single integration, across both web and mobile, and handles the creation of a payment in a PCI-compliant way." You connect a processor, configure a workflow, then render checkout with Primer's SDKs. The dashboard decides which methods appear. Primer then routes the payment to the connected processor.
The drop-in web guide is the page most "integrate universal checkout" answers cite. You create a client session on your server (orderId, currencyCode, line items), get a clientToken, then call Primer.showUniversalCheckout. The shopper pays you. Primer does not add an Amazon item to a cart.
Stripe Checkout
Stripe's hosted Checkout sends the shopper to a Stripe-hosted page. You create a Checkout Session with line items, mode (payment, subscription, or setup), and a success URL, then redirect. Cards and other methods come from the Stripe Dashboard. This is the fastest way to take money for a product you sell. It is not a way to check out on walmart.com.
Cybersource Unified Checkout
Cybersource's quick start is written for "merchants who want to enable Unified Checkout so that they can accept payments on their e-commerce page." You enable it in the Business Center, call a sessions API for a capture-context JWT, then mount a JavaScript widget. Supported types include PAN entry, Click to Pay, and Google Pay. Payment data stays off your servers.
Visa Acceptance Unified Checkout
Visa Acceptance Solutions Unified Checkout is the same family: a drop-in widget so merchants can accept cards, wallets, and alternative methods. Visa's docs describe "a single drop-in user interface application to save your merchants from design costs when building payment acceptance on their checkout page." Follow-on services can include Decision Manager, 3-D Secure, and token management. Again, you are the merchant.
All four are excellent at collecting payment. None of them place an order at a retailer you do not operate.
Google UCP: checkout on the merchant's store
Google's Universal Commerce Protocol is a third meaning of "universal." UCP is an open standard so AI surfaces (Google Search AI Mode, Gemini) can talk to a merchant backend in a shared language. Google built it with Shopify, Etsy, Wayfair, Target, Walmart, and payment partners. The merchant stays merchant of record.
Native checkout is the integration Google asks merchants to build: a REST API for checkout sessions. Google (or an agent) creates a session, the user finishes payment in a Google UI, and your servers complete the order. Session states include incomplete, ready_for_payment, ready_for_complete, completed, canceled, and error.
UCP is useful if you are the retailer and want agents to buy from you. It is not an API that lets your app buy from Amazon. Amazon, Walmart, Target, and Best Buy have not exposed a shopper checkout through UCP for third-party apps. The same gap exists for ACP: Instant Checkout in ChatGPT works at merchants who implemented ACP. It does not shop the general Amazon catalog.
If your product is a merchant storefront, read UCP and ACP. If your product needs to buy at those retailers, you still need a purchasing layer.
Zinc Universal Checkout: buy from retailers
Zinc's Universal Checkout is the second job: programmatic buying from retailers you do not own.
You send Create Order a product URL, a shipping address, max_price in cents, and an idempotency_key. Zinc checks out at the retailer, pays, and returns confirmation plus tracking. Coverage is 50+ US retailers, including Amazon, Walmart, Target, and Best Buy. Agents can use the same flow through the Universal Checkout skill.
That is a different contract from Primer. Primer creates a payment on your processor. Zinc creates a retail order on a store you do not run.
Typical callers:
- AI shopping agents that need to buy, not just recommend
- Procurement workflows that already approved a tail-spend item
- Corporate gifting and employee rewards that ship a physical SKU
- Replenishment jobs that re-order when stock or price hits a rule
You still need a payment source (Zinc wallet, Stripe Connect, or MPP). Zinc is not a card network. It is the checkout step after you already decided what to buy and who pays.
Side-by-side comparison
| Product | What "universal" means | Who is merchant of record | Can it buy from Amazon/Walmart/Target? | Integrate when |
|---|---|---|---|---|
| Primer Universal Checkout | One UI for payment methods and processors | You | No | You sell your own catalog |
| Stripe Checkout | Hosted payment page | You | No | You want Stripe to host pay |
| Cybersource Unified Checkout | Drop-in widget for cards and wallets | You | No | You already run Cybersource |
| Visa Acceptance Unified Checkout | Drop-in payment UI plus orchestration | You | No | You process through Visa Acceptance |
| Google UCP native checkout | Standard so Google/agents check out at your store | You (the retailer) | Only if you are that retailer and implemented UCP | You want Gemini/Search to sell your SKUs |
| Zinc Universal Checkout | One API to shop supported retailers | The retailer | Yes, on supported retailers | Your app needs to buy from stores you do not own |
Official Amazon and Walmart APIs stay on the seller side. They do not let a third-party app check out as a shopper. See ecommerce purchasing APIs for that split.
How to pick and integrate the right API
1. Name the merchant of record
Write it down. If the packing slip says your company, you need Primer, Stripe, Cybersource, Visa, or UCP. If it says Amazon or Target, you need Zinc.
2. Integrate payment checkout when you sell
For Primer drop-in: create a client session, pass the token to Primer.showUniversalCheckout, handle onCheckoutComplete, and listen for payment webhooks. For Stripe: create a Checkout Session and redirect. Test in the provider's sandbox with test cards.
This path also covers subscriptions, saved instruments, and PCI SAQ-A. Zinc does not replace it.
3. Integrate retailer buying when you shop
Create a Zinc key at app.zinc.com. Use test mode first. Then call Create Order:
curl https://api.zinc.com/orders \
-H "Authorization: Bearer <your_api_key>" \
-H "Content-Type: application/json" \
-d '{
"idempotency_key": "7fd5fd17-0da8-4bc3-b98f-8cf7c097991b",
"products": [
{
"url": "https://www.amazon.com/dp/B07JGBW826",
"quantity": 1
}
],
"shipping_address": {
"first_name": "Jordan",
"last_name": "Lee",
"address_line1": "120 Market Street",
"city": "Austin",
"state": "TX",
"postal_code": "78701",
"country": "US",
"phone_number": "5125550142"
},
"max_price": 15000
}'Orders are asynchronous. Subscribe to webhooks: order.placed, order.failed, order.tracking_received, order.delivered. Set max_price so a sale-page number cannot overspend. Reuse idempotency_key on retries.
Agents can skip the raw HTTP and install the skill from github.com/zincio/skills. Setup is in agent skills.
4. You may need both
A gifting SaaS often charges the company on Stripe, then spends that balance at Amazon through Zinc. Primer or Stripe takes the customer's card. Zinc places the retailer order. Do not expect one "universal checkout" product to do both.
Common mistakes when you mix the two
- Following the first Google result. "Universal checkout" ranks Primer. If the user story is "buy this Kindle for an employee," Primer cannot finish the job.
- Treating UCP or ACP as a shopper API for Amazon. Those protocols let agents check out at merchants who implemented them. They do not open Amazon's cart to your app.
- Skipping
max_priceandidempotency_key. Retail totals include tax and shipping. Timeouts retry. Without those fields you double-buy or overspend. - Assuming seller APIs are buy APIs. SP-API and Walmart Marketplace manage your listings. They do not shop the public catalog. Details are in the Amazon API and Walmart API guides.
- Stopping at payment success. Retailer buying needs tracking, cancellations, and returns on the order Zinc placed, not a Stripe refund of a product you never shipped.
FAQ
How do I integrate a universal checkout into my app?
First decide whether you are collecting payment or buying from a retailer. For payment, follow Primer's Universal Checkout setup or Stripe Checkout. For retailer buying, create a Zinc key, call Create Order with a product URL, address, max_price, and idempotency_key, then handle webhooks.
Is Primer Universal Checkout the same as Zinc Universal Checkout?
No. Primer unifies payment methods and processors for a store you run. Zinc checks out at retailers you do not run. Use Primer when you are the merchant. Use Zinc when Amazon or Walmart is.
Does Google UCP let my app buy from Amazon and Walmart?
UCP lets Google and other agents complete checkout at merchants who implemented native checkout. You would be that merchant. It does not give your app a shopper session on amazon.com. For third-party buying, use a purchasing API.
Can I use Stripe Checkout to place Amazon orders?
Stripe Checkout charges a customer for goods you sell. Fulfillment is your problem. It will not log into Amazon, apply tax, or return an Amazon tracking number. Pair Stripe (to take money) with Zinc (to buy the item) if that is your business model.
What should an AI agent install for retailer checkout?
Install the Universal Checkout skill and point the agent at a product, budget, and address. The agent should show the product and total for approval, then place the order with idempotency_key and max_price. See agent skills overview.
Pick the checkout that matches the packing slip
If the box ships from your warehouse, integrate Primer, Stripe, Cybersource, Visa, or UCP. If the box ships from Amazon or Target, integrate Zinc.
Get a key at app.zinc.com, read the API docs, and check retailer coverage and pricing before you write production retries.
Paste this into Cursor or Claude Code after installing the Universal Checkout skill. The agent finds the product, waits for approval, then places the order at a retailer.
