AATARCHITECTURE AFRICA
TECHNOLOGIES
Bounce
BOUNCE ONE · Transactions. Transformed.Concept demonstration · Illustrative institutions and balances · No live integrations
AAT · ARCHITECTURE AFRICA TECHNOLOGIES LIMITED

Transactions.
Transformed.

Where Your Transactions Come Alive.

One customer instruction can turn eligible everyday transactions into progress toward chosen financial destinations. Customer-directed. Non-custodial by design. Kenya-first.

◉ BOUNCE ONE● DEMO
Illustrative linked-provider balance · not held by BOUNCE
KES 687/-
Illustrative BOUNCE capture
KES 20.00
✓ KCB Savings · destination confirmed in simulation
Original payment: KES 1,000 to Naivas
◇Rules⌁Destinations▥Footprints

KES 687/- is an illustrative provider balance, not a BOUNCE wallet. Live visibility requires an authorized provider interface.

HOW IT WORKS

Simple. Directed. Automatic.

One standing customer instruction. A seven-stage journey that leaves the original eligible payment independent.

1

Choose

Select either a fixed KES amount or a percentage, plus an eligible destination.

2

Connect

Authorize an eligible payment channel through agreed provider interfaces.

3

Transact

Make an everyday payment normally through your provider.

4

Capture

Initiate the separate, customer-authorized additional amount.

5

Redirect

Authorized institutions route funds toward the chosen destination.

6

Inform

Confirm the outcome after the appropriate receiving-institution response.

7

Track

Keep a capture footprint; check actual balances with the account provider.

Three institutions of trust. Three distinct messages.

The originator can confirm the payment; the receiver can confirm its own credit; BOUNCE can send its capture confirmation last. Each party retains its existing customer relationship and notification practices.

Original payments remain independent.

If a separate capture cannot proceed due to insufficient funds, the original eligible payment is not cancelled by BOUNCE. Initial outcomes shown in the prototype are Successful or Failed, not invented settlement states.

FINANCIAL SUPERMARKET

One ecosystem. Many financial goals.

A populated, curated illustration of how financial institutions could showcase savings, loan, investment, insurance, pension and SACCO products to consenting customers.

Illustrative directory only. Named institutions are examples, not confirmed BOUNCE participants, endorsed offers, verified product listings or live registration integrations. A live storefront would require institutional approval and verified links.
PARTNER ECOSYSTEM

Value for participants. Independence for everyone.

BOUNCE offers an elective additional capability, not an invitation to surrender customers, funds, transaction control or branding.

📱

Payment originators

Mobile-money operators, banks, card issuers and payment platforms can offer customers a richer post-transaction financial journey without replacing ordinary payment rails.

🏦

Receiving institutions

Banks, SACCOs, MMFs, lenders and pensions can receive eligible customer-directed allocations through authorized channels and present their own products to interested customers.

🛡️

Insurance & health

Insurers and cover providers may offer eligible premium or contribution destinations, subject to product rules, consent, premium acceptance and reconciliation.

⌘

Integration partners

Processors, gateways and fintech infrastructure specialists can explore APIs, event validation, capture routing, acknowledgment, security and reporting.

Why explore BOUNCE?

Relevance

Give consenting customers practical reasons to connect routine payment activity with independently held financial goals.

Distribution

Showcase institution-approved product offerings and approved onboarding journeys in an accessible supermarket environment.

Measurable pilot value

Test opt-in, successful captures, destination confirmation, reconciliation, customer experience and delivery costs with agreed evidence.

Examples discussed in outreach or concept visuals (such as Airtel, NCBA, KCB, Equity, CIC, Britam and Cellulant) are not presented as confirmed integrations or endorsements.

PARTNER-LED INTEGRATION · DEDICATED BRIEF

A practical route from interest to evidence.

For technical, product, compliance and business-development teams evaluating how BOUNCE ONE could connect to existing regulated infrastructure without disrupting the customer’s original transaction.

What BOUNCE coordinates

Customer-authorized standing rules, eligibility events, capture instructions, destination identifiers, confirmation records, reconciliation references and an auditable capture footprint. BOUNCE does not hold funds or pose as the source-of-truth account balance.

One rule: % OR fixed KESOriginal payment independentSuccessful / Failed

What institutions retain

Money movement, account custody, product approval, ledger and balance authority, compliance responsibilities, their direct customer relationship and existing messages. Interfaces and liabilities must be agreed before any live pilot.

Customer consentProvider account recordsControlled pilot

A five-gate integration pathway

01

Discover

Confirm the role, use cases, customer consent, target rails and legal responsibilities.

02

Map

Define eligible events, fixed/percentage rule handling, endpoints, settlement ownership and exceptions.

03

Sandbox

Exchange synthetic events and verify idempotency, security, non-interference and failure handling.

04

Pilot

Run a limited, approved experiment with participant controls and provider-side confirmations.

05

Measure

Reconcile, evaluate customer outcomes, agree economics and decide on expanded deployment.

Pilot performance dashboard — measures to agree

These are proposed measurement definitions, not claims that BOUNCE or any named payment provider currently achieves particular volumes, uptime or response times.

Customer activation

Opt-in and rule-activation rate; consenting participants by channel and destination.

Eligible capture rate

Eligible original events versus valid additional capture attempts.

Confirmed success

Successful captures confirmed by receiving institutions / valid attempts.

Confirmation latency

Measure median and 95th-percentile acknowledgment and receiving-credit times.

Reconciliation & exceptions

Matched references, failed capture causes, reversals and duplicate-prevention incidents.

Original-payment integrity

Confirm BOUNCE capture failure has not independently cancelled an eligible original payment.

PARTNER OPPORTUNITY EXPLORER

Test a scenario, not a market claim.

Enter your own assumptions. Daily volume and rates below are hypothetical inputs for discussions, not actual Safaricom, Airtel, Visa, bank or BOUNCE performance.

ILLUSTRATIVE OUTPUT

Potential capture activity

Confirmed captures / day
—
Captures / month
—
Capture value / day
—
Capture value / month
—

Model assumes independent filters for eligible transactions, customer opt-in and confirmed success. It estimates additional customer-directed captures only, not revenue, an investable valuation, customer balances or guaranteed partner performance.

Technical questions we expect a serious partner to ask

Who moves and holds funds?
Only licensed or otherwise authorized institutions in their agreed roles. BOUNCE coordinates customer instructions, capture outcomes and reference data. It does not serve as a wallet, account, money-holder or balance authority.
How does the receiving institution confirm?
A partner-defined acknowledgment, signed event, status query or equivalent interface confirms the relevant state. An instruction's acceptance alone must never be labeled a credited destination. Matching reference and reconciliation rules are agreed per rail.
How are interruptions and duplicate events handled?
Proposed controls include idempotency identifiers, replay-safe event handling, audit trails, conflict resolution, retry discipline and explicit failure reporting. Detailed implementation requires partner technical design and testing.
Can three SMS messages reach the customer?
Yes, where providers and customer preferences permit: the original payment provider, the receiving financial institution and BOUNCE each communicate a distinct fact. BOUNCE can arrive last once the proper destination confirmation is received.
Can the institution display its products?
With formal participation and approvals, an institution could display verified offers, conditions and an authorized registration link. The demonstration directory is illustrative and does not yet represent these storefront connections.
What about account balances and real-time guarantees?
Actual balances remain the institution's records. Authorized APIs could make provider-reported values visible in BOUNCE. Low-latency confirmation is a design objective to be measured during partner tests, not a guaranteed number of seconds.
ABOUT AAT

Architecture Africa Technologies Limited

AAT is developing BOUNCE ONE as a customer-directed, non-custodial financial allocation and orchestration architecture. Kenya is the first concept market; broader expansion would depend on integrations, legal review and testing.

Our mission

Enable everyday eligible transactions to advance independently held financial goals through customer choice and accountable execution.

Our approach

Respect existing relationships, prove interoperability with providers, and build measured, commercially useful institutional integrations.

Five principles behind the platform

Open any highlight to explore the principle in more detail.

🇰🇪 Kenya-first
The demonstration is grounded in KES, familiar Kenyan channels and potential financial destinations, with future expansion subject to market-specific readiness.
👥 Customer choice
Exactly one rule method per instruction: a fixed KES amount or a percentage of the original eligible payment, with a chosen receiving destination and customer control.
🛡 Non-custodial design
BOUNCE holds no funds. Providers execute fund movements and keep their accounts, ledgers, customer relationships and balance records. Original payments remain independent.
🔗 Partner-led integration
Agree consent, eligibility, security, event mapping, capture routing, receiving-institution confirmation and reconciliation before a controlled live pilot.
🏦 Institutional independence
Each participating institution retains its customers, branding, products, records, approvals and notification rights. BOUNCE adds a capability without taking over an institution.

BOUNCE — Transactions. Transformed.
Where Your Transactions Come Alive.

BOUNCE ONE · INTERACTIVE SIMULATOR

See a transaction transform.

Configure one additional capture, choose an illustrative destination and simulate receiving-institution confirmation. Successful or Failed footprints only. No real funds move.

The original payment is represented separately. No API calls, customer accounts, real messages or actual bank balances are accessed.

LIVE PREVIEW OF SIMULATED SETTINGS

Transaction summary

Adjust the rule or select Simulate transaction. No money will move.

Simulations: 0 · Successful: 0 · Failed: 0

Capture footprints

No simulated captures yet.

Three independent notification examples

Simulated records appear after a demonstration. Actual communication channels remain subject to originator, receiving institution and BOUNCE agreements.

Originator

Normal payment confirmation.

Receiving institution

Destination credit confirmation, when applicable.

BOUNCE

Success or failure notification after outcome verification.

CONTACT AAT

Start an informed conversation.

Business development, financial institutions, payment platforms, integration specialists and prospective pilots can prepare a structured inquiry here.

Let's talk about the opportunity.

We can discuss your role in the ecosystem, prospective pilot scope, interfaces, product distribution, operational safeguards and measurement approach.

Contact channel: not yet published

AAT's verified corporate email and a secure form-processing service must be configured before launch. This prototype never silently submits personal details to a server.

Suggested outreach package

A brief introduction, one-page Why BOUNCE proposition, relevant use case, requested integration role and proposed exploratory discussion.

Nothing is submitted by this website. You can copy your inquiry or open your email application to choose a recipient.