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.
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.
KES 687/- is an illustrative provider balance, not a BOUNCE wallet. Live visibility requires an authorized provider interface.
One standing customer instruction. A seven-stage journey that leaves the original eligible payment independent.
Select either a fixed KES amount or a percentage, plus an eligible destination.
Authorize an eligible payment channel through agreed provider interfaces.
Make an everyday payment normally through your provider.
Initiate the separate, customer-authorized additional amount.
Authorized institutions route funds toward the chosen destination.
Confirm the outcome after the appropriate receiving-institution response.
Keep a capture footprint; check actual balances with the account provider.
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.
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.
A populated, curated illustration of how financial institutions could showcase savings, loan, investment, insurance, pension and SACCO products to consenting customers.
BOUNCE offers an elective additional capability, not an invitation to surrender customers, funds, transaction control or branding.
Mobile-money operators, banks, card issuers and payment platforms can offer customers a richer post-transaction financial journey without replacing ordinary payment rails.
Banks, SACCOs, MMFs, lenders and pensions can receive eligible customer-directed allocations through authorized channels and present their own products to interested customers.
Insurers and cover providers may offer eligible premium or contribution destinations, subject to product rules, consent, premium acceptance and reconciliation.
Processors, gateways and fintech infrastructure specialists can explore APIs, event validation, capture routing, acknowledgment, security and reporting.
Give consenting customers practical reasons to connect routine payment activity with independently held financial goals.
Showcase institution-approved product offerings and approved onboarding journeys in an accessible supermarket environment.
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.
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.
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.
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.
Confirm the role, use cases, customer consent, target rails and legal responsibilities.
Define eligible events, fixed/percentage rule handling, endpoints, settlement ownership and exceptions.
Exchange synthetic events and verify idempotency, security, non-interference and failure handling.
Run a limited, approved experiment with participant controls and provider-side confirmations.
Reconcile, evaluate customer outcomes, agree economics and decide on expanded deployment.
These are proposed measurement definitions, not claims that BOUNCE or any named payment provider currently achieves particular volumes, uptime or response times.
Opt-in and rule-activation rate; consenting participants by channel and destination.
Eligible original events versus valid additional capture attempts.
Successful captures confirmed by receiving institutions / valid attempts.
Measure median and 95th-percentile acknowledgment and receiving-credit times.
Matched references, failed capture causes, reversals and duplicate-prevention incidents.
Confirm BOUNCE capture failure has not independently cancelled an eligible original payment.
Enter your own assumptions. Daily volume and rates below are hypothetical inputs for discussions, not actual Safaricom, Airtel, Visa, bank or BOUNCE performance.
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.
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.
Enable everyday eligible transactions to advance independently held financial goals through customer choice and accountable execution.
Respect existing relationships, prove interoperability with providers, and build measured, commercially useful institutional integrations.
Open any highlight to explore the principle in more detail.
BOUNCE — Transactions. Transformed.
Where Your Transactions Come Alive.
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.
Simulations: 0 · Successful: 0 · Failed: 0
Simulated records appear after a demonstration. Actual communication channels remain subject to originator, receiving institution and BOUNCE agreements.
Normal payment confirmation.
Destination credit confirmation, when applicable.
Success or failure notification after outcome verification.
Business development, financial institutions, payment platforms, integration specialists and prospective pilots can prepare a structured inquiry here.
We can discuss your role in the ecosystem, prospective pilot scope, interfaces, product distribution, operational safeguards and measurement approach.
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.
A brief introduction, one-page Why BOUNCE proposition, relevant use case, requested integration role and proposed exploratory discussion.