Questions,
answered directly.

ProofPay is a Denxor Labs application that turns supported payment notifications and receipts into structured, searchable transaction records stored on your device, so you can find proof of a payment later without digging through old messages and screenshots.

Payment evidence — SMS confirmations, screenshots, paper receipts, banking notifications — tends to scatter across different apps and formats. ProofPay gives that evidence one structured, searchable home.

Anyone who's ever needed to answer "did I actually pay this?" — personal use, small business record-keeping, expense tracking, reimbursements, and resolving payment disputes are the use cases the product is built around.

ProofPay Basic is manual: you share a payment message with ProofPay yourself, using your device's Share function, and nothing is processed until you do. ProofPay Premium adds optional automated processing: once you authorize it, relevant payment messages are identified and processed without you sharing each one. Both store transaction records locally on your device. See the Basic Privacy Policy and Premium Privacy Policy for the full detail on each.

No. ProofPay is a record-keeping tool — it reads information from payment messages and documents you already received, it doesn't connect to any bank's backend to confirm a payment actually settled. A ProofPay record is evidence of what a message or receipt said, not an independent bank confirmation.

No — treat it as organized personal evidence, not an official bank document. For situations that legally require a bank statement, get that from your bank directly.

ProofPay is free to download directly during active development — there's no paywall on the current build. Pricing beyond this stage hasn't been finalized publicly.

Download the APK from the Download section, open the downloaded file on your Android device, and allow the install when prompted. Android will warn that it's from outside the Play Store — that's expected for a direct APK, not a sign anything is wrong.

Download the latest APK from the same Download section and install it over the existing app. There's no in-app auto-update yet — check the Updates destination for new releases.

Android 7.0 (API level 24) and above.

Check ProofPay's product page for current platform availability — this changes as development progresses, so it's kept in one place rather than duplicated here.

Yes — the security architecture described in the Data & Security Policy (Android Keystore–backed encryption) reflects the current Android build.

Message parsing, transaction storage and record-keeping happen on-device. Receipt verification via QR code opens the online Denxor Labs verifier, which does need connectivity to check a signature.

Transaction-related details contained in supported device messages or notifications — merchant, amount, date and reference — used to build a structured transaction record. Full detail is in the Privacy Policy.

It's what makes a "transaction record" useful at all — without merchant, amount, date and reference, there's nothing to search or show you later.

No. Denxor Labs does not sell user information.

No. ProofPay's data isn't used for advertising purposes.

For the core transaction-capture flow, no — records are parsed and stored locally on your device. See Trust Center for the full data-flow walkthrough.

Yes — that's the default for transaction records. The receipt-verification flow is the exception, since checking a cryptographic signature happens through the online verifier rather than on-device.

Yes — you can delete individual records from within the app, and uninstalling ProofPay removes its local data from your device entirely. See ProofPay Basic Privacy Policy §14 for the full detail.

Encrypted local storage backed by Android Keystore mechanisms, sitting behind PIN or biometric authentication. See the Security category below for the technical detail.

Whoever can unlock the app on your device — that's why PIN/biometric protection exists. Denxor Labs does not have standing access to your locally-stored transaction records.

Transaction records and the pending-message queue use encrypted local storage backed by Android Keystore mechanisms, rather than being stored in plain form.

Your PIN is authenticated using salted PBKDF2‑HMAC‑SHA256 with a high iteration count. Repeated failed attempts trigger escalating lockout behaviour rather than unlimited guesses.

Yes — your device's fingerprint sensor can unlock the app as an alternative to entering your PIN.

ProofPay does not require the SEND_SMS permission and does not send messages on your behalf. It only requests what supported message-parsing actually needs.

A message you share with ProofPay is parsed on-device, queued through an encrypted message queue, and converted into a structured record before being written to storage — so pending data isn't left exposed mid-process. ProofPay doesn't read messages you haven't shared with it.

ProofPay's notification design is intended to reduce exposure of sensitive transaction amounts in notification previews — for example on a lock screen someone else might glance at.

No — and we won't claim that. Security here is engineered into the architecture (PIN hashing, encrypted storage, minimal permissions), but no software system can eliminate every conceivable security risk. See the full Data & Security Policy.

Each ProofPay receipt carries a QR code. Scanning it opens the official Denxor Labs verifier, which checks the receipt's cryptographic signature entirely in the browser and confirms it hasn't been altered — no app, account, or server round-trip required to perform the check. See Verification claims for exactly what that check does and doesn't confirm.

ProofPay recognizes information from supported transaction message formats — it doesn't claim compatibility with every bank, provider, or message format. If a message type isn't recognized yet, sharing it with ProofPay won't produce a usable record.

Camera scans and imported images/PDFs/DOCX files go through a review step before saving specifically so you can correct anything extracted incorrectly — a blurry photo or unusual receipt layout can affect accuracy. Review the extracted details before confirming the save.

Yes — a saved transaction record can be exported as a PDF, which you can share the way you'd share any other file from your device.

Because transaction records are stored locally rather than on a Denxor server, uninstalling ProofPay removes its local data from that device along with it.

Check ProofPay's product page and the Updates destination — ProofPay is in active development, so some capabilities described as upcoming may not be live yet.

Email denxorpraxis@gmail.com or message on WhatsApp with what happened, and which device/version if you have it — reports go straight to the people building the app.