06b · Conversational · WhatsApp

The price lives in WhatsApp.

The seller writes pay 100 cafea in WhatsApp. The bot returns a miaPOS payment link. The customer pays in their own banking app. No new app to install, no checkout page to leave.

Number
ChannelsWhatsApp Business · 1:1 chat
LocalesRO · RU · EN · FR · DE
StatusLive · production · since 14.06.2026

The store is wherever the seller already talks to the customer.

For most of our merchants — D2C, HoReCa, services, social commerce — the channel where the deal is closed is WhatsApp. The conversation is already there. The miaPOS bot just turns one of those messages into a payment.

A seller writes pay 245 #pizza-large to the miaPOS WhatsApp bot. The bot replies in the same chat with a payment link and a 245 MDL amount. The seller forwards the link to the customer (same WhatsApp thread, another WhatsApp thread, SMS, e-mail — wherever the customer is). The customer opens the link, confirms in their banking app, and the seller gets a paid notification back in WhatsApp.

The seller never leaves WhatsApp. The customer never sees a card form. The money moves directly from the customer's bank account to the merchant's bank account on the same instant-payment rail.

WhatsApp · +373 690 02 773
pay 245 #pizza-large
Seller · 14:32
💳 Payment ready
Amount: 245 MDL
Description: pizza-large
Open link to pay →
miaPOS bot · 14:32
Paid · 245 MDL — receipt sent to the customer
miaPOS bot · 14:33

How it works.

From first message to paid notification, all inside one WhatsApp chat.

1
Seller sends their first message
The seller opens WhatsApp and writes anything to +373 690 02 773. There is no /start, no contact-sharing handshake. The phone number that sent the message is the identity — the bot resolves it through the partner bank and confirms the seller is bound. An unknown phone gets a polite refusal.
2
Seller types an amount
Five equivalent forms: pay 245, /pay 245 "Pizza" #tag, /rtp 250, or just the number 245 (interpreted as pay 245). The tag and description are optional and used for reconciliation.
3
Bot returns a payment link
The bot replies in the same chat with the amount, optional description, and a tap-to-open payment link. The seller forwards the link to the customer through whichever channel the customer is on — usually the same WhatsApp thread.
4
Customer confirms in their bank app
The link opens a single payment screen. The customer scans the QR or taps the deep-link to authorise the exact amount inside their own trusted banking app. No card fields, no CVC, no 3DS.
5
Seller sees "Paid" in WhatsApp
The bot updates the chat with a paid (or failed) status. The merchant's account is credited in seconds.

Commands the seller can use.

Short, forgiving grammar. Five locales out of the box.

pay 100 "Espresso" #cafea

Issue a payment link for 100 MDL. The description and tag are optional and used for reconciliation in the merchant portal.

/pay 100

Slash-prefixed alias of pay — equivalent.

100

Implicit shorthand. Just typing a number is interpreted as pay 100. Safe by WhatsApp Cloud API constraint — the bot lives in 1:1 chats only; numbers cannot leak into group context.

/rtp 250 "Consultation"

Issue a Request-to-Pay where the underlying instant-payment rail supports it.

/lang

Opens an interactive list with five language options — Română, Русский, English, Français, Deutsch. The chosen locale persists per phone across all future messages.

WhatsApp vs Telegram — same product, two surfaces.

Both channels share the same broker and the same payment rail. They differ in what the underlying messaging API allows.

AspectTelegram (@miaposbot)WhatsApp (+373 690 02 773)
Where the bot lives1:1 chat, group chats, channels, inline mode in any chat (@miaposbot 245 #tag)1:1 chat only (Meta does not expose inline mode or general group surface)
Onboarding/start + Share phone tap, ~30 secondsThe first message is the binding event — the phone is intrinsic
Free-form repliesAnytimeWithin the 24-hour customer-service window of the seller's last inbound message; late status updates require Meta-approved Utility templates
LocalesRO · RU · EN · FR · DERO · RU · EN · FR · DE
Payment railSame IPS rail, same brokerSame IPS rail, same broker
Payment link surfaceTap-to-open inside Telegram (Mini App possible)Tap-to-open inside any browser the WhatsApp link launches

For sellers who already live in WhatsApp.

The acceptance surface fits the channel where the deal is closed.

D2C & HoReCa

Pre-orders, deposits, takeaway. The conversation that closes the sale is the same conversation that collects the money.

Services

Consultations, appointments, on-demand. One thread per client, payments inside it.

Social commerce

The seller already routes Instagram or TikTok DMs to WhatsApp. The payment lives at the end of that thread.

Cross-border SMEs

WhatsApp is the dominant SME messaging channel across most of miaPOS's expansion markets. One bot covers many geos.

Field teams & delivery

Couriers, technicians, sales reps. Phone is the only device; WhatsApp is the only app.

Marketplaces in chat

The seller's customer book is WhatsApp threads. Payments stay where the relationship already is.

"The customer never installs anything. The seller never opens anything new. The money moves on the same rail it always would."

Try it, or build with it.

If you sell — open WhatsApp, message , and follow the onboarding. Your phone needs to be already known to your partner bank. If you build for merchants — the bot, the backend, the locale picker and the broker contract are documented.