# IT Consortium — Phase 0 Kickoff Brief

**Status:** Ready for founder to send
**Purpose:** Initiate ITC contracting and technical onboarding in Phase 0 week 1, so that production credentials are live before Phase 2 (week 18) begins.
**Lead time:** 3–6 weeks from first contact to production credentials. Any slippage here pushes Phase 2 directly.
**Audience:** ITC sales / partnerships team; ProcureGlobal founder.
**Last updated:** 16 May 2026

---

## 1. Outreach email (ready to send)

**Subject:** ProcureGlobal — TransFlow + UniWallet integration enquiry

**To:** ITC sales / partnerships (confirm exact address via [itconsortiumgh.com](https://itconsortiumgh.com) contact form or LinkedIn to their Head of Partnerships)

> Dear IT Consortium team,
>
> I'm Ekow Thompson, founder of **ProcureGlobal**, a B2B + B2C e-commerce platform launching in Ghana later this year. We'd like to begin onboarding to **TransFlow Checkout** and **UniWallet** as our secondary payment processor, with Paystack as primary.
>
> **Quick context**
> - GHS settlement to our **Stanbic Bank Ghana** account; USD presentment for diaspora buyers via Paystack FX.
> - MVP production launch target: ~6 months out.
> - First-year GMV projection: GHS 2–4M across B2C (~70% MoMo, ~20% card, ~10% bank) and B2B (high-value bank and MoMo).
> - Expected ITC share of total routing volume: ~25–30%, weighted toward high-value B2B settlements where TransFlow is the natural rail.
>
> **What we're looking for**
> 1. A kickoff call with your sales / partnerships team this or next week.
> 2. Your KYC and onboarding document checklist.
> 3. Indicative pricing on cards, MoMo, and bank transfer at the volumes above.
> 4. Sandbox credentials so our engineering can begin integration in parallel with contracting.
> 5. Written confirmation that settlement to our Stanbic account runs on TransFlow with same-day timing (no clearing hop).
> 6. TransFlow Checkout and UniWallet API documentation, plus webhook signature and idempotency specifications.
>
> Happy to share architecture detail or compliance posture (PCI SAQ-A; Ghana DPA registration in progress) on a call. Looking forward to working with you.
>
> Best regards,
> Ekow Thompson
> Founder, ProcureGlobal
> ekowthompson@gmail.com

---

## 2. What we need from ITC — tracker

| # | Ask | Owner | Status |
|---|---|---|---|
| 1 | Initial sales / partnerships call | ITC | Pending |
| 2 | KYC + onboarding document checklist | ITC | Pending |
| 3 | Indicative pricing (cards, MoMo, bank) | ITC | Pending |
| 4 | Sandbox credentials | ITC | Pending |
| 5 | Settlement timing confirmation (Stanbic, same-day) — written | ITC | Verbally confirmed; need it in writing |
| 6 | TransFlow Checkout API documentation | ITC | Pending |
| 7 | UniWallet API documentation | ITC | Pending |
| 8 | Webhook specification + idempotency guarantees | ITC | Pending |
| 9 | Production credentials timeline | ITC | Pending |
| 10 | SLAs (uptime, dispute resolution, refund SLA) | ITC | Pending |
| 11 | Master Services Agreement / merchant contract | ITC | Pending |

---

## 3. What ITC will ask from us — KYC pre-flight

Start gathering now so we don't bottleneck on our side. Typical Ghana PSP requirements:

1. **Business registration** — certificate of incorporation, certificate to commence business (RGD documents).
2. **Tax** — TIN, GRA tax clearance certificate, VAT registration if applicable.
3. **Directors / shareholders** — IDs (passport + Ghana Card), proof of address, completed KYC forms.
4. **Beneficial ownership disclosure** — anyone with >10% ownership.
5. **Bank account** — Stanbic Bank Ghana account confirmation letter (account name, account number, branch, SWIFT/BIC).
6. **Source of funds** — 6–12 months of bank statements for the business and/or founder.
7. **Business profile** — description of products, customer segments, expected volumes (already covered in the outreach email).
8. **Website / app** — live URL or detailed mock-ups. `brand-system-v1.html` is available now; a public landing page will help.
9. **Compliance posture** — DPA registration acknowledgement letter (in progress per PRD §1.1 decision 12), AML/CFT policy if available.
10. **Technical contact** — name, email, role. Currently Ekow until the first engineer is hired.

---

## 4. Phase 0 critical-path schedule

| Week | Milestone | Owner | Notes |
|---|---|---|---|
| 1 | Email sent; LinkedIn follow-up to Head of Partnerships | Founder | Day 1 — non-negotiable |
| 1 | Kickoff call scheduled | ITC | Aim for same-week slot |
| 2 | Kickoff call held; KYC checklist received | Both | |
| 2 | KYC documents prepared and submitted | Founder | Gather in parallel with email; don't wait for the call |
| 3 | Sandbox credentials received | ITC | Unblocks parallel engineering |
| 3 | Pricing proposal received | ITC | |
| 4–6 | KYC review by ITC compliance | ITC | Their internal lead time; chase if no update by week 4 |
| 6 | Contract signature | Both | Target signed before Phase 1 begins (week 4 of overall timeline) |
| 6–8 | Production credentials issued | ITC | Phase 2 cannot start without these |

If any milestone slips by more than one week, escalate within ITC and consider whether to start a parallel conversation with a third PSP as insurance.

---

## 5. Risks and mitigations

| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| No response to initial email | Medium | High | LinkedIn follow-up day 3; warm intro via Stanbic or Paystack contacts if cold outreach stalls |
| KYC bottleneck on our side (missing documents) | Medium | High | Gather all documents in §3 during week 1, in parallel with the email |
| Pricing comes in materially higher than Paystack | Medium | Medium | Negotiate; accept reduced ITC routing share if pricing is uncompetitive on B2C; keep them on B2B where TransFlow advantage justifies the rate |
| Sandbox documentation incomplete or API patterns inconsistent with Paystack | Medium | Medium | The `PaymentProvider` interface in PRD §6.5 is designed to absorb provider differences; engineering will adapt |
| Stanbic-on-TransFlow turns out to need a clearing hop | Low | Medium | Verbally confirmed otherwise (PRD §1.1 decision 13); would add one day to B2B cash conversion if wrong |
| ITC compliance team queries DPA registration not yet finalised | Medium | Low | Share the DPC acknowledgement letter; explain registration is in progress and tracked as parallel workstream |

---

## 6. Notes for the kickoff call

Bring to the call:
- This brief, printed or shared on screen.
- A one-page architecture diagram showing where ITC sits relative to Paystack (covered conceptually in PRD §6.5).
- Three test scenarios to walk through with their technical team:
  1. Card payment with 3DS authentication.
  2. MoMo MTN payment with USSD prompt + callback.
  3. Bank transfer via the TransFlow rail.

Be ready to share:
- PRD §6.5 (payments) and §6.6 (multi-currency) so ITC can scope correctly.
- Expected request rates: 5–50 requests/minute at MVP, growing to 200–500/min at scale.
- That we are API-first with a separate mobile app, so the integration must work for both web (session cookies) and mobile (bearer-token) flows.
- That webhooks are received on the Express API at a stable endpoint (e.g. `https://api.procureglobal.gh/v1/webhooks/itc`) with HMAC signature verification.

Specific technical questions to ask:
- Idempotency: do they accept idempotency keys on retries? What's the dedupe window?
- Webhook signature scheme: HMAC-SHA256? Header name? Replay protection?
- Refund API: full and partial? Same-day or settlement-cycle bound?
- Dispute / chargeback handling: notification channel, response window, evidence portal?
- Currency support: GHS only, or USD too? (Paystack covers USD; we need to know if ITC duplicates.)
- Rate limits on the API.
- Status page or incident communication channel.

---

*This brief is a living document. Update §2 as items move from Pending to Received, and §4 as milestones are hit or slip. Anything that turns out to require a PRD change goes back into PRD §6.5 with a v3.6 bump.*