Financial Services
›
Financial Services & Banking
›
Payments & Card Networks
Payment Network Services
Regulated environments where trust, compliance, and operational resilience are non-negotiable.
Visa
Mastercard
American Express
The Clearing House
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles (cards, payments, treasury, and execs), timeline, regulatory constraints, and what ‘good’ looks like for each stakeholder.
Alignment Questions
Let’s Start — Who’s in Your Corner?
- Who will actively participate in this program from your side? Please list names, titles, and best contact for each person.
- Which of these roles are already engaged or aware of this initiative?
- Which of the people you named will be the primary day-to-day owner for technical integration and who will be the commercial/contract owner?
- Is there an internal RACI or decision matrix we should review that defines approvers, consultees, and implementers for vendor partnerships?
- Are there external parties (partner banks, processors, regulators, major merchants) who must be in these conversations? Who are they and how do they influence decisions?
If One Person Says No — Who Is It?
- Who inside your organization could single-handedly block the program, and what would their main objection likely be?
- Which stakeholder groups prioritize commercial economics over reliability or vice versa?
- For the top three influencers, list the concrete metrics or thresholds (eg. interchange uplift %, settlement lag hours, fraud rate) that would make them comfortable.
- Have any stakeholders previously rejected a similar integration or network relationship? If yes, what reasons were given and how were they resolved (if at all)?
- How do internal governance cycles (procurement review, risk committee, board approvals) affect the speed and certainty of decisions?
Deadlines That Create Pressure — Tell Us the Worst-Case Impact
- If a go-live misses your target date, what specific business outcomes are at risk in the next 30/90/180 days (lost volume, campaign delays, regulatory exposure)?
- What is your target go-live date or window, and is it tied to any commercial events (product launches, partnerships, seasonal peak) or regulatory milestones?
- Are there immovable external dates (partner blackouts, regulatory implementation deadlines, merchant contractual go-lives) we must align with?
- What internal milestones must be complete before your team can start technical integration (legal review, compliance checklist, procurement signoff, production keys)?
- If issues arise during integration, how much schedule flexibility do you realistically have?
Regulatory Red Lines — What Would Make You Stop?
- What regulatory or supervisory outcomes would force you to pause or cancel this partnership?
- Which supervisory bodies and regulations most directly govern your ability to onboard a new network (eg. central bank, financial conduct authority, card scheme regulations, privacy/data protection)?
- Do you have any open regulatory examinations, enforcement actions, or ongoing remediation programs that could constrain contracting or certification timelines?
- What specific compliance artifacts must be provided pre-contract (SOC2/ISO reports, AML/KYC attestations, PCI-DSS evidence, regulatory letters)?
- Are there jurisdictional restrictions (data residency, cross-border settlement prohibitions, sanctioned-country exposure) that would block parts of our proposed solution?
What ‘Good’ Actually Means to Each Person in the Room
- Imagine your exec reports back in 90 days — what three headline metrics would prove this was a strategic success?
- For the cards/product owner: what interchange, approval rate, or revenue metrics are must-haves?
- For treasury/finance: which settlement terms, float/FX behaviors, or cashflow KPIs must we guarantee?
- For operations/security: what target uptime and recovery objectives (RTO/RPO) are non-negotiable?
- For merchant or acquiring stakeholders: what acceptance coverage, POS compatibility, or processing fee levels would be considered ‘good enough’?
Where Things Break Today — The Real Operational Pain
- What specific authorization, clearing, settlement, or tokenization failures have you experienced in the last 12 months (give an example and impact)?
- Which parts of your current value chain cause the most manual work or reconciliation burden?
- How do recurring failures affect customer relationships or merchant retention? Please share a recent story if possible.
- What monitoring and alerting do you have today, and where are blind spots that make problem detection slow or unreliable?
- When an operational issue occurs, what is your typical time-to-resolution and escalation path?
Try On the Best-Case — What Would You Celebrate?
- If we delivered everything perfectly, what new customer behaviour or business outcome would convince you this partnership was transformative?
- Give one concrete pilot scenario (region, product, transaction mix, volume) that would prove value quickly for your team.
- Which KPIs should appear on a shared executive dashboard during and after rollout?
- What constraints must remain in place even in this ideal outcome (eg. regulatory guardrails, conservative risk thresholds)?
- What would success look like to your customers (cardholders, merchants)? Describe customer-facing improvements you’d celebrate.
Signals of Readiness — Small Steps That Mean Big Commitment
- What’s the smallest, irreversible signal or deliverable you’d need from us to decide to proceed (sample contract clause, regulatory letter, pilot scope, technical sandbox access)?
- Which commercial terms are easiest to agree and which will require executive-level negotiation?
- Who exactly needs to sign off on the SOW, contract, and production access (names/roles)?
- What would a realistic cadence for decision checkpoints look like (weekly working group, biweekly exec steerco, milestone gating)?
- What are the non-negotiable internal approvals or governance steps we should queue up now to avoid delays later?
-
Current State Mapping
Document existing authorization, clearing, settlement, tokenization posture, fee structures, merchant acceptance footprint, and operational failure modes.
Current State
Where We Stand Today — a quick snapshot
- What primary connection model do you currently use to the network (e.g., direct switch, gateway, processor API)?
- What are your typical monthly transaction volumes and your peak transactions per second (TPS) during busiest hours?
- Which payment products do you actively support today?
- Who are the internal and external teams we should know for operational decisions (names, roles, and escalation contacts)?
- List the core systems and vendors in your authorization → clearing → settlement chain (switch, gateway, issuer processor, acquirer processor, settlement engine).
What’s silently costing you time or revenue?
- How often do you experience unexplained declines or authorization mismatches that materially affect authorization rates?
- When declines increase, where do they tend to cluster—certain merchant categories, regions, acquiring partners, or card products?
- Tell us about a recent incident where a payments issue caused lost revenue or elevated customer contacts — what happened and what was the impact?
- How do reconciliation gaps currently surface (automated alerts, manual discovery, acquirer dispute)?
- How does it feel inside your team when reconciliation or settlement surprises appear—frustrated, resigned, reactive, or something else?
Are your transactions actually reaching the finish line?
- How reliable and timely is your settlement flow—are funds posted according to expected timelines?
- What percentage of settled batches require adjustments, reversals, or off-cycle corrections each month?
- Describe your reconciliation cadence and the tools or reports you use to validate clearing and settlement accuracy.
- Where do settlement disputes usually originate—interchange mis-coding, FX differences, acquirer fees, or failed remittances?
- How long does it typically take to detect and resolve a settlement exception from detection to closure?
How confident are you in your token and digital identity posture?
- Where are you in your tokenization journey—are tokens used in production, pilot, or not yet implemented?
- Which token types and ecosystems do you support today (network tokens, wallet tokens, token vaults, POS tokens)?
- What operational issues have you experienced related to token lifecycle (provisioning failures, token refresh, deprovisioning, mapping mismatches)?
- Who manages keys and tokenization certificates today and where are they hosted (HSM vendor, cloud KMS, in-house)?
- If you have tokenization gaps, which channels are most affected—mobile wallets, e-commerce, in-app, or physical POS?
Who really accepts your cards—and who doesn't?
- Where do you feel your acceptance footprint falls short in ways that limit growth or customer experience?
- Which merchant categories or regions refuse or deprioritize your cards, and why do you think that happens?
- Are there specific large merchants or acquirers you cannot reach today without extra work or higher fees?
- How consistent is POS and contactless support across your top merchants—are there terminals or gateways that fail to accept your tokens/cards?
- Share an example where acceptance limitations directly affected a merchant relationship or a marketing initiative.
When things break, who survives the night?
- How often do you experience operational outages or degraded performance that impact authorizations or settlements?
- Describe the most common failure modes—network latency, message loss, reconciliation drift, downstream processor downtime, or others.
- What are your current fallback behaviors (route to alternate switch, soft-decline, offline approvals) and how often are they invoked?
- How quickly can your teams detect an incident and who is alerted automatically (ops, product, sales, executives)?
- Walk us through a recent post-mortem—what caused it, what fixed it, and what remains unresolved?
Money matters — how transparent and predictable are your fees?
- How would you describe the predictability of interchange, assessment, and acquirer fees across your top corridors?
- Which fee drivers cause the most disagreement or reconciliation work—multi-currency FX, interchange category, surcharge/assessment, or acquirer margins?
- Do you have automated fee attribution and rebating workflows, or is fee recovery largely manual?
- How often do fee surprises (unexpected charges or withholding) occur and how do they affect cashflow forecasting?
- Give an example of a fee-related dispute and how long it took to recover funds or correct billing.
If you could change one thing right now — what would move the needle?
- If a single improvement could eliminate your biggest pain in authorization, clearing, settlement, or tokenization, what would it be?
- Which three KPI improvements would convince your executives this work was worth prioritizing (e.g., % decline reduction, settlement accuracy, time-to-resolution)?
- What timeline feels realistic for a pilot that proves value—weeks, months, or longer—and what constraints would limit speed?
- Who needs to sign off to start a pilot or integration (titles/roles), and what information do those stakeholders want to see first?
- What would make you hesitant to engage in a pilot or change program—regulatory risk, resource bandwidth, commercial terms, or something else?
-
-
Outcome Discovery
Define target business outcomes (interchange economics, acceptance coverage, uptime, fraud tolerance), measurable success signals, and must-have constraints.
Discovery Questions
Starting With What Matters Most
- Which single business outcome would you prioritize above all others for this engagement?
- Who inside your organization will feel the impact of that outcome most acutely, and what would success sound like to them?
- Which three metrics does your executive team already track that speak to progress on that priority?
- How urgent is achieving that outcome on a scale from tactical (next 12 months) to strategic (multi-year)?
- If you had to name the one thing currently preventing that outcome, what would it be?
What If 'Good Enough' Is Keeping You Here?
- What compromises have you accepted in your payments program that, in hindsight, might be costing you more than you realize?
- How long have those compromises been in place and what prompted them originally?
- When these compromises surface externally (e.g., merchant complaints or issuer friction), how do they typically show up?
- What would change in the business if you didn't have to accept those compromises anymore?
- Which internal belief or constraint most often justifies keeping the status quo?
Numbers That Make Your CFO Smile
- If you could reset interchange economics today, what top-line and margin targets would you set for the next 12 months?
- Which pricing levers are truly available to you—assessment fees, rating groups, merchant pass-through, or promotional routing?
- What minimum per-transaction economics (net to issuer/acquirer) do you consider a deal-breaker?
- Do you have recent benchmark targets or external comps we should use when modeling economics?
- How sensitive would your stakeholders be to a short-term revenue dip if it enabled higher lifetime value (e.g., acceptance expansion)?
Where Will Customers Notice The Difference?
- If you could double acceptance in one merchant category or geography overnight, which would you choose and why?
- Which channels matter most for your cardholders and merchants—card-present, e‑commerce, in-app, or tokenized wallets?
- What percentage of your volume today happens in priority geographies or merchant segments?
- Which merchant types are hardest to win—high-risk verticals, cross-border marketplaces, or small merchants—and why?
- How do your top merchants measure payment experience—authorization speed, decline rates, reconciliation simplicity, or reporting access?
How Much Risk Can You Live With?
- What level of fraud loss or chargeback rate would trigger executive escalation or a program review?
- Which fraud controls do you consider non-negotiable today—real-time scoring, velocity checks, tokenization, or manual reviews?
- How often do false positives (legitimate transactions blocked) create customer or merchant complaints, and how do you currently measure that impact?
- If liability shifted in a scenario (e.g., merchant or network), what operational or financial implications would you need to prepare for?
- Are there existing fraud partners, watchlists, or consortium feeds you must keep integrated?
Uptime, Performance, and When Seconds Matter
- Imagine peak shopping hours: how much downtime or latency can you tolerate before merchants and issuers notice significant harm?
- What are your target SLAs for authorization availability and average latency (ms)?
- Describe your worst recorded outage or performance incident—how long, impact, and what root cause was identified?
- What peak transactions-per-second (TPS) or batch clearing volumes should any solution comfortably handle?
- Which monitoring and alerting channels do your ops teams require (e.g., Slack, SMS, PagerDuty, email, dashboards)?
What Can’t Move — Regulatory and Contractual Must-Haves
- Which regulatory or contractual constraints would force us to change approach immediately if not satisfied?
- Are there certifications or audits (e.g., PCI, ISO, local regulator) that must be in place before go-live?
- Which settlement currency or settlement window constraints are non-negotiable for your treasury operations?
- Have you previously encountered regulator pushback or contract disputes tied to interchange, surcharging, or routing that we should know about?
- If a proposed change required a brief regulatory filing or notice, what internal review timeline would we need to respect?
How We'll Know We Succeeded (Signal-Led Acceptance)
- Which success signals will convince your leadership this project is delivering—revenue, acceptance, uptime, fraud reduction, or customer satisfaction?
- What baseline values should we measure from today so we can objectively show improvement?
- How frequently does leadership expect reporting during pilot and after production (daily/weekly/monthly)?
- What governance cadence and stakeholders do you want on the success dashboard (names or roles)?
- Are there any KPIs that if missed for X period would be considered a failure rather than a performance issue? Please specify KPI and threshold.
Practical Integration Boundaries — What We Can and Can’t Touch
- Which systems must remain unchanged during integration (core banking, POS gateways, settlement engines, token service providers)?
- What endpoints, APIs, or data schemas are available today for integration—can you share docs or versions?
- Who will own integration delivery on your side and what other teams must be involved (e.g., network ops, security, treasury)?
- What timeline constraints do we have for sandbox, UAT, and production cutover?
- Which acceptance criteria must be met before we route live volume (e.g., pass rate, settlement reconciliation accuracy)?
Hidden Costs and Operational Reality Checks
- What internal operational work (staffing, process changes, training) will we need to budget for that often gets overlooked?
- If we required a temporary routing change or dual-run during cutover, what operational pain would that create for your teams?
- Which downstream reconciliation or reporting processes are brittle today and likely to need fixes during integration?
- How do you prefer to handle exceptions during rollout—automated retries, manual review queue, or temporary throttling?
- What budget or resource contingency do you typically reserve for unexpected operational work in projects like this (% of project budget)?
Making the Decision Real — Tradeoffs We Should Be Ready For
- Which tradeoff would you be most willing to make: faster go-live with limited features, or fuller feature set with longer timeline?
- If we proposed a phased rollout, what must be included in phase 1 versus what can wait?
- What internal approvals are likely to be the slowest, and how can we design the plan to address them early?
- What would acceptance by your merchants look like in phase 1—measured behaviorally or via explicit sign-off?
- What timeline is realistic for your organization to make a go/no-go decision after we present a recommended approach?
Next Steps That Don't Leave You Guessing
- Given everything above, what would a successful pilot look like in 90 days—what outcomes, data, and stakeholder buy-in would you need?
- Who needs to be in the executive review after the pilot, and what decision authority do they hold?
- What information or artifacts do you need from us to get your procurement, legal, and compliance teams moving?
- What would make you say 'no' at the end of a pilot—list non-negotiable failure conditions if any?
- Finally, what’s the best way for us to keep momentum—regular check-ins, embedded technical office hours, or an on-site workshop?
-
Solution Experience
Walk through outcome delivery using the customer’s real transaction scenarios to validate how the network addresses economics, reliability, and tokenization needs.
Experience Meetings
- Solution Experience Kickoff & Preconditions Alignment
- Economics & Routing Scenario Walkthrough
- Reliability & Peak-load Resilience Simulation
- Tokenization & Digital Payments Experience
- Consolidated Validation, Exceptions & Acceptance Signoff
- Seller to deliver token mapping spec and sample reconciliation reports tied to the customer's dataset.
- Obtain explicit customer validation that the economics presented map to their expectation of consequence and future-state benefit.
- Seller to deliver a detailed economics report showing per-scenario P&L impact and routing recommendations.
- Customer to confirm tolerance for proposed routing change and identify a pilot merchant cohort.
- Technical mapping: update any data field mismatches discovered during dataset validation.
- Restate SLAs & Failure Modes
- Prove the network meets the agreed SLA thresholds under the customer's real peak scenarios.
- Expose and document any operational failure modes and required mitigations.
- Agree monitoring, alerting, and runbook updates necessary to operationalize the future state.
- Seller to provide replay logs, latency histograms, and failover test artifacts for customer review.
- Ops teams to draft or update runbooks and monitoring thresholds based on test outcomes.
- Schedule a follow-up ops runbook walkthrough for any unproven or failed scenarios.
- Confirm Token Use-cases & Gaps
- Prove token provisioning, authorization, and settlement flows for the customer's real digital scenarios.
- Ensure reconciliation integrity and traceability between tokens and PANs.
- Confirm that tokenization delivers stated business outcomes (fraud reduction, UX improvement, reduced PCI burden).
- Introductions & Objectives
- Customer to confirm which merchants/wallets will be included in a token pilot.
- Security/compliance to review token storage/VAULT architecture and provide sign-off or remediation items.
- Executive Summary: Current vs Future vs Consequence
- Obtain explicit customer validation that the solution experience proves the defined future state or capture conditional exceptions.
- Document and assign remediation actions for any failed success signals with owners and deadlines.
- Secure agreement to progress to Solution Scope with a clear list of scope-in items and integration touchpoints.
- Customer to sign an experience validation memo or provide formal conditional acceptance.
- Seller to produce a consolidated findings deck, remediation backlog, and proposed Solution Scope agenda.
- Assign owners and dates for each remediation and schedule the Solution Scope workshop.
- Produce a clean, one-sentence current state that all parties acknowledge.
- Quantify the direct business consequences of the current state to create urgency.
- Agree a one-sentence future state outcome and measurable success signals.
- Confirm dataset, simulation plan, and owners for pre-work so subsequent meetings can run real scenarios.
- Customer to deliver anonymized transaction dataset and baseline SLA/incident reports.
- Customer to provide executive-approved one-sentence current state and target future-state sentence.
- Seller to prepare scenario scripts and simulation environment based on the provided dataset.
- Schedule the scenario walkthrough meetings and assign technical contacts.
- Recap Preconditions & Success Signals
- Demonstrate net interchange and fee impact on the customer's real transaction mix.
- Identify top sources of economic leakage and routing opportunities with clear ownership.
- Load & Validate Dataset Assumptions
- Define Test Matrix (peak, degradation, outage)
- One-sentence Current State
- Provisioning Walkthrough with Real Flow
- Scenario Findings Digest
- Tokenized Authorization & Acceptance
- Consequence Quantification
- Run Peak Traffic Replay & Live Observability
- Live Economics Simulation
- Open Exceptions & Root Cause Action Plan
- Simulate Failover & Recovery
- Routing & Acceptance Impact
- Settlement & Reconciliation Mapping
- Acceptance Criteria Confirmation & Signoff
- Define Future State (one sentence)
- Operational Tieback
- Tieback to Outcomes (fraud tolerance, UX, acceptance)
- Next Steps into Solution Scope
- Success Signals & Acceptance Criteria
- Tieback to Consequence
- Data & Simulation Plan
- Final Validation & Q&A
- Validation Checkpoint
-
Solution Scope
Define included modules (switching, tokenization, fraud, analytics, settlement), integration touchpoints, responsibilities, SLAs, and acceptance criteria.
Scope Configuration
- Process Real-Time Transaction Authorizations
- Execute Clearing and Settlement Batches
- Perform Cross-Border FX Conversion and Settlement
- Activate Network Tokenization for Digital Wallets
- Provision Token Vault and Credential Management
- Operate Fraud Detection and Risk Scoring Engine
- Manage Chargeback and Dispute Resolution Processing
- Process Loyalty and Rewards Redemption Transactions
- Provide Issuer Portfolio Analytics Reports
- Enable Contactless and Mobile Payment Acceptance
- Route Transactions via Merchant Acceptance Network
- Deliver Settlement and Regulatory Reporting Files
- Offer BIN Sponsorship and Issuer Connectivity
- Provide Tokenized E‑commerce Checkout Integration
Scope Questions
Process Real-Time Transaction Authorizations
- Which channels require real-time authorization (e.g., POS, e-commerce, mobile wallets)?
- What peak transactions per second (TPS) and average TPS should the authorization path support?
- Which messaging/protocols must be supported for authorization (select primary)?
- What latency SLA do you require for authorization responses (average / p95)?
- Who is responsible for endpoint availability and monitoring (customer vs network)?
- Are there special risk/decision rules that must run in-line during authorization? Describe if yes.
Execute Clearing and Settlement Batches
- What settlement cycle(s) do you require (e.g., T+0, T+1, daily batch)?
- Which settlement file formats and protocols are required?
- Do you require net or gross settlement processing?
- What reconciliation cadence and tooling do you need (end-of-day, hourly, automated matching)?
- Are there specific counterparties or clearing houses you must interface with? List them.
- Do you require guaranteed funds or pre-funding controls for settlement?
Perform Cross-Border FX Conversion and Settlement
- Which currencies and FX corridors are in scope for cross-border settlement?
- Do you require real-time FX rates, locked rates, or end-of-day conversion?
- Which settlement currencies should the system deliver to your bank accounts?
- What regulatory or tax reporting considerations affect cross-border flows (e.g., withholding, GST/VAT)?
- Are there preferred FX providers or correspondent banks you must use?
- Do you require hedging, netting, or multi-leg settlement optimization?
Activate Network Tokenization for Digital Wallets
- Which tokenization formats and schemes must be supported (network token spec, EMVCo, platform tokens)?
- Which digital wallets and token requestors must be enabled (e.g., Apple Pay, Google Pay, Samsung Pay)?
- Do you need token provisioning for card-on-file, digital wallet, or both?
- What parties will manage token lifecycle events (provisioning, re-enrollment, suspension)?
- Are there specific triggers for token reissuance (expiry, suspected compromise)? Describe.
- What testing and certification is required before token activation (wallet certification, issuer QA)?
Provision Token Vault and Credential Management
- Do you require a hosted token vault, on-premises HSM integration, or hybrid model?
- What encryption standards and key management protocols are mandated (e.g., PCI, AES, KMIP)?
- Who will be the custodian of cryptographic keys and rotation responsibilities?
- What SLA for vault availability and key retrieval is required?
- Are there regulatory or data residency constraints for storing tokens/credentials?
- Please list expected token volumes and retention/archival requirements.
Operate Fraud Detection and Risk Scoring Engine
- Which fraud channels should be analyzed in real-time (authorization, chargeback, onboarding)?
- Do you want out-of-the-box rule sets, custom rules, machine-learning models, or a combination?
- What risk score thresholds and actions do you expect (block, review, allow with warning)?
- What telemetry and data feeds are available for model training (transaction history, device fingerprinting)?
- Do you require explainability/audit logs for each decision for regulatory review?
- What SLA for fraud engine latency is acceptable for inline authorization decisions?
Manage Chargeback and Dispute Resolution Processing
- Which dispute workflows do you follow (scheme chargeback timelines, bilateral processes)?
- What evidence/document types are required to support representments (receipts, logs, auth records)?
- What dispute SLAs and targets do you require for resolution time and response?
- Who handles customer communications and representment submissions (customer, acquirer, network)?
- Do you need analytics on dispute drivers and chargeback ratios?
- Are there merchant-level dispute policies or thresholds that should trigger remediation?
Process Loyalty and Rewards Redemption Transactions
- Which loyalty program types are supported (co-branded issuer, merchant-funded, network rewards)?
- Do redemptions occur at POS, online checkout, or via issuer portals?
- How should rewards valuation and accrual rules be applied (fixed points, % spend, tiers)?
- Do you require real-time balance checks and authorization holds for redemptions?
- Who maintains the loyalty catalog and updates (merchant, issuer, network)?
- Are there regulatory or promotional tax considerations for rewards redemptions?
Provide Issuer Portfolio Analytics Reports
- What high-level KPIs do you require (interchange revenue, transaction volume, fraud rate, authorization rate)?
- What reporting frequency and delivery channels do you need (daily, weekly, monthly; portal, SFTP, API)?
- Do you require pre-built dashboards or custom report development?
- Are there segmentation needs for reporting (BIN-level, product-level, merchant category)?
- What formats are preferred for consumption (CSV, Excel, PDF, API)?
- Do you require secure role-based access to analytics and drill-down capabilities?
Enable Contactless and Mobile Payment Acceptance
- Which contactless technologies must be supported (NFC, MST, QR code)?
- Do your merchants require terminal certification (EMV Level 2, contactless kernel)?
- Are there offline transaction requirements for contactless (limited floor limits)?
- Which acceptance devices and POS vendors are in scope?
- Do you require activation support for mobile in-app SDKs or POS firmware updates?
- What fraud controls are required specifically for contactless interactions?
-
Mutual Commit
Negotiate and document commercial terms, regulatory obligations, SLAs, go-to-market responsibilities, and executive sign-offs.
Agreement Modules
- Term Sheet
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Pricing & Commercial Terms Annex
- Service Level Agreement (SLA)
- Data Processing Agreement (DPA)
- Regulatory & Compliance Addendum
- Settlement & Funding Schedule
- Integration & Technical Acceptance Criteria
- Certification & Onboarding Checklist
- Go-to-Market & Co-Marketing Agreement
- Executive Sign-off & Governance Charter
- Escrow & Key Management Agreement
- Fraud, Liability & Chargeback Allocation
- Change Control & Change Order Process
- Termination, Exit & Transition Plan
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm connectivity, keys/certifications, test data, fallback plans, monitoring, and assigned operational owners are ready for execution.
Readiness Questions
Getting Comfortable — Quick introductions to set the stage
- Who are you and how do you prefer we refer to your team during this engagement?
- What is your title and primary area of accountability for payments?
- What’s the timeline you’re targeting for a production connection or go-live?
- Who are the must‑have decision-makers we should keep informed (roles, not just names)?
- What keeps you up at night about adding or changing a payment network relationship?
Are you settling for fragile uptime?
- How would you describe the worst availability or outage scenario you’ve experienced with a payments partner?
- How often do you experience meaningful service degradation during peak hours?
- How do outages typically show up for your business—lost authorization, delayed settlement, increased disputes, or other effects?
- When uptime issues occur, who is expected to respond inside your organization and how quickly?
- How long has your team been managing the current reliability profile (i.e., is this a new pain or a long-standing one)?
Where do you lose money you don’t expect?
- Which parts of the current economics worry you most—interchange leakage, assessments, cross-border fees, or reconciliation gaps?
- Can you share an example of a recent reconciliation or settlement surprise and its financial impact?
- How do you currently measure the net economics of a card program or acquiring relationship?
- What would a meaningful improvement in economics look like quantitatively for your organization?
- Who in your organization is responsible for approving pricing or fee changes tied to a network relationship?
Who really owns tokenization and the digital experience?
- Where do you currently store and manage tokens—your gateway, network token service, processor, or in-house?
- How often do tokenization failures (missing tokens, failed binds) cause payment declines or customer friction?
- Who is accountable for the token lifecycle (provisioning, rotation, deactivation) in your org?
- What integrations (wallet providers, mobile issuers, gateways) must work seamlessly for your digital strategy to succeed?
- If tokens could unlock one capability overnight, what would you pick—mobile wallet acceptance, card-on-file migration, e‑commerce optimization, or something else?
How risky does fraud feel today?
- Is your current fraud posture making you lose revenue through false positives or exposing you to losses from false negatives?
- How do you currently detect and respond to fraud—rules engines, ML scoring, third-party services, or manual review?
- Describe a recent fraud event that changed a policy or threshold—what happened and what did you change?
- How tolerant are your stakeholders to short‑term increases in false positives if that reduces long‑term losses?
- What friction from fraud controls has the biggest impact on customer experience or merchant conversions?
If execs said this project failed in 12 months, what would they point to?
- Which stakeholder (cards, payments, treasury, ops, legal, exec) would be the harshest judge of success and why?
- What are the top 3 measurable success signals each of those stakeholders would expect?
- What SLA targets would satisfy your operational and commercial teams (authorization latency, availability, settlement timing)?
- How frequently do stakeholders expect reporting and what level of transactional detail is required?
- If we agreed on a small set of metrics to monitor post-launch, which three should we prioritize?
If we could cutover tomorrow, what could break?
- Which connectivity methods do you require for production (API over TLS, ISO 8583 over VPN, host-to-host, cloud peering)?
- Do you have the required certificates/keys and HSM access available now or will those be provisioned by a vendor?
- How complete is your test data that reflects real transaction mixes, edge cases, and peak-volume scenarios?
- Do you have defined fallback and offline processing plans if network calls fail? If yes, briefly describe ownership.
- Who will be the named operational owners on both sides for cutover and 0–72 hour incident response?
Who do we need in the room to make this stick?
- Which teams must be actively involved through integration and the first 90 days (select all that apply)?
- What internal change management challenges have blocked previous payment integrations?
- How would you like communication and decision cadence to work during onboarding (steering committee, weekly touchpoints, ad‑hoc war room)?
- Who signs acceptance at the end of validation—name roles and the minimum criteria they’ll require?
- What internal approvals or regulatory notifications must be completed before production traffic is permitted?
What will make you confident to launch?
- What end-to-end tests are absolute musts before we move to production (authorization success rate, settlement reconciliation, token binding, fraud detection efficacy)?
- What pass/fail thresholds should we use for acceptance (e.g., authorization acceptance % , reconciliation variance, latency)?
- Who needs to sign off on each validation area (technical, security, commercial, legal)?
- How much production-like volume do you want to run in pilot before full cutover?
- If a critical validation fails, what rollback / remediation approach do you prefer?
After launch — who’s actually paying attention?
- What ongoing monitoring and alerting do you require post-launch (real-time alerts, daily reconciliations, SLA breach notifications)?
- What escalation paths do you want for Sev-1 / Sev-2 incidents?
- How should we manage continuous improvement—shared backlog, quarterly roadmap reviews, joint ops meetings?
- Which KPIs should trigger a business review rather than a technical ticket (e.g., economics drift, acceptance degradation)?
- How would you prefer to handle feature requests that affect commercial terms or revenue sharing?
-
Deployment Enablement
Plan and execute cutover tasks, runbooks, cross-team sequencing, rollback triggers, and monitoring activation with clear owners.
-
Validation Checklist
Verify end-to-end authorization, clearing, settlement, token flow, fraud rules, performance baselines, and SLA adherence against acceptance criteria.
Validation Questions
Getting Comfortable — quick context
- To start, who are you and how do you interact with payments day-to-day?
- Which of these best describes why you are exploring a new network partnership right now?
- What timeframe are you working toward for a decision or pilot?
- Tell us about the last payments or network project you ran — what succeeded and what surprised you?
- How would you describe the current emotional tone around this initiative internally (e.g., frustrated, hopeful, skeptical)?
Who’s Really Pulling the Levers?
- If every stakeholder could be brutally honest: whose approval tends to slow things down and why?
- Which functions must sign off on a network change for it to proceed?
- Who, in your organization, would be the single point of accountability for commercial and operational sign-off?
- When the executive team evaluates network partners, what three outcomes move them from interest to commitment?
- How do your legal/regulatory teams typically influence commercial terms—do they set immovable constraints or negotiate tradeoffs?
- If we needed an executive-level sponsor to push a pilot, who would be most persuasive internally and why?
What’s Been Getting in the Way? (Operational realities we need to fix)
- Which operational or network problems have you quietly accepted as 'normal'?
- Describe a recent incident where a payments failure directly impacted revenue, customer experience, or regulatory standing—what happened and who felt the pressure?
- How frequently do these incidents occur and how predictable are they?
- When issues happen, what is the typical downstream cost (hours to resolve, manual headcount, lost transactions)?
- Who on your team becomes the 'firefighter' during incidents, and how does that strain other priorities?
If We Could Rebuild Your Payments Flow
- What would change if your authorization and settlement chain behaved perfectly for 90 days—what business signals would you see that prove it worked?
- Which business outcomes matter most for this initiative?
- What measurable thresholds would make you call a pilot a success (e.g., decline rates, settlement lag, fraud reduction)? Please be specific.
- What constraints are absolute deal-breakers (regulatory, contractual, technical), and which are negotiable tradeoffs?
- If you had to prioritize three improvements in order, what would they be and why?
Where Tokens, Cards and Rules Collide
- How would you describe your token strategy today—are tokens a source of competitive advantage or an operational headache?
- Which token use-cases are in scope for this engagement?
- Who manages token orchestration and lifecycle for you (internal team, third-party token service provider, issuer network)?
- Where do token-related failures show up today (falls back to PAN, token mismatch, mapping delays, wallet declines)?
- Do you have certification, key management, or PCI/TSP requirements that must be met before go‑live?
Reliability Is a Promise — How Broken Is It Today?
- If a customer-facing outage happened tomorrow, how confident are you that recovery and communication would go smoothly?
- What are your existing uptime and latency baselines during peak and non-peak hours?
- How do you test resilience today (chaos testing, scheduled failovers, load tests), and how often?
- What are acceptable RTO and RPO targets for your payments stack?
- Who owns 24/7 incident response and who needs to be notified for major outages?
Money Moves: Clearing, Settlement, and Reconciliation
- Where in your clearing/settlement lifecycle do exceptions and manual interventions spike?
- What settlement cadence and currency coverage do you require?
- How many FTEs or hours per week does reconciliation and exception handling consume today?
- Describe the tools and exports your team relies on for reconciliation—what works and what doesn't?
- What regulatory or local settlement rules (e.g., central bank windows, reserve requirements, tax withholding) must a partner support?
What Would Make You Confident to Say Yes?
- Which tests and proof points would you require to validate the deployment (pick all that apply)?
- For each of the selected tests, what numeric or observable threshold defines success for you (e.g., decline rate < X, settlement lag < Y)?
- How long should a pilot/validation window run before you decide to scale or walk away?
- Who must sign the final operational acceptance and commercial go/no-go (roles, not names)?
- What are the top three residual risks that would make you pause even if tests pass, and what mitigation would you need to proceed?
-
-
Success
Review outcomes against success signals, operationalize continuous monitoring and optimization, and maintain a shared backlog for issues and enhancements.
Success Reviews
- Success Review & KPI Validation
- Operational Monitoring & SLA Handoff
- Continuous Improvement & Shared Backlog Prioritization
- Incident Retrospective & Risk Mitigation
- Executive Business Review — Quarterly Success Review
Issues & Enhancements
- Implement code/config fixes and provide a patch deployment schedule.
- Obtain operational sign-off on runbooks and handoff readiness.
- Provision and share a read-only dashboard view to customer and ops teams.
- Finalize and publish runbooks and escalation contacts into the shared operations repository.
- Implement any agreed threshold changes and confirm via test alerts.
- Backlog Introduction & Categories
- Establish a single shared backlog with agreed categories and ownership.
- Agree on prioritization methodology and SLAs for remediation and enhancements.
- Commit high-priority items to the near-term release schedule and assign owners.
- Create the shared backlog board and import prioritized items with impact/effort scores.
- Assign owners and target delivery windows to the top 5 prioritized items.
- Publish backlog governance rules and triage cadence to stakeholders.
- Incident Timeline & Facts
- Identify root cause and list corrective actions with clear owners and dates.
- Establish preventive measures and monitoring changes to reduce recurrence risk.
- Agree on verification tests and closure criteria for incident sign-off.
- Introductions & Meeting Objectives
- Update runbooks and monitoring alerts based on RCA outcomes.
- Run post-change verification tests and report results within agreed window.
- Executive Summary of Outcomes vs Targets
- Secure executive alignment on whether outcomes meet strategic expectations.
- Obtain funding or authorization for prioritized strategic improvements.
- Commit to next-quarter metrics and executive sponsor for ongoing oversight.
- Produce a one-page executive summary with decision capture and distribute within 48 hours.
- If approved, allocate budget and resources to prioritized strategic items and update roadmap.
- Schedule the next executive review and circulate required preread materials.
- Confirm which success signals are met and which are not with supporting evidence.
- Quantify business consequences for unmet signals to create urgency for remediation.
- Agree on acceptance, remediation plan, owners, and follow-up validation date.
- Deliver full KPI pack with raw data, dashboards, and sample transactions to all attendees.
- If remediation required, produce a remediation plan with scope, owners, timeline, and acceptance criteria within 3 business days.
- Schedule follow-up validation meeting and circulate required prework for validation.
- Purpose, Scope, and Roles
- Ensure full monitoring coverage for all critical flows and clear ownership of alerts.
- Agree on SLA measurement method, reporting cadence, and escalation procedures.
- Crystal-clear Current State Statement
- Impact vs Effort Scoring Exercise
- Monitoring Architecture & Dashboards Walkthrough
- Financial Impact & ROI Review
- Impact Assessment & Stakeholder Consequences
- Consequence Quantification
- Alerting Rules and Escalation Paths
- Root Cause Analysis
- Operational Health & Risk Posture
- Define Prioritization & Governance Rules
- Corrective Actions & Preventive Measures
- KPI Trend Review vs Success Signals
- Strategic Opportunities & Required Investments
- Roadmap Alignment & Release Windows
- SLA Measurement & Reporting Cadence
- Operationalization: Ticketing, SLAs, and Communication
- Decisions & Approvals
- Operational Playbooks & Runbook Walkthrough
- Proof Points & Evidence
- Verification Plan & Closure Criteria
- Define Future State & Acceptance Criteria
- Ownership Sign-off and Handoff Checklist
- Next Quarter Objectives & Metrics
- Agreement: Accept, Remediate, or Extend
- Next Steps & Follow-up Review Scheduling