Recommended Free Tools
Require the agent’s payment authorization to reference the merchant’s authenticated, finalized checkout—not merely the agent, product, or price it initially discussed. In Google’s AP2 model, a merchant-signed checkout is linked to a user-approved or user-constrained mandate, and the payment mandate is cryptographically bound to that same checkout. The merchant and payment participants verify the link before proceeding.
What “tied to the accepted offer” means
A product page, a chat summary, and a checkout are not necessarily the same offer. A shopper may approve one price or configuration, then encounter changed quantity, shipping, taxes, discounts, or terms at checkout. To make the authorization meaningful, it needs to identify the actual transaction the merchant is prepared to fulfill.
As an Amazon Associate I earn from qualifying purchases.
AP2 addresses this with a merchant-signed Checkout JWT containing checkout details. A closed Checkout Mandate is bound to that checkout, and the Payment Mandate refers to the same checkout through a cryptographic hash of the Checkout JWT. A verifier can then check that the payment authorization corresponds to the authenticated checkout rather than to a different or altered one.
The hash does not independently guarantee that a price is correct, fair, or what the user remembers seeing. It binds authorization to the signed payload. That payload must contain the terms relevant to the purchase—such as items and quantities, currency, taxes, shipping, discounts, and total—for the binding to establish what was authorized. AP2 leaves the detailed contents of the checkout object to the commerce protocol in use. Its checkout-hash design also specifies use of a non-deterministic signature scheme for the Checkout JWT.
#1 Best Overall
- With Square Terminal, you can ring up sales, accept payments, and print receipts, all with one device. Use it at the counter or ring up customers anywhere in your store.
- Accept all major credit and debit cards and pay one low rate with no hidden fees and no long-term contracts.
- Process chip cards in just two seconds.
- Get your money as soon as the next business day.
- Use it cordlessly with the built-in battery, designed to last all day.
How authorization follows the checkout
- Build the cart. The agent and merchant negotiate items and checkout details. An initial search result or quoted product price is not yet the final transaction.
- Authenticate the final checkout. The merchant returns a signed checkout object representing the purchase terms it is willing to stand behind.
- Obtain authority for that transaction. If the user is present, a trusted user-facing surface presents the closed checkout for approval. If the purchase is autonomous, the user has already approved bounded constraints that the finalized checkout must satisfy.
- Create linked mandates. The agent presents a closed Checkout Mandate and Payment Mandate that refer to the merchant’s checkout. In AP2, the payment mandate’s checkout hash provides the link.
- Verify before payment. The merchant checks the checkout and mandate constraints. The credential provider and, where applicable, the network verify payment authorization before releasing a credential; the merchant’s payment processor checks that the credential is scoped to this checkout.
- Record the outcome. Participants return signed receipts for acceptance or rejection, creating records that can be checked against the mandates and checkout.
This sequence separates an agent’s ability to propose or assemble an order from the authority to pay for it. The payment step should follow verification of the finalized transaction, not trust in a conversational claim that the user approved it.
Choose the right consent path
When the user is present
The user sees and approves the closed checkout and payment. The trusted surface is responsible for obtaining informed consent before creating the user-signed mandate. This is the clearest path when the user needs to review the final cart or decide whether changed terms are acceptable.
Rank #2
- Use the, easy-to-use, and customizable POS to get started.
- Accept contactless payments, chip cards, Apple Pay, and Google Pay from anywhere, with improved connectivity, extended battery life, and enhanced security. Pay one low rate for every tap or dip.
- No long-term commitments or contracts, no monthly fees- and with offline payments, keep taking payments for up to 24 hours.
- Safely and securely accepts payments anywhere. Plus, get data security, 24/7 fraud prevention, and payment-dispute management at no extra cost.
- Use the, easy-to-use, and customizable POS to get started.
When the agent acts autonomously
The user approves constraints in advance; the agent then forms a closed checkout, and verifiers check that transaction against those constraints. AP2 describes the verifier as receiving closed mandates in either mode, but the trust basis differs: direct user signature in the present-user path, versus a user-signed open mandate and the agent key in the autonomous path.
Constraint choices can include allowed merchants, eligible line items and quantities, an amount and currency where represented in the applicable mandate or payment data, an expiration window, and whether the user must return to approve the finalized cart. AP2’s checkout-mandate documentation identifies merchant and line-item constraints, but it does not standardize every possible constraint in every implementation. Set expiration deliberately: AP2 recommends short-lived open mandates and says an agent must not reuse one for another checkout before it receives a rejection receipt for the previous attempt.
Rank #3
- 【Universal Compatibility】 - The MDB Payment Device to PC Converter is designed to connect a variety of MDB devices such as acceptors, bill receivers, and card readers effortlessly. It offers seamless integration with any vending equipment compliant with MDB specifications, ensuring versatility in your payment solutions.
- 【User-Friendly Interface】 - This USB adapter features a straightforward setup process. Simply connect it to your computer, and the adapter transforms MDB protocols into RS-232 serial protocols. This allows for easy communication between your vending machine and your PC, simplifying operations while providing reliable performance.
- 【Enhanced Control】 - With capabilities to control up to eight MDB-compatible devices simultaneously, this converter enhances your management efficiency. Whether you’re handling dispensers or bill acceptors, experience effective monitoring and command over your vending machine operations like never before.
- 【Robust Functionality】 - The MDB-PC USB converter supports a variety of interfaces, including cash interfaces (10H and 60H) and USD interfaces (40H). This broad support mechanism ensures compatibility across multiple configurations, making it an ideal solution for complex setups.
- 【Comprehensive Package】 - Each converter comes complete with required cables, a user guide, and a user agreement, providing everything you need for successful installation. Designed for easy implementation, enjoy a plug-and-play experience with reliable support for all essential MDB functions.
Keep identity, credential scope, and transaction approval distinct
These controls answer different questions. Agent authentication helps establish who sent a message and whether it was changed in transit. Credential scoping limits where or how a payment instrument can be used. Transaction binding connects the user’s authority to the particular finalized checkout. A sound design checks all three where the implementation supports them.
| Protocol or offering | What it addresses | What it does not establish by itself |
|---|---|---|
| AP2 | Mandates linked to a merchant checkout, with verification and signed receipts described in the AP2 specification. | It does not by itself define every checkout field, dispute-retention procedure, or chargeback outcome. |
| Visa Trusted Agent Protocol | Signed agent recognition, linked consumer/device identity, and payment-container data for browsing and payment interactions; Visa’s getting-started guide describes signature verification using the agent’s public key. | Agent or message authentication alone does not prove that a payment matches the user-approved checkout. |
| Universal Commerce Protocol (UCP) | Google describes UCP as a common language for commerce interactions among agents, merchants, and payment providers, compatible with AP2, A2A, and MCP. | Commerce coordination is not itself the same as authorization binding between a user mandate and a checkout. |
| Mastercard agentic-shopping material | Describes agent-specific tokens scoped by spending limits, merchant categories, purposes, or time windows, revocable by the consumer, and authentication such as passkeys or two-factor authentication. | These are Mastercard’s stated product-design controls, not evidence of a universal property of agentic payments or independent performance results. |
Google says checkout can take place on Google surfaces while the merchant remains merchant of record. That distinction matters: the surface where shopping happens, the protocol that carries checkout information, and the party responsible as seller are separate roles.
Rank #4
- Effortless payments and printing: Accept card payments and print payment receipts on the spot with the built-in 40 mm thermal printer.
- Faster sales processing: Use pre-set menus and catalogs to make transactions faster and smoother for you and your customers.
- Reliable and portable: Featuring a 6.5" HD touchscreen made from Corning Gorilla Glass and a powerful battery that lasts all day.
- Seamless connectivity: Stay connected with free mobile data and WiFi, ensuring uninterrupted transactions.
- Real-time payment tracking: Monitor payments and issue refunds right from your device, so you're always in control.
Make verification deterministic
AP2 says mandate validation and processing must occur in deterministic code even when a role is otherwise agentic. An LLM can help interpret a request, negotiate a cart, or assemble a proposed transaction; ordinary software should enforce the rules before payment is attempted.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Validate signatures and expected schemas and versions.
- Check mandate expiration and applicable merchant, item, quantity, amount, and currency constraints.
- Recompute the checkout hash and confirm it matches the payment mandate and the merchant-signed checkout.
- Check that the payment credential is scoped to the transaction and handle retries or replay attempts explicitly.
- Reject mismatches and require fresh authorization when the final checkout falls outside the user’s approved terms.
Do not silently treat a changed total, item, or merchant as covered by the earlier approval. Whether a change can proceed under an autonomous mandate depends on the actual constraints and checkout data the implementation verifies.
Best Value
- Compatibility - This POS display stand is compatible for Pax A35, Pax S300. Note: Please carefully confirm the POS machine model before purchasing.
- Easy Installation - Installs quickly using the included type adhesive tape or can be permanently installed to any surface via a drilled hole and bolt mount. And can be removed by heating the area with a hairdryer and using string/thread to detach it if needed.
- Adjustable Card Terminal Mount - The 360-degree swivel allows cashiers to effortlessly turn the device left and right to assist customers without leaving their side, while the 65-degree tilt ensures the terminal is positioned at the optimal angle for various counter heights.
- Commercial Strength - Steel construction gives this universal POS stand durability for use as counter payment terminal in almost any setting.
- Perfect Height - The Pax A35 credit card payment machine stands' ideal height of 4.7" is designed for optimal counter alignment. It provides ample clearance for card insertion and can be adjusted using the tilt feature. Once the perfect tilt angle is set, secure it in place with the included Allen key and wrench to prevent unwanted movement.
What receipts can—and cannot—prove
AP2 describes Checkout Receipts and Payment Receipts returned after mandate acceptance or rejection. Its verification process includes checking mandate integrity, recomputing the checkout hash, and matching receipt references. Together, mandates and receipts can preserve an integrity-protected account of the checkout and authorization presented to the participants.
That record can support an audit or a dispute, but AP2 leaves detailed dispute procedures, evidence retention, and retrieval requirements outside its specification. The mechanism does not itself guarantee a refund, determine legal liability, or resolve a chargeback. A production system needs its own documented process for retaining and retrieving the relevant checkout, mandate, and receipt records.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
