Banks and wallets

Confirm the person.
Then the 85.000 FC.

Wallets and banks cannot wait on a slow SMS. Zindua sends the login code on WhatsApp, the payout challenge on PushMirror with amount and payee, KYC “one more photo”, and a fraud ping when the city changes.

Wallet OTP, payouts, KYC, new device.

African woman with a Neo Bank wallet challenge, OTP code, and $85 payout cards

What you send

Banking & fintech

Wallet OTP, payouts, KYC, new device.

OTP

Transfers

Sent, received, failed. Chat when they must act now. Email for the monthly file.

KYC

Received, extra photo, approved. Templates, not a second ESP for compliance mail.

Fraud

New device, new city, new payee. Context on the challenge before they tap.

On the ground

Payout to **** 2080, approve on the phone they already have

The user taps send in the wallet. PushMirror shows 85000 CDF and the masked payee. They approve. WhatsApp is the fallback OTP when push is off. Email keeps the statement. One project, not three vendors at launch.

Sign in and step up OTP on WhatsApp
PushMirror: amount, payee, city, approve or deny
KYC: document in, extra selfie, account open

9:41

●●●

Serenity Wallet

Payout challenge

Confirm

Envoyer 85000 CDF vers **** 2080 ? Appareil: Pixel · Kinshasa. Approuver ou refuser.

14:22

Approuver

14:22

Paiement envoyé. Reçu aussi par email. Si ce n’était pas vous, geler le compte dans l’app.

14:23

How it works

Three steps. Same API.

Link the desk, map the templates, send when the file moves. One POST /send on every channel.

Step 01

Connect channels

WhatsApp line + PushMirror in the app. Email stays on your SMTP.

Step 02

Map risk

OTP vs 1 tap vs deny. Amount and payee in the payload.

Step 03

Ship one send()

wallet-payout.ts · TypeScriptAuto

const challenge = await zindua.pushMirror.create({  userId: user.id,  type: "approve",  purpose: "payout",  context: {    amount: "85000 CDF",    payee: "**** 2080",    city: session.city,  },  fallback: { channel: "whatsapp", to: user.phone },});