- Kinondoni Vijana , P.o Box 8010, Dar es salaam , Tanzania
- +25662959557
- info@prot.co.tz
This document outlines the integration flow and complete customer journey for payments processed through Pesapal on the PROT platform.
The purpose of this document is to provide a clear understanding of:
• How customers interact with the platform
• How appointments and event bookings are processed
• How Pesapal is integrated into the payment workflow
• How transaction confirmations are handled
• Security and compliance considerations
PROT is an appointment and event management platform that allows users to schedule appointments, register for events, and complete payments securely online.
The platform integrates with Pesapal to facilitate secure digital payments through multiple payment channels.
Supported payment methods may include:
• Mobile Money
• Bank Transfers
• Debit Cards
• Credit Cards
Supported payment channels include:
• M-Pesa
• Airtel Money
• Mixx by Yas (Tigo Pesa)
• Visa
• Mastercard
• Supported bank payment channels available through Pesapal
The following parties are involved in the transaction process:
Customer/User
End user booking appointments or registering for events
PROT Platform
Platform managing appointments, registrations, schedules, and payments
Pesapal
Payment gateway provider
Mobile Network Operators/Banks
Payment processors
Admin Team
Reviews and manages bookings, appointments, and payments
Integration Components
Customer Frontend
Website or application interface used by customers
Backend System
Handles appointments, events, bookings, and payment requests
Pesapal API
Processes payment requests and confirmations
Notification System
Sends payment confirmations and booking notifications
Step 1 – Customer Visits Platform
The customer accesses the PROT website using:
• Mobile device
• Tablet
• Desktop computer
The customer can:
• Browse available events
• View appointment services
• Search schedules
• View availability and pricing
Step 2 – Event or Appointment Selection
The customer selects:
• Event registration
or
• Appointment booking
Actions performed:
• Select date and time
• Choose service or event type
• Continue to booking
System Actions:
• Booking information is temporarily stored
• Availability is checked automatically
Step 3 – Booking Process
The customer proceeds with booking.
The customer provides:
• Full Name
• Phone Number
• Email Address
• Appointment details or event information
System validates:
• Required fields
• Slot availability
• Payment amount
Step 4 – Booking Creation
Once details are confirmed:
The PROT backend:
• Generates a unique booking reference number
• Creates a pending booking record
• Stores customer information securely
Booking status initially becomes:
PENDING PAYMENT
Step 5 – Payment Method Selection
Customer selects Pesapal as preferred payment gateway.
Available payment channels include:
• M-Pesa
• Airtel Money
• Mixx by Yas
• Visa/Mastercard
• Bank payment channels
Step 6 – Payment Request Initialization
The PROT backend sends a secure payment request to Pesapal API.
The request includes:
• Booking Reference Number
• Customer Name
• Customer Phone Number
• Amount
• Currency
• Callback URL
• Transaction Description
Security Measures:
• HTTPS encrypted communication
• API authentication credentials
• Secure server-to-server communication
Step 7 – Customer Payment Authorization
The customer is redirected to the Pesapal hosted payment environment.
Depending on selected payment method:
Mobile Money:
Customer:
• Receives payment prompt
• Enters mobile money PIN
• Confirms payment
Card Payment:
Customer:
• Enters card details
• Completes OTP or 3D Secure verification where applicable
Step 8 – Payment Processing
Pesapal processes payment through the selected financial institution.
Possible transaction outcomes:
• Successful
• Failed
• Cancelled
• Pending
Step 9 – Payment Confirmation Callback
After payment processing:
Pesapal sends callback information to the PROT backend.
Callback contains:
• Transaction ID
• Booking Reference
• Payment Status
• Amount Paid
• Payment Method
• Timestamp
Backend validates:
• Transaction authenticity
• Matching amount
• Valid booking reference
Step 10 – Booking Status Update
Upon successful verification:
Booking status becomes:
CONFIRMED / PAID
System actions:
• Payment recorded
• Confirmation generated
• Customer notified
• Administrator notified
If payment fails:
Booking status becomes:
FAILED PAYMENT
Step 11 – Customer Notification
Customer receives:
• Booking confirmation
• Payment confirmation
• SMS or Email notifications where applicable
Notification details may include:
• Booking Number
• Amount Paid
• Appointment date and time
• Event details
Step 12 – Service Delivery
Platform administrators process bookings.
Possible fulfillment:
• Appointment scheduling
• Event attendance access
• Digital event links
• Service activation
Booking status transitions:
• Processing
• Scheduled
• Completed
Step 13 – Support
Customers may contact support for:
• Payment assistance
• Booking modifications
• Appointment inquiries
• Technical support
Support channels:
• Phone
• Email
• WhatsApp
• Website contact form
Customer selects appointment or event
Customer proceeds to booking
Booking created on PROT
Customer selects Pesapal
PROT sends payment request to Pesapal
Customer authorizes payment
Pesapal processes transaction
Pesapal sends callback response
PROT validates transaction
Booking status updated
Customer receives confirmation
Service fulfillment begins
Security measures include:
• HTTPS/SSL encryption
• Secure API authentication
• Callback verification
• Server-side payment confirmation
• Administrator access controls
• Logging and monitoring
Sensitive Data Handling:
• Card information is not stored on PROT servers
• Payment processing is handled by Pesapal
• Customer information is accessible only to authorized personnel
The platform handles failures through:
• Transaction status checks
• Retry mechanisms
• Customer notifications
• Manual review procedures
Common failure scenarios:
• Insufficient balance
• User cancellation
• Network timeout
• Invalid credentials
• Service downtime
The administration team may reconcile:
• Booking records
• Pesapal transaction reports
• Settlement reports
• Payment confirmations
Transaction logs are maintained for:
• Payment requests
• Payment responses
• Callback notifications
• Booking status updates
• Administrative activities
These logs support:
• Compliance reviews
• Troubleshooting
• Fraud prevention
• Operational monitoring
The PROT platform integrates securely with Pesapal to provide users with a seamless and reliable booking and payment experience.
The integration supports:
• Multiple payment channels
• Real-time transaction processing
• Automated payment confirmations
• Secure customer data handling
• Efficient appointment and event management
