Questions about ScanPay.

ScanPay is a payment gateway and transaction platform. It helps businesses and individuals process payments, verify that payments have actually been made, facilitate transactions through escrow, and automate billing for internet service providers and utilities.

Businesses, marketplaces, developers, service providers and individuals. Which services apply depends on the service and your setup, so contact the ScanPay team to confirm what fits your case.

Payment verification, escrow solutions, a payment gateway, M-Pesa STK Push integration, transaction infrastructure, ISP billing, and utility billing for electricity, water and gas.

ScanPay is based in Nairobi, Kenya. You can reach the team at support@scanpay.africa or on 0723 658 888.

A customer makes a payment. ScanPay receives or checks the relevant payment information. The transaction details — amount, reference, method and status — are confirmed, and your business or system is notified so you can complete the transaction.

Yes. Verification can run through the API and webhooks, so your system is told when a transaction reaches a verified state instead of someone checking manually.

Yes. Verification is available through the ScanPay API, so it can be called from a website, a mobile application, or an internal business system at the point where the decision to proceed is made.

Yes. That is what verification is for — confirming payment details before you release a product, service, access or funds.

No. Verification confirms what happened with the payment. It reduces uncertainty; it does not remove every risk from a transaction, and it does not vouch for the other party's conduct.

The buyer pays into the transaction rather than directly to the seller. ScanPay confirms the payment has been received, both parties see the same status, and the transaction proceeds on the terms agreed at the start.

Marketplaces, businesses handling higher-value transactions, and individuals transacting with someone they do not already know. Eligibility depends on the transaction and is agreed with the ScanPay team before go-live.

Verification confirms a payment already made directly to you. Escrow places ScanPay in the middle of the transaction so payment is received and confirmed before the agreed transaction proceeds.

No. ScanPay facilitates the transaction and confirms the payment status. It does not make claims about legal custody, licensing, insurance or guaranteed outcomes.

Connect ScanPay to your website, application or business system. Payments are collected through the gateway, each carries a transaction reference and status, and your system is notified when the payment is confirmed.

Yes. ScanPay exposes a REST API and webhooks, so it can be connected to a website, a mobile application, an ERP, a POS or an internal business system.

Each transaction carries a status. Your system can query it through the API or receive it through a webhook the moment it changes, and the dashboard shows the same information.

STK Push sends a payment prompt directly to a customer's phone. Instead of reading out a paybill number and account reference, the customer receives the request with the amount already filled in and approves it with their M-Pesa PIN.

Your system calls the ScanPay STK Push endpoint with the amount, the customer's phone number and your own reference. The customer approves the prompt, and ScanPay sends the confirmation back to your callback URL.

A 1% transaction fee applies to transactions processed through the ScanPay M-Pesa integration.

Yes. STK Push can be integrated into websites, applications, ERP, POS and other business systems.

Yes. ScanPay supports internet service providers with billing and payment collection workflows, including invoicing, payment status tracking, and updating the customer account once a payment is verified.

Yes. Electricity billing is supported for both prepaid and postpaid arrangements, billed against meter or account numbers with payment verification before the account is updated.

Yes. Water billing covers metered accounts, consumption-based bills, arrears carried across cycles, collection and payment verification.

Yes. Gas billing covers cylinder refills and metered supply against a customer gas reference, with payment verification before a delivery or credit is released.

Yes. A customer account can carry more than one service, and the bills appear together in the same billing view.

Yes. A REST API covers initiating payments, requesting payment verification, creating escrow transactions, billing, and querying transaction status.

Yes. Webhooks push transaction events to your endpoint as statuses change, so your system does not have to poll for updates.

API reference and integration guides are available in the ScanPay merchant portal at my.scanpay.africa.

Yes. Gateway, verification, escrow and billing all write to the same transaction record, so one reference follows a transaction end to end.