Buy-side checkout infrastructure from Firmly. Each capability below is sourced from Firmly’s own docs (or marked not documented) and carries a status. Everything is claimed until independently verified — see the methodology for how a row becomes verified.
| Dimension | Value · source · evidence | Status |
|---|---|---|
| coverage | ~11M merchants / $900B+ GMV via platforms (Shopify/BigCommerce/Magento); discovery limited to your account's merchant domains“Connect to a $900B+ marketplace through a single API”source: developers.firmly.ai/introduction.mdevidence: none yet — not independently verified | claimed |
| execution | Standardization layer over merchant systems; order placed via a single Complete Order API call“Firmly acts as a standardization layer between your application and merchant systems, providing consistent cart operations regardless of the underlying platform.”source: developers.firmly.ai/concepts/how-firmly-works.mdevidence: none yet — not independently verified | claimed |
| payment | Caller supplies card, JWE-encrypted with Firmly's rotating public key; Klarna express flow“The credit card must be encrypted as a JWE token”source: developers.firmly.ai/api-reference/payment/complete-order-v2.mdevidence: none yet — not independently verified | claimed |
| auth | Two models — Browser Session (client) + Server-to-Server token; header-based“Server-to-Server (S2S) authentication enables your backend services to make authenticated API requests to Firmly APIs.”source: developers.firmly.ai/api-reference/authentication/server-to-server.mdevidence: none yet — not independently verified | claimed |
| access | Marketed self-serve ("self-onboard in minutes"); actual developer key access not documented“Self-onboard in minutes”source: www.firmly.ai/connectevidence: none yet — not independently verified | claimed |
| protocols | REST/JSON API per the developer docs. Firmly markets support for UCP, ACP, MCP, AP2, TAP, KYA on firmly.ai/connect, but the dev docs name none of them.“UCP, ACP, MCP, AP2, TAP, KYA and every standard that follows”source: www.firmly.ai/connectevidence: none yet — not independently verified | claimed |
| discovery | Merchant PDP URL, product ID, or cross-merchant Discovery search“Extracts product information from a merchant's product detail page (PDP) URL.”source: developers.firmly.ai/api-reference/catalog/get-product-from-url.mdevidence: none yet — not independently verified | claimed |
| returns | Read-only status (returned/partially_returned + refund breakdown); no endpoint to initiate a return“retrieves the current status of a placed order directly from the merchant platform”source: developers.firmly.ai/api-reference/orders/get-order-status.mdevidence: none yet — not independently verified | claimed |
| regions | not documentedsource: not documented by the vendor | not documented |
| pricing | not documentedsource: not documented by the vendor | not documented |
| sandbox | not documented (no sandbox host; examples target a demo store staging.luma.gift, not a Firmly sandbox)source: not documented by the vendor | not documented |
| status | Live (stated on firmly.ai/connect; no dev-doc status label)“Now live”source: www.firmly.ai/connectevidence: none yet — not independently verified | claimed |
Status per capability: claimed (from the vendor’s docs) · verified (we ran it) · failed (we ran it; it did not do the claim) · unverifiable (no way for us to test). How we test: methodology.