Firmly (Firmly AI)

FIRMLY (FIRMLY AI)Manage supplier listing

Cross-network card enrollment, cardholder-verification and payment-intent telemetry, observed from inside a single router that abstracts Visa, Mastercard and Discover behind one API. The byproduct is a comparably-measured record of how each card network behaves for the same logical operation: enrollment path and BIN-detected network assignment, verification method actually required (Visa iframe handshake plus FIDO2, Mastercard iframe plus FIDO2, Discover with no cardholder-verification step at all), challenge trigger and completion outcomes, FIDO2 assertion success or failure at intent time, saved-card reuse via virtual_card_id without PAN re-entry, and card revocation events — all chained statelessly through a JWE flow_token so each step links into one tamper-evident flow ending in an order completion call

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Firmly (Firmly AI) and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Transaction & Payment Processing ServicesApplication Software
Instruments: equities
Categories

Dataset card

Type: not stated
Format: Tabular API event records chained by flow_token (JWE-encrypted state) and intent_id, plus persisted enrollment objects carrying virtual_card_id, card_art and masked PAN representation. Structured request and response payloads across a versioned REST surface (enroll, select-card, enroll/trigger, enroll/verify, intent, intent/challenge, card-art, cards/delete, then wallet-complete-order on a separate payment/vault domain). Card-art payloads are image assets
Volume: Modest volume with exceptional per-event structure: every flow emits a chained, JWE-linked sequence of enrollment, verification-challenge, verification-completion, intent, challenge and order-completion events with the network resolved from BIN. Est. tens of thousands to low hundreds of thousands of flow events to date. Separately a small reference asset is immediately licensable and holds no payment data at all: the BIN-to-network routing and verification-requirement mapping, which encodes which verification each network demands for which card class
Users: N/A as a consumer base — a B2B API integrated by destinations, not a consumer product, so end-user counts sit with the integrating destinations. Institutional estimate: tens of integrating destination accounts (inferred from a seed-stage, $2M-funded, 38-person company still documenting a single flagship agentic-pay surface)
History: 2 years
Update frequency: not stated
Growth: Active and current — a maintained public developer portal with versioned API references, a Headless SDK, a dedicated agentic-commerce solutions section, and agentic-pay surfaced as a primary destination rather than a legacy surface. Seed stage with $2M raised and 38 employees indicates active build-out rather than maturity
Launched: Company established ~2021-2022 (contact-provider organisation record from that window, $2M seed, Seattle); the Agentic Pay network-token-router product is ~2025-2026, dating to the current agentic-commerce cycle since it is positioned explicitly for AI-agent checkout
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site