Skip to content

Mobile & In-Person Payments Arena

Mobile & In-Person Payments arenaBuyer checklist

Every requirement we judge mobile & in-person payments products against, as a ready-to-send RFP checklist — with each item's priority, why it matters, and how the top-ranked products score on it today.

52 requirements · 12 themes · verdicts for 4 products · updated 2026-09-16 · priorities mirror the story weights our scoring uses (methodology)

Procurement report →
Show the markdown export
# Mobile & In-Person Payments — buyer checklist (RFP)

Derived from ProductArena's evidence-graded user-story taxonomy for Mobile & In-Person Payments: 52 judged requirements. Priorities mirror story weights (3 = must-have, 2 = should-have, 1 = nice-to-have).

## Accept payments

- [ ] **[must-have]** Sign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same week
- [ ] **[must-have]** Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in person
- [ ] **[must-have]** Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a reader
- [ ] **[should-have]** Split a single sale across multiple payment methods or payers
- [ ] **[should-have]** Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminal

## Agenticness

- [ ] **[must-have]** Plug MCP servers into this product so it can use their tools
- [ ] **[must-have]** Connect an agent via an official MCP server
- [ ] **[must-have]** Drive the product through a documented public API
- [ ] **[must-have]** Delegate tasks to a built-in AI assistant inside the product
- [ ] **[should-have]** Point an agent at llms.txt or agent-oriented docs
- [ ] **[should-have]** Run the product headlessly / in CI for automation
- [ ] **[should-have]** Use an official CLI
- [ ] **[should-have]** Issue scoped/least-privilege API credentials for an agent
- [ ] **[should-have]** Build against official SDKs
- [ ] **[should-have]** Subscribe to events via webhooks
- [ ] **[should-have]** Get AI-generated insights and suggestions from my data inside the product
- [ ] **[should-have]** Set up automations that run autonomously in the background
- [ ] **[should-have]** Operate the product with natural-language commands
- [ ] **[should-have]** Explore an interactive API reference with runnable examples
- [ ] **[should-have]** Download a machine-readable API spec (OpenAPI or equivalent)
- [ ] **[should-have]** Rely on versioned APIs with a documented deprecation policy
- [ ] **[nice-to-have]** Test against a sandbox environment without touching production data

## Automation depth

- [ ] **[must-have]** Define rules that trigger actions automatically on events
- [ ] **[should-have]** Perform bulk operations across many items at once
- [ ] **[should-have]** Schedule recurring jobs or workflows
- [ ] **[nice-to-have]** Version, review, and roll back my automations

## Catalog receipts

- [ ] **[should-have]** Manage an item catalog with inventory counts that stay in sync across registers and channels
- [ ] **[nice-to-have]** Issue digital (email/SMS) or printed receipts that meet card-network requirements

## Checkout integration

- [ ] **[must-have]** Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven API
- [ ] **[should-have]** Embed in-person payments into my own iOS or Android app with official mobile SDKs
- [ ] **[should-have]** Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automations
- [ ] **[should-have]** Test my in-person integration end-to-end with a simulated reader or test card environment before going live

## Disputes refunds

- [ ] **[must-have]** Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review
- [ ] **[should-have]** Get notified of chargebacks and submit dispute evidence before the deadline
- [ ] **[should-have]** Issue full or partial refunds back to the original card from the point of sale, dashboard, or API

## Hardware fleet

- [ ] **[must-have]** Have an agent provision a new location end-to-end via API — creating the location and registering its readers
- [ ] **[must-have]** Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
- [ ] **[should-have]** Run multiple locations with per-location devices, settings, and reporting
- [ ] **[should-have]** Pair a card reader with the POS app or register it to my account and take a payment within minutes

## Offline reliability

- [ ] **[should-have]** Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returns

## Openness

- [ ] **[must-have]** Export all of my data in open formats and leave
- [ ] **[must-have]** Self-host the core product
- [ ] **[should-have]** Do everything through the API that I can do in the UI
- [ ] **[should-have]** Read the product's source under an open license

## Payouts reconciliation

- [ ] **[must-have]** Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger
- [ ] **[should-have]** See when each payout lands and speed it up (next-day or instant) when I need the cash
- [ ] **[should-have]** Reconcile daily takings against payouts with itemized transaction and fee reports

## Pci compliance

- [ ] **[should-have]** Keep my PCI scope minimal because card data is captured end-to-end by certified readers and vendor systems, with vendor guidance on my remaining obligations

## Privacy posture

- [ ] **[must-have]** Prevent my data from being used to train AI models
- [ ] **[should-have]** Choose where my data is stored (region/residency)
- [ ] **[should-have]** Control data retention and deletion
- [ ] **[should-have]** Opt out of telemetry and usage tracking

---

Source: https://ultrametric.ai/productarena/arena/mobile-payments (evidence-graded verdicts for 4 products) · methodology: https://ultrametric.ai/productarena/methodology

Chips show the top 4 ranked products' current verdict on each requirement — ✓ full · ~ partial · ! disputed · — none · n/a not applicable.

Accept payments — stories about accept payments in this arenaAccept payments· 5 items

Stories about accept payments in this arena

Agenticness — how well agents can access and operate the productAgenticness· 17 items

How well agents can access and operate the product

Automation depth — how much of the product can run unattendedAutomation depth· 4 items

How much of the product can run unattended

Catalog receipts — stories about catalog receipts in this arenaCatalog receipts· 2 items

Stories about catalog receipts in this arena

Checkout integration — stories about checkout integration in this arenaCheckout integration· 4 items

Stories about checkout integration in this arena

Disputes refunds — stories about disputes refunds in this arenaDisputes refunds· 3 items

Stories about disputes refunds in this arena

Hardware fleet — stories about hardware fleet in this arenaHardware fleet· 4 items

Stories about hardware fleet in this arena

Offline reliability — stories about offline reliability in this arenaOffline reliability· 1 item

Stories about offline reliability in this arena

  • merchant-ops userKeep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returns

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 4 products fully deliver this today

    should-have

Openness — open source, data portability, and self-hosting storiesOpenness· 4 items

Open source, data portability, and self-hosting stories

Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliation· 3 items

Stories about payouts reconciliation in this arena

Pci compliance — stories about pci compliance in this arenaPci compliance· 1 item

Stories about pci compliance in this arena

  • developerKeep my PCI scope minimal because card data is captured end-to-end by certified readers and vendor systems, with vendor guidance on my remaining obligations

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Privacy posture — data-handling and privacy storiesPrivacy posture· 4 items

Data-handling and privacy stories

Full evidence behind every verdict lives on the arena page and each product page — chips above deep-link straight to the judged story.