> ## Documentation Index
> Fetch the complete documentation index at: https://ownpay.org/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> OwnPay is licensed under AGPL-3.0 and is completely free - no licensing fees.
> Production docs URL: https://ownpay.org/docs - append .md to any page URL for clean markdown.
> OwnPay requires PHP 8.3+, MySQL/MariaDB, and Redis.
> MCP server available at https://ownpay.org/docs/mcp for programmatic documentation queries.
> Use root-relative links (e.g. /quickstart) for internal navigation - do NOT include /docs prefix.
> Plugin development: consult /developer/plugin-types/ pages for correct interfaces and manifests.

# SMS Data Logs - Review Forwarded Messages and Payments

> Review raw forwarded SMS messages, inspect parser extraction status, and manually resolve unmatched incoming payments from the OwnPay admin.

The SMS Data Logs page displays all text messages forwarded from your paired Android devices. It acts as an audit trail for your automated manual gateway verification system.

## Getting here

1. Log in to the OwnPay admin dashboard
2. Under the **MOBILE & SMS** section in the left sidebar, click **SMS Data**

## Page sections

### 1. Match filters dropdown

* **All:** Shows all forwarded SMS records
* **Matched:** Displays SMS messages that successfully matched a customer's transaction ID
* **Unmatched:** Displays forwarded SMS messages that did not map to any active checkout transaction
* **Pending:** Displays forwarded SMS messages awaiting template mapping or manual checkups

### 2. Parsed SMS table

* **SENDER:** The source phone number or sender ID
* **AMOUNT:** Visual display of the cash amount parsed from the message
* **TRX ID:** The extracted Transaction ID
* **GATEWAY:** The manual gateway slug associated with the template
* **STATUS:** Visual status badge (`matched` in green, `unmatched` in red, `pending` in yellow)
* **RECEIVED:** Exact timestamp when the forwarded SMS reached the server

## SMS status states

* `matched`: The transaction ID extracted from the SMS matched a pending transaction record
* `unmatched`: The SMS was parsed, but the transaction ID did not match any active checkout transaction
* `pending`: The SMS is queued for parsing or lacks a matching template pattern

## Best practices

* Regularly monitor **Unmatched** logs to see if customers are inputting incorrect transaction IDs at checkout
* Verify the raw SMS body text in the log before executing manual approvals
* Do not manually delete SMS data logs unless performing system maintenance
* Do not worry if spam SMS messages appear as `unmatched`; the parser will ignore any messages that do not contain matching wallet templates

<Warning>
  Always cast transaction IDs to strings. If writing a custom script to query these logs, do not treat UUIDs or TrxIDs as numbers to prevent query failure.
</Warning>

## Related pages

* [SMS Center](/user-guide/mobile-sms/sms-templates) - Configure the parsing patterns
* [Paired Devices](/user-guide/mobile-sms/devices) - Connect the companion phones
* [Transactions](/user-guide/payments/transactions) - Manually approve payments


## Related topics

- [List Outbound SMS Queue](/docs/api-reference/list-outbound-sms-queue.md)
- [Retry Outbound SMS](/docs/api-reference/retry-outbound-sms.md)
- [Submit Received SMS](/docs/api-reference/submit-received-sms.md)
- [Get Pending Outbound SMS](/docs/api-reference/get-pending-outbound-sms.md)
- [Update SMS Template](/docs/api-reference/update-sms-template.md)