activate, don't build

Turn on an API integration like a plugin — no developer, no server, no code

AfrikCru doesn't hand you code to host and maintain. Tell the agent what you need — starting with PawaPay mobile money, more connectors coming — and the integration runs on our servers, forever, not yours. No terminal, no deploy, no webhook to babysit.

Start on the web → See how it works
no sales call · no credit card · every call below is a real tool this agent runs
mcp://afrikcru/tools · session trace
live
// 1. merchant tells the agent what they need — in plain language
call merchant_register(
name: "Kampala Fresh Foods"
)
→ 201 { merchantId: "mrc_8f2a1c", dashboardToken: shown once, never logged }
// 2. merchant's own PawaPay key — encrypted before it touches disk
call vault_store_credential(
service: "pawapay", environment: "production"
secret: redacted client-side — AES-256-GCM
)
→ 200 { stored: true, plaintextLogged: false }
// 3. first real deposit — tested against your own PawaPay account
call pawapay_create_deposit(
provider: "MTN_MOMO_UGA", amount: "5000", currency: "UGX"
)
→ 202 ACCEPTED … webhook COMPLETED in 1.8s
// same three calls, any connector — pawapay_* today, next_provider_* whenever it's proven

you'll never actually see this — it's shown here so you can verify it's a real tool call, not a script reading you a line.

vs. the alternative

Why not just ask an AI coding agent?

They're great at writing code. That was never the hard part. The hard part is who runs it, forever, after you close the chat.

AfrikCruClaude Code / ChatGPT / GeminiA developer
Who writes the integrationNobody — it already existsYou, with AI helpThe developer
Who hosts it, running 24/7AfrikCruYou need your own serverThe developer sets it up, you maintain it after
Who verifies incoming webhooksAlready built & testedYou'd build this yourselfThe developer builds it
When the provider's API changesAfrikCru fixes it once, for everyoneYou find out when something breaksYou pay the developer again
Setup timeMinutes, in a conversationHours to days, if you can codeDays to weeks, plus hiring
Do you need to know how to codeNoYes (or heavy AI hand-holding)No — but you need to find and pay one
CostUsage-based subscriptionFree — just your own hostingSalary or freelance retainer
trust boundary

We move data. We never hold what's yours.

The agent sits between your business and the provider — but the boundary is structural, not a promise in a privacy policy. AfrikCru is not a payment aggregator, and it's not limited to payments.

You

The merchant — plain language in, a live integration out.

  • Your account with the provider
  • Your KYC, your compliance
  • Your funds, your settlement

AfrikCru agent

We never hold your funds, never do your KYC, never see your keys in plain text.

  • Never holds funds
  • Never does your KYC
  • Never logs a key in plain text
  • Runs & tests the integration

The provider

Whichever API you need — live: PawaPay. Next: whatever's proven.

  • Your account with them
  • Settles / responds directly to you
  • Same boundary, every connector
the vault

Your key, encrypted before it's stored — not after

AES-256-GCM, client-side. Audited: no route ever selects a raw key, and no plaintext ever reaches a log.

what you send once
sk_live_7bV3k...actualKey

Any provider's key — PawaPay today, same vault for whatever's next.

AES-256-GCM
what's actually stored
4f9e2a...c71b (ciphertext) + authTag

This is the entire row. No plaintext column exists.

scope, made explicit

What this agent is allowed to do — and what it can't

Hold or move your funds
Settlement always happens on your own provider account
Perform your KYC or compliance
You register directly with the provider
See or log your key in plain text
Encrypted client-side, verified by an automated audit test
Build, test, and confirm your integration
Live in minutes, in the open, with a real trace like the one above
connector registry

Not a payments tool. An API integration agent — proven one connector at a time

PawaPay is the first connector, proven end-to-end. Every future one — payments or not — goes through the same vault, the same trust boundary, the same real-pilot-merchant bar before it ships.

● live pawapay mobile money · 20+ African countries · deposits, hosted checkout, refunds, payouts (sandbox)
○ candidate logistics e.g. Sendy — not started, not promised
○ candidate messaging & notifications e.g. Africa's Talking, WhatsApp Business — not started, not promised
○ candidate identity verification e.g. Smile Identity — not started, not promised
○ candidate a second payment rail only after a real pilot merchant proves pawapay end-to-end — not started, not promised
picked from what merchants actually ask the agent for — never a roadmap we made up. tell it what you need connected.
session --new

Your next integration could be live before you finish reading the docs you didn't have to

Pay-as-you-use on technical usage. Never a percentage of your revenue.

Start on the web → See the connector registry