Skip to content
Ratomir Jovanovic edited this page Oct 26, 2026 · 3 revisions

PandaPayLens Wiki

PandaPayLens is an open-source, local-first tool that explains payment errors and puts payment events on a timeline. You paste an API response, a webhook, a postback or a log export, and it tells you what the provider reported, what the code means, which events belong together and what looks wrong.

Play the 60 second PandaPayLens demo video

What it does

Question you have What PandaPayLens shows
"What does this decline or error code mean?" Decoded error with category, next step, retry guidance and a doc link
"Which provider and format is this payload?" Structural detection with a confidence score and the reasons for it
"In what order did things really happen?" A timeline by event time and by arrival order, with filters
"Are these webhooks about the same payment?" Correlation by explicit identifiers only, never by guesswork
"Is something wrong in this flow?" Deterministic findings: duplicates, failed rebills, chargebacks, etc.
"Can I share this with a colleague or vendor?" JSON, Markdown and PNG exports with identifiers masked by default

What it does not do

  • It does not call any payment provider and needs no API keys.
  • It does not store or upload what you paste. Analysis runs in your browser (or locally in the CLI).
  • It does not verify webhook signatures. Pasted webhooks are always treated as unverified.
  • It does not confirm settlement or tell you whether money actually moved. It describes only the records you supplied.
  • It is not a merchant account, referral or underwriting service, and listing a provider implies no partnership.

Start here

  1. Getting Started: use the demo, run it locally or install the CLI.
  2. How Analysis Works: the pipeline from raw text to findings.
  3. Input Formats: what you can paste and the size limits.
  4. Error Decoding: categories, retry guidance and confidence levels.
  5. Timeline and Correlation: how events are ordered and grouped.
  6. Diagnostic Rules: every rule and what triggers it.
  7. Providers and Capabilities: which providers can be analyzed and how well.
  8. High-Risk Providers: subscriptions, payouts, wallets and regulated sectors.
  9. Privacy and Security: redaction, masking, limits and the threat model.
  10. Command Line Interface, Exports and Reports, Self-Hosting.
  11. Contributing, FAQ and the Glossary.

Project status

Releases and their contents are listed in the changelog and on the changelog page. The current number of analyzable providers is always shown on the providers page.

Clone this wiki locally