Integration plan

Everything in this prototype is simulated. These items need external access or approval before real payments.

• MyZaka wallet payments

  Needs Mascom approval

  Official API docs, merchant onboarding, sandbox credentials, settlement terms, PIN/auth flow.

• Wallet balance lookup

  Needs Mascom approval

  Only shown if the API permits. Demo balance used today.

• Visa / Mastercard

  Needs card gateway

  PCI DSS gateway with tokenisation and 3-D Secure. No card data on our servers.

• Bank account payments

  Needs bank partner

  Modular — enabled only once a bank API or authorised service is confirmed.

• Payment webhooks

  Needs provider

  Signed callbacks verified server-side; status polling as fallback.

• Refunds & reversals

  Needs provider

  Traceable, authorised correction workflow only.

• Accounts, roles & database

  Ready to build

  Commuter, driver, operator and admin roles with secure sign-in (Phase 2).

• Brand use

  Needs Mascom permission

  Theme is configurable; no endorsement is implied before formal approval.

Payment safeguards in place

• One unique key per payment attempt — retries never charge twice.
• Fixed fares come from the vehicle record, not the phone.
• Pending state until the provider confirms; never "success" offline.
• QR codes hold only a public vehicle ID.