SMS automation
SMS data
Every payment SMS Paybob has received or you entered by hand, and its status.
SMS Data lists every payment SMS Paybob has stored: forwarded by a device, sent through the Inline SMS API, or entered by hand. Each row is one payment you received, with the values read from the SMS.
Statuses
| Status | Meaning |
|---|---|
| Approved | Ready to confirm a payment. |
| Pending | Waiting for balance verification to confirm it, or set to Pending by hand. Can't confirm a payment yet. |
| Used | Already confirmed a payment. It can't be used again. |
Tabs filter the list by status: All, Approved, Pending and Used.
The list
Each row shows the Device it came from, the Payment Method (its SMS filter), the Type and Currency of that filter, the sender's Phone Number, the Transaction ID, the Amount, the Balance, the SMS Date/Time and the Status.
Search by phone number, transaction ID, date/time, device or payment method, and filter by type, device or payment method. Click a transaction ID to copy it.
Each transaction ID can appear only once. A second SMS with the same transaction ID is treated as a duplicate and not stored again, whichever way it arrives.
Adding an SMS by hand
Use Create SMS when an SMS didn't reach Paybob, for example because the phone was off, or to test an SMS filter.
| Field | What to enter |
|---|---|
| Device | Optional: the phone the SMS belongs to. |
| Entry Type | Automatic to paste the SMS, or Manual to type each value. |
| Payment Method | The SMS filter for this kind of SMS. |
Automatic: paste the complete SMS into Message (Copy & Paste from SMS). The Parsed Preview shows what Paybob reads from it as you type. The filter must read both an amount and a transaction ID. The SMS is saved as Approved.
Manual: enter the Amount, Phone Number, Transaction ID, Reference, SMS Date/Time (optional) and Status yourself.
An SMS added by hand never changes balance verification.
Once saved as Approved, the SMS can confirm a matching Pending payment within a minute, just like a forwarded one.
Editing and deleting
Edit changes any value, including the status. Delete removes the row. Deleting a Used SMS doesn't undo the payment it confirmed.
Be careful setting an SMS back to Approved
An approved SMS can confirm a payment. Only approve an SMS you've checked against your account.
Inline SMS API
The Inline SMS API lets any tool that can send a web request forward payment SMS to Paybob, without the Android app. For example, an iPhone Shortcuts automation that runs when a payment SMS arrives, or a small script.
Click Inline API on the SMS Data page. It shows:
- whether the API is Enabled or Restricted;
- your secret endpoint URL, with a copy button;
- an example request.
Send a POST request to the URL with the SMS sender and the complete, unmodified message:
{
"sender": "bKash",
"message": "You have received Tk 500.00 from 01700000000. Fee Tk 0.00. Balance Tk 5,500.00. TrxID 9XA7K2M1QP at 03/10/2026 10:00"
}Paybob reads the message with your SMS filters and stores it as Approved. SMS sent this way skip balance verification and aren't linked to a device. Sending the same SMS twice is safe: the second request returns the row already stored.
The full request and response reference, with code samples, is in the API reference.
Treat the URL like a password
The secret is part of the URL. Anyone who has it can submit SMS that may confirm pending payments. Use Regenerate if it's ever exposed: the old URL stops working at once. Use Restrict to switch the API off while you're not using it, without changing the URL.
Permissions
Viewing, creating, editing and deleting SMS data each have their own permission. Managing the Inline SMS API has a separate permission, since its URL is a secret. See Staff and roles.