Who this is for
This guide is for a team preparing to evaluate a processor against a defined product and operating model. It is not a provider comparison, a technical certification, a pricing analysis, or a promise that a processor will support or approve a proposed program.
Decision map
Translate the product into states and events before translating it into an integration list. Describe what customers and operators should see when a transaction is initiated, accepted, declined, pending, completed, reversed, returned, disputed, corrected, or under review. Then identify which system and party acts at each transition.
Treat records as a set of purposes rather than one universal source of truth. Customer display, transaction processing, internal ledgering, settlement, reconciliation, reporting, investigation, and evidence may rely on different records. The evaluation should expose how those records connect and how discrepancies become accountable work.
Roles and dependencies
The company owns its product requirements and internal operating choices. The processor and every other counterparty retain their respective evaluation and delivery responsibilities. Legal, compliance, risk, finance, product, technology, and operations teams retain program-specific judgment.
Questions to ask
- Which state transitions and exceptions must be supported and observable?
- What are the interface, data, environment, access, and testing boundaries?
- How are reconciliation breaks, incidents, releases, and service issues assigned and escalated?
- Which records explain the event to customers, operators, finance, and reviewers?
- What proposed requirement is actually an assumption that still needs confirmation?
Adjacent capability handoffs
Connect owns the primary relationship evaluation. Use Processor Mapping to separate responsibilities, Developer & Integration to structure interface questions, and Support & Ticketing to frame operational handoffs. These are topical references, not availability statements.
Compare the sponsor-bank readiness guide and network-counterparty readiness guide so bank, processing, and network responsibilities remain distinct.
Primary next step
Review the Connect capability and convert the proposed product flow into a versioned state, interface, record, ownership, and exception map before evaluating processor fit.
Published after review. Claims status: approved. Reviewer: Todd. Module-status matrix checked on 2026-09-27; the matrix does not establish public availability for the linked modules.