Quick context: why this matters now

• How urgent is adding instant, irrevocable payments for your top commercial clients right now? Options: Critical, must act within 30 days, High priority, within 2-3 months, Medium priority, this quarter, Low priority, later this year
• Which client relationships or segments are driving the urgency, and how many commercial accounts does that cover? Options: Top 1 client, Top 5 clients, Top 10 clients, Top 20 clients, A particular industry segment
• How many deposit dollars would you estimate are at risk if you cannot match competitors' instant payables? Options: Under $5M, $5M–$50M, $50M–$200M, Over $200M, Unsure
• If a pilot proves required speed and fraud tolerance within eight weeks, would your organization be willing to commit to a production rollout? Options: Yes, subject to standard legal terms, Yes, with expedited legal review, Maybe, requires board/exec approval, No, cannot commit now

How payments actually move today and where they stall

• Your current payment flow was built for batch windows—how often does that mismatch cause failed client expectations or lost business? Options: Daily, Weekly, Monthly, Rarely, Unsure
• How many transactions per day do your top 20 commercial clients originate on average? Options: Under 1,000, 1,000–10,000, 10,000–100,000, Over 100,000, Unsure
• During peak events such as payroll or large disbursements, what is your 95th percentile throughput requirement? Options: Under 50 tps, 50–500 tps, 500–2,000 tps, Over 2,000 tps, We don't measure this
• What core system or message format currently throttles your ability to respond in seconds rather than hours?
• Who owns reconciliation and exceptions today, and how long do settlement gaps typically remain open? Options: Payments ops team, Treasury team, Shared ops/treasury, Outsourced provider, Other

When speed becomes irrevocable, what breaks first

• If an instant, irrevocable payment is incorrectly blocked or allowed, what downstream loss or client churn do you fear most? Options: Direct customer loss, Regulatory penalty, Large settlement discrepancy cost, Reputational damage, Operational load increase
• How often do high-value payments get flagged by your current fraud engine and later confirmed as legitimate? Options: Daily, Weekly, Monthly, Rarely, Unsure
• What is your acceptable false-positive rate for high-value irrevocable payments? Options: Under 0.1%, 0.1%–0.5%, 0.5%–1%, Over 1%, Undetermined
• Which roles must approve customer notifications or remediation when a legitimate payment is blocked, and what is their typical SLA to respond?
• Which single fraud metric, if not met in pilot, would cause you to halt the project immediately? Options: False-positive rate, False-negative rate, Decision latency, Unexplained settlement variance, Other

Who will own money, liquidity, and the first line of risk

• If settlement becomes instant, who will be accountable for intraday liquidity and first-line loss exposure inside your organization? Options: Treasury, Head of Payments, CFO, Shared committee, Other
• Do you currently maintain intraday credit lines or prefunding arrangements that would be used for instant settlement? Options: Yes, established lines, Yes, but limited, No, we would need to create them, Unsure
• How many hours of treasury or payments headcount are required daily now to manage large outbound commercial payments? Options: Under 2 hours, 2–6 hours, 6–12 hours, Over 12 hours, Unsure
• If a pilot requires a temporary prefunding buffer of 5% to 15% of peak daily volume, what budget or approval path would you need to proceed? Options: Already budgeted, Requires treasury approval, Requires CFO approval, Requires board approval, Would not approve

Integration realities we must clarify now

• Your core and fraud systems were built for batch decisioning, which specific integration point threatens to extend the timeline by months?
• Which systems must we integrate with for a pilot, select all that apply Options: Core ledger, Payments switch/gateway, Fraud engine, Treasury management system, Compliance screening system, Reconciliation engine
• Are production and test APIs available for each selected system, or will custom adapters be required? Options: All have APIs and test endpoints, Most have APIs, one requires custom work, APIs unavailable for key systems, Unknown, need to investigate
• Please list the team or vendor that controls each integration point and whether they will commit engineering resources during the pilot
• If a required integration cannot provide test endpoints within six weeks, would you pause the pilot or realign scope to reduce integration dependency? Options: Pause pilot, Realign scope, Use simulated endpoints, Proceed and accept delay

Regulatory and compliance gates to clear

• Which compliance approval or regulatory review is most likely to delay live instant settlement at your institution? Options: AML program review, Sanctions screening certification, Board-level policy approval, Third-party vendor due diligence, Privacy/data-sharing review
• Do you require separate AML or sanctions certification for instant irrevocable rails beyond your current checks? Options: Yes, additional certification required, No, current program covers it, Unsure, needs legal review
• Name the compliance and legal roles or committees that must sign off on pilot data sharing and screening rules and their expected review timelines
• How long does your internal legal review of new payment flows typically take, and what could shorten that timeline? Options: Under 2 weeks, 2–4 weeks, 4–8 weeks, Over 8 weeks, Not sure
• Is there a regulatory prohibition or board policy that would prevent irrevocable instant settlement for any of your commercial client segments? Options: Yes, for some segments, No, allowed, Unsure

What alternatives are you weighing right now

• If you decided not to buy from an external partner, how would you bring instant capability in-house or via your incumbent, and what is the real chance that option succeeds?
• Which of the following options are you actively evaluating or have evaluated? Options: Upgrade with incumbent core vendor, Partner with another payment network, Build in-house, Use a payment gateway provider, Accept competitive loss and do nothing, Other
• For each option you selected, what single condition would have to be true for you to stay with that approach instead of switching to a new partner?
• Has anyone on your team proposed a do-it-yourself build, and if so who proposed it and what resources did they estimate? Options: Yes, senior engineering proposed build, Yes, payments ops proposed build, No one has proposed build, Unsure
• If our pilot demonstrates the speed and fraud tolerance you require, which alternative would still beat that outcome and why would you choose it?

Acceptance metrics that would close the loop

• If the pilot proves sub-two-second confirmations, 0.5% fraud false positives at scale, and zero settlement anomalies during peak, what is your expected approval path to convert to production? Options: Payments ops + treasury sign-off, CFO sign-off required, Board level approval required, Procurement and legal finalization only
• Which of the following metrics do you require us to report from the pilot? Options: Peak throughput (tps), 99th percentile latency (ms), False-positive rate, False-negative rate, Settlement discrepancy count, End-to-end confirmation time
• What absolute thresholds do you require for throughput (transactions per second), 99th percentile latency in milliseconds, and acceptable fraud false-positive rate on payments over $50,000?
• List the approvers who must sign the acceptance certificate and the lead time each requires after pilot results are shared
• If acceptance thresholds are met, how quickly can procurement and legal complete a commercial and SLA agreement? Options: Within 2 weeks, Within 4 weeks, Within 8 weeks, Longer than 8 weeks

Operational handoff: support, runbooks, and escalation

• Assuming production conversion, what specific operational failure in the first 90 days would make you pause live instant rails? Options: Unresolved settlement anomalies, High false-positive rate affecting top client, Multiple unavailable hours, Liquidity shortfall causing failed payments, Other
• Provide the job title and team who will be the named incident owner for 24/7 escalations during and after rollout
• Which support model do you prefer post-go-live? Options: Vendor-managed 24/7 support, Shared NOC with vendor, Fully internal support, Hybrid with vendor retained for tier 2/3
• List runbook elements, staffed hours, and SLA penalties that are non-negotiable for you during the 90-day ramp
• If a named treasury client reports a settlement discrepancy, what time-to-resolution would you insist we meet to avoid losing that client? Options: Under 1 hour, 1–4 hours, 4–24 hours, Over 24 hours

Signals, timing, and practical next steps

• If the pilot shows the target metrics, what internal obstacles could still prevent an immediate production commitment? Options: Budget freeze, Legal procurement delays, Board concerns, Integration gaps, No further obstacles
• Which of the following signals would accelerate your decision to proceed to commercial negotiation? Options: Pre-approved budget, COO sign-off, Draft SLA available, Completed certification, Named internal champion
• List the roles that must attend the pilot kickoff and the weekly time commitment required from each
• When would you prefer to start a 6 to 8 week pilot? Options: Immediately, Within 30 days, Next quarter, Later this year, Unsure
• If we scope a pilot that isolates low-risk corridors and meets your acceptance metrics in production-like tests, will you sign a conditional commitment to proceed to commercial terms? Options: Yes, with timeline conditions, Yes, subject to legal terms, Maybe, need internal approvals, No

• Integrate Core Banking Adapter
• Onboard Faster-Payments Network Link
• Deploy Message Formatting and Routing Engine
• Activate Real-Time Settlement Ledger
• Configure Fraud Scoring and Rules Engine
• Enable Compliance Screening and Sanctions Filtering
• Provision Liquidity Management Interface
• Implement Transaction Confirmation API
• Deploy Exception Handling and Inquiry Workflow
• Execute Network Certification and Test Transactions
• Perform Throughput Load Tuning and Optimization
• Train Operations and Treasury Teams on Platform
• Activate 24x7 Monitoring and Alerting

Integrate Core Banking Adapter

• Do you have an existing integration adapter or middleware for your core ledger (name the adapter type or 'none')?
• Which core account namespaces or ledger account IDs will receive instant-settlement entries (provide account ID patterns or sample IDs)?
• How will you authenticate API calls from the platform to your core (mutual TLS, OAuth2 client credentials, IP allowlist, other)? Options: Mutual TLS, OAuth2 client credentials, IP allowlist, Other
• Specify the transaction posting workflow your core uses for real-time credits (immediate ledger entry, batch posting, pending queue) and any lifecycle states we must map. Options: Immediate ledger entry, Batch posting, Pending queue / manual settle, Other
• Provide the expected mapping rules between payment message fields (ISO 20022 pain.001 / proprietary) and your core fields for payer account, beneficiary account, value date, and transaction reference.
• Who on your team owns connection testing and validation with the core (name role and escalation contact type, e.g., 'platform integration lead / email')?

Onboard Faster-Payments Network Link

• Which faster-payments network connectivity option will you use for pilot (direct network link, hosted gateway, or partner aggregator)? Options: Direct network link, Hosted gateway, Partner aggregator, Undecided
• Do you have existing bilateral clearing agreements or channel credentials for the chosen faster-payments rail (Yes / No)? Options: Yes, No
• When can you allocate a test participant ID or channel certificate for the pilot environment (date or 'TBD')?
• Describe required message-level features the network must support for your flows (ISO 20022 pain.001 immediate confirmation, asynchronous status callbacks, MDT fields for corporate references).
• Identify any routing restrictions for pilot transactions (geo limits, currency controls, value caps per message) and list the value cap thresholds.
• Who will sign network onboarding paperwork and who is the operational contact for network-level incidents (role and contact method)?

Deploy Message Formatting and Routing Engine

• Which message formats must the engine accept and emit during pilot (ISO 20022 pain.001, proprietary XML, JSON API payload, other)? Options: ISO 20022 pain.001, Proprietary XML, JSON API payload, Other
• How should message enrichment happen for corporate reference data (use your customer ID mapping table name or describe lookup rules)?
• Specify routing rules for outgoing payments (by beneficiary bank identifier, by value threshold, or by risk score field) and give one example rule.
• Provide expected schema for reconciliation reference fields (transaction reference, settlement reference, your internal trace ID) that must be preserved end to end.
• Which transformation tests do you require during pilot (sample pain.001 -> network XML, round-trip ID preservation, character-set / UTF-8 checks)?
• Who will approve production-ready message mappings and where will approved mapping artifacts be stored (repository or folder path)?

Activate Real-Time Settlement Ledger

• What ledger account or GL codes will be used for pilot instant-credit and instant-debit settlement entries (provide GL codes or account ID patterns)?
• How is settlement finality recorded in your core (final ledger posting, pending then final, or manual confirmation) and which ledger state flags must be set? Options: Final ledger posting, Pending then final, Manual confirmation required, Other
• Specify reconciliation file format and cadence you need from the ledger for pilot (daily CAMT.053, intra-day CSV, immediate webhook on settlement). Options: Daily CAMT.053, Intra-day CSV, Immediate webhook, Other
• What prefunding or intraday liquidity threshold for the settlement account must be enforced before the pilot is allowed to route payments (amount or percentage)?
• Who on your treasury team will be the named owner for settlement ledger anomalies and what is the escalation phone/email workflow?
• What acceptance criteria will confirm the settlement ledger is correct in pilot (reconciliation match rate, settlement finality within X seconds, and example reconciliation threshold)?

Configure Fraud Scoring and Rules Engine

• Which fraud signals must be available in pilot for scoring (device fingerprint, velocity by account, beneficiary velocity, anomaly score from your AML watchlist)?
• How will you map your existing fraud rule IDs to the platform rule set (provide sample rule ID and desired behavior mapping)?
• Indicate the high-value thresholds that should trigger stricter scoring or manual review during pilot (value in currency or range). Options: Under threshold, Threshold X-1, Threshold X-2, Custom
• Describe the manual-review workflow for flagged irrevocable payments (notification channel, ticket ID pattern, and average decision SLA).
• What false-positive and false-negative rate targets must pilot meet for the fraud engine to be accepted (specify percentages for each)?
• Who will be the fraud operations contact that reviews rule tuning requests and provides labeled incident examples (role and contact method)?

Enable Compliance Screening and Sanctions Filtering

• Which sanctions/PEP screening lists must be applied in pilot (domestic watchlist, global sanctions list equivalent, internal denylist)? Options: Domestic watchlist, Global sanctions list, Internal denylist, All of the above
• How should screening be performed on message payloads (pre-send screening on payer, post-receive beneficiary screening, or both)? Options: Pre-send on payer, Post-receive on beneficiary, Both
• Specify the screening matching thresholds for fuzzy name matches and whether manual review is required for medium-confidence hits.
• Where will compliance decision logs be archived for audit (S3 bucket, secure file share, or compliance repository) and what retention period is required? Options: S3 bucket, Secure file share, Compliance repository, Other
• Who in your compliance team signs off on screening rule exceptions and what evidence do they require (case ID, payee documents, transaction history)?
• How quickly must a screening decision be returned during pilot to avoid blocking real-time flows (maximum latency in milliseconds)?

Provision Liquidity Management Interface

• Do you maintain a prefunding account or intraday credit line for real-time rails and provide the account identifier type (internal account ID, external clearing account)? Options: Prefunding account, Intraday credit line, Both, None
• How will the platform query or reserve funds before routing a payment (balance API, reservation call, periodic snapshot)? Options: Balance API, Reservation call, Periodic snapshot, Other
• Specify your acceptable liquidity thresholds and alerting levels (e.g., maintain at least 20% buffer of expected peak daily outflow).
• Which treasury systems must receive intraday liquidity feeds (treasury workstation, cash position file name or API endpoint)?
• Who authorizes automatic top-ups or intraday sweeps from your funding account and what approval channel must be used?
• How frequently must liquidity state be reconciled during pilot (real-time, every 15 minutes, hourly)? Options: Real-time, Every 15 minutes, Hourly, Daily

Implement Transaction Confirmation API

• Which confirmation pattern do you require for pilot: immediate synchronous confirmation, asynchronous webhook callback, or both? Options: Immediate synchronous confirmation, Asynchronous webhook callback, Both
• Provide the confirmation callback URL(s) or API endpoint patterns the platform should use in pilot and the expected authentication method.
• Specify the confirmation payload fields you need retained for customer receipts (confirmation ID, settlement timestamp, ledger reference).
• How should duplicate confirmations be handled by your systems (idempotent by confirmation ID, dedupe window in seconds)?
• Who will validate confirmation payloads in pilot and where will validation test cases be stored (UAT repo path or test plan ID)?
• When do you require confirmation events to be considered the authoritative record for the customer-facing channel (time after settlement in seconds)?

Deploy Exception Handling and Inquiry Workflow

• Which exception types must be captured during pilot (failed settlement, timeout confirmation, routing error, screening hold)? Options: Failed settlement, Timeout confirmation, Routing error, Screening hold, Other
• Describe the inquiry lifecycle for a disputed instant payment (ticket creation source, SLA for first response, resolution SLA).
• Indicate the integration points for exceptions into your CRM/Ticketing system (API endpoint, file drop, email-to-ticket) and provide sample routing rules. Options: API endpoint, File drop, Email-to-ticket, Other
• Who is the operational owner for exception triage and what shift coverage is required during pilot (hours and role)?
• Specify required audit trail elements for exceptions (original message, rule hits, personnel actions with timestamps) and retention period.
• How should recovered or reversed funds be recorded for reporting (reversal ledger entry format, reversal reference mapping)?

Execute Network Certification and Test Transactions

• Which network certification test cases must be completed in pilot (connectivity, message validation, end-to-end settlement, failover)?
• Where will test transaction artifacts be staged (UAT environment name or test ledger account IDs) and who provides test credentials?
• When do you need signed test-certification evidence for audit (date) and what format do you require (test report PDF, signed checklist)? Options: Test report PDF, Signed checklist, Certificate of completion, Other
• Which negative test scenarios are mandatory (message truncation, corrupted checksum, insufficient funds) and list one required scenario.
• Who is the approver for network certification sign-off and what evidence must they review (test logs, reconciliation samples)?
• How many test transactions at peak concurrency do you require the certification run to include (transactions per second or concurrent sessions)?

• decision_readiness
• current_state
• desired_state
• success_criteria
• gaps
• stakeholders
• desired_state
• stakeholders
• current_state
• success_criteria
• decision_readiness
• gaps
• stakeholders
• current_state
• desired_state
• gaps
• success_criteria
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Order Form / Subscription Agreement
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Pilot-to-Production Conversion Agreement
• Liquidity & Settlement Addendum
• Data Processing & Compliance Addendum (DPA)
• Support & Maintenance Addendum
• Change Order Agreement

• Go-live Health Check
• First Measurement Review
• Acceptance Gate Meeting
• Operational Quarterly Review
• Annual Outcomes and Remediation Review

• Maintain a prioritized queue of operational enhancements and agree timing for at least the next quarter.
• Produce a clear pass or fail result for each acceptance criterion recorded in Pilot Evaluation with supporting evidence.
• Document remediation tasks and timelines for any unmet criteria so the team can close gaps without ambiguity.
• Confirm the planned decommissioning state and timeline for the incumbent payment system to prevent dual-running and adoption erosion.
• Publish the signed acceptance record or documented buyer approval and store it in the shared workspace.
• Open remediation tickets for any failed or conditional criteria with explicit verification steps and completion dates.
• Execute the incumbent decommissioning or read-only configuration and confirm data archival/migration status with a completion date.
• Schedule a follow-up verification check for remediation items on a fixed date before full production ramp.
• KPI trends against Pilot Evaluation targets
• Confirm throughput and settlement success metrics remain within acceptable thresholds compared to Pilot Evaluation targets.
• Ensure incident burn-down is progressing and no high-severity items remain unassigned or undated.
• Reconfirm agreed success criteria and owners
• Resolve or re-prioritize any open high-severity incidents and publish updated resolution dates.
• Adjust operational runbooks or alert thresholds if recurring incidents indicate monitoring gaps.
• Provide a quarterly compliance summary showing screening false-positive trends and actions taken.
• Yearly trend analysis for latency and fraud false-positive rate
• Confirm that long-term latency and fraud false-positive trends meet the expectations set in Pilot Evaluation or document required multi-quarter remediation.
• Close or escalate remediation items older than 90 days with a clear resolution plan.
• Validate the operational support model and shared channel remain effective for 24/7 real-time payments operations.
• Publish the annual performance report comparing median and 95th percentile latency and fraud false-positive rate to Pilot Evaluation targets.
• Create remediation plans for any multi-quarter gaps with milestone dates and verification criteria.
• Update runbooks and escalation contact lists to reflect any changes from the past year and distribute to the shared channel.
• Confirm the production cutover completed and no high-severity deployment defects remain open.
• Establish the initial list of blockers with target resolution dates and owners recorded in the shared channel.
• Verify that the buyer's primary commercial pilot clients are able to send and receive test transactions end-to-end.
• Publish a post-cutover checklist with verification status for network certification, API connectivity, and credential rotation.
• Open and assign tickets for any high-severity defects discovered during validation, with target resolution dates.
• Share an initial adoption summary showing number of pilot clients onboarded and basic volume trends for the next check-in.
• Present first dataset against Pilot Evaluation targets
• Determine whether transaction confirmation latency and fraud false-positive rate are trending toward Pilot Evaluation targets or require remediation.
• Create a prioritized remediation plan with concrete tasks and dates to reach the acceptance gate.
• Confirm monitoring thresholds and alerting for latency and fraud signal regressions.
• Adjust fraud scoring thresholds or rule mappings to reduce false positives and document expected impact and verification method.
• Provision additional liquidity or pre-funding buffers for peak windows and record the change in the liquidity runbook.
• Update integration configuration (endpoints, timeouts, retries) to address identified throughput bottlenecks.
• Publish the date and data snapshot that will serve as the baseline for the acceptance gate.
• Restate acceptance criteria and numeric targets
• Incident and SLA adherence summary
• Throughput and peak behavior review
• Deployment and cutover validation
• Long-running remediation and technical debt review
• Present outcome data against each acceptance criterion
• Early adoption and usage signals
• Open issue backlog and remediation progress
• Root-cause diagnosis for any metric shortfalls
• Document pass or fail per criterion and rationale
• Operational readiness and support model health
• Compliance posture and audit findings
• Open issues and immediate blockers
• Capture formal acceptance decision and signatory details
• Agree corrective actions and timeline to acceptance gate
• Compliance and AML screening results
• Agree remediation items and resolution timeline
• Agree immediate remediation actions
• Shared channel health and enhancement request queue
• Agree next 12-month remediation and monitoring commitments
• Confirm monitoring and alerting adjustments
• Incumbent system wind-down and data handling