PLENA WhatsApp Verifier Technical Brief

East Africa needs a verifier that works where people already are: WhatsApp.

The first WhatsApp workflow should be brutally simple: send “VERIFY CODE” and receive a plain-language status, link, and scope limit. No app install. No PLENA vocabulary required.

WhatsApp-native verificationEast African Trust CorridorPublic log

Minimum viable message flow

1. User message

VERIFY PLENA-RR-0001

2. System lookup

Backend checks receipt ID, status, issuer, revocation, expiration, and public-safe fields.

3. Reply

PLENA receipt found.
Status: verified static public record.
Type: refusal receipt.
Issued: 2026-05-11.
Limit: not legal advice.
Open: joinplena.com/receipts/PLENA-RR-0001.html

Backend requirements

  • WhatsApp Business API number.
  • Webhook receiver.
  • Receipt lookup endpoint.
  • Rate limiting and abuse controls.
  • Language detection or language code command.
  • Audit log without exposing private evidence.
  • Fallback reply for unknown IDs.

Language-first pilot set

EnglishSwahiliKinyarwandaKirundiLugandaAmharicFrench

Do not claim this WhatsApp verifier is live until a real business number, webhook, and receipt lookup are deployed and tested.

Reply templates

FOUND:
PLENA receipt found.
Status: [verified / static public pilot / revoked / expired / redacted / pending].
Type: [receipt type].
Issued: [date].
Limit: This reply confirms only the public receipt summary. It does not expose private evidence.
Open: [public URL]

NOT FOUND:
No PLENA public receipt was found for [CODE]. Check the code or ask the sender for the official verification link.

REVOKED:
PLENA receipt found, but its public status is revoked or superseded. Do not rely on this receipt without reading the current public record.