Payment requests

A payment request turns "you owe me" into something the other person can settle in moments. You state the amount and why; it appears in their Kit Pay app; they approve or decline in their own time, with their own approval. Nobody fumbles for numbers, nobody mistypes an amount, and both of you keep a record of how it went.

Sending a request

1. Choose the person, from contacts or by phone number.
2. Enter the exact amount you are owed and a note that explains it — the note does the diplomacy.
3. Send it. The request travels to their app and waits for their decision.

What the other person sees

Your request shows up with your name, the amount, and your note. Paying it is a normal sensitive action on their side — they review and approve it with their wallet PIN or supported device security, tied to that specific payment. Nothing about a request can take money without the payer's own approval, which is what makes requests polite: you are asking, visibly, not reaching into a pocket. The receiving side is covered in approve or decline a payment request.

Where requests shine

• Splitting a shared cost — everyone gets a request for their exact share, and the awkward arithmetic dies quietly.
• Informal business — a tailor or boda rider can request the agreed price, and the record protects both sides.
• Money across distance — a parent requesting school support gets the amount right without a phone call about digits.

Requests and scammers

Because a request cannot take money by itself, scammers dress requests up as things that look like they must be approved — a fee to release a prize, a refund that somehow needs your approval first. The rule that defeats all of it: approve only requests you recognise, from people you actually owe. An unexpected request deserves a decline, not benefit of the doubt. Scam warning signs has the patterns.