# AI workability — RFP: 27.27-Merchant Solution Partner

*Buyer: ATB Financial · Source: merx · Closes: 14 Sep 2026 00:00 UTC*

**AI workability: 36%** (majority needs humans) · notice-only read · bid call: **NO_GO**

- Effort: 4,300 h total · 1,530 h AI · 2,770 h human (low confidence)

## Verdict

No-go: mandatory merchant solution requirements cannot be met by a small AI-first shop.

## Bid call

**NO_GO** — The RFP requires an established merchant solution partner with 24/7 live phone support, real-time settlement, and institutional operational excellence. A small independent IT shop cannot meet these mandatory requirements, and AI cannot substitute for regulated financial infrastructure, certifications, and human accountability. Source documents are thin, but the stated requirements are clear enough to recommend no-go.

## Deliverables

| Deliverable | Mode | AI share | Hours |
| --- | --- | --- | --- |
| RFP response and proposal package | ai_assisted | 80% | 200 |
| Solution architecture and integration design | ai_assisted | 60% | 300 |
| Automated merchant onboarding platform | ai_assisted | 70% | 800 |
| Real-time settlement integration | human_only | 15% | 600 |
| 24/7/365 live phone support | human_only | 10% | 1000 |
| Ongoing technical support and maintenance | ai_assisted | 50% | 500 |
| Security and compliance certification | human_only | 10% | 300 |
| Partnership and commercial model agreements | human_only | 5% | 200 |
| Project management and governance | human_only | 20% | 300 |
| Technical documentation and training material | ai_agent | 90% | 100 |

## Risks

- **[high]** Mandatory 24/7/365 live phone support cannot be met by a small shop without a large support organization. — *Partner with a call center or do not bid.*
- **[high]** Real-time settlement requires Payment Canada RTR certification and banking relationships. — *Confirm whether subcontracting or white-label partnership is allowed; otherwise no-go.*
- **[high]** No existing bank-agnostic processing platform or merchant acquiring experience. — *Leverage a payments platform partner, but this weakens the bid.*
- **[medium]** Source documents are thin; requirements may be misinterpreted. — *Request clarification from ATB Financial before bidding.*
- **[medium]** AI-generated code in financial services may face compliance scrutiny. — *Use AI for prototypes and documentation, with human architects and compliance review.*
- **[high]** Small shop lacks reference contracts and institutional credibility. — *Partner with an established payments provider or no-go.*

## Human roles

- **Legal and commercial negotiator** (15%): Contract signature, partnership model, liability.
- **Compliance and security officer** (20%): Financial regulations, audits, certifications.
- **24/7 support staff** (35%): Live phone support SLAs require humans.
- **Settlement operations and finance** (15%): Real-time settlement and financial reconciliation.
- **Project manager / client relationship** (10%): Stakeholder workshops and accountability.
- **Solution architect / reviewer** (5%): Validate AI-generated designs and code.

## Why not more AI

- Cannot sign contracts or take legal/financial accountability.
- Cannot provide live phone support with committed SLAs.
- Cannot obtain Payment Canada RTR certification or banking licenses.
- Cannot perform on-site relationship work or client workshops.
- Cannot approve merchant accounts or make credit decisions.
- Cannot provide institutional operational excellence references.

## Requirements & compliance

| Ref | Requirement | Status |
| --- | --- | --- |
| RFP | Proponents must demonstrate institutional operational excellence, backed by 24/7/365 technical live phone support SLAs, swift incident resolution protocols, and a future-forward product roadmap prepared to natively support upcoming industry innovations such as the Payments Canada Real-Time Rail (RTR) infrastructure and embedded finance integrations. | gap |
| RFP | Ideal proponents provide a highly agile, bank-agnostic processing platform that supports flexible partnership models—including referral, wholesale, or hybrid structures. | gap |
| RFP | Proponents should self-select based on their technical capability to deliver frictionless merchant onboarding via an automated digital self-enrollment engine capable of approving standard business accounts, accelerating time-to-revenue efficiency, and facilitating real-time or same-day financial settlement. | gap |

## Evaluation criteria

- **Not published** (N/A): No evaluation criteria in source documents; likely includes technical capability, experience, support model, and partnership flexibility.

## Key dates

- 2026-08-20 — Publication
- 2026-09-14 — Closing Date

## Gaps in source documents

- No evaluation criteria or weighting published.
- No contract value, duration, or pricing model.
- No detailed scope of work beyond high-level solution areas.
- No information on existing systems or incumbent.
- No clarification on whether partnerships or subcontracting are allowed.
- No security clearance or onsite presence requirements specified.

## Assumptions

- The proponent is expected to be the merchant solution partner, not just a software vendor.
- The project includes both bid preparation and ongoing service delivery.
- No existing banking/payment partnerships or certifications are available.
- AI agents can produce software and documents but cannot perform regulated financial activities.
- Effort estimates are rough due to thin source documents.

---

*Generated by GovContract from public tender documents. Human review required before acting on bid decisions.*