Skip to main content

purchase-history-parsers

Parse store purchase histories into plain Python records: what you bought, when, for how much, and how you paid, going as far back as each store's own history.

Part of infinparse. Each parser takes one file you exported from your own account and returns a list of Purchase dataclasses. No parser logs in or makes network calls. For stores with no export button, the browser exporters produce the file from your own logged-in browser session.

Supported stores

Store File you need How to get it Parser Runbook
Steam purchase-history page, saved as HTML exporter steam docs/sources/steam.md
Google Play order-history page, saved as HTML exporter google_play docs/sources/google_play.md
Humble Bundle humble-orders.PERSONAL.json exporter humble docs/sources/humble.md
Blinkit blinkit-orders.PERSONAL.json exporter blinkit docs/sources/blinkit.md
Amazon Your Orders.zip Amazon's data request amazon docs/sources/amazon.md
PlayStation Store receipt email saved as .html your mail client playstation docs/sources/playstation.md

Any currency works; each row keeps the currency the store shows. Some parsers expect English-language pages; see each runbook.

Install and use

pip install purchase-history-parsers

One dependency: Beautiful Soup, for reading saved HTML pages.

from purchase_history_parsers import parser

rows = parser("steam").parse("steam-purchase-history.PERSONAL.html")   # list[Purchase]

parser("mypkg.mystore") loads your own parser by dotted path, so you don't need a fork.

Exporters

The exporters are small JavaScript files that run in your browser, on the store's own page, while you're logged in. Each loads your full history and downloads the file the matching parser reads. Install one in a userscript manager (Tampermonkey, Violentmonkey) to get an "Export" button on the page, or paste it into the browser's developer console to run it once. Your password never touches this package, and the Python parsers never go online.

What an exporter saves is only what its parser reads: the history rows, with no page scripts, session data, account email or profile. It is still your purchase history, so the file name says PERSONAL and the page carries a banner. Keep it private: never attach it to an issue. To report a parsing problem, describe the layout or share masked structure instead.

The model

Purchase

Field Type Meaning
store str steam, amazon, ...
order_id str the store's id (or a stable hash when the store shows none)
date date order date
items str item names joined with |
kind str purchase, refund, market or other
amount Decimal + spent, − returned, in currency
currency str INR, USD, ...
payment str payment method as the store shows it
original_amount Decimal | None pre-discount price, if shown
charged Decimal | None part paid from a real account (0 if store credit paid it all; None = all of amount)
refunded bool the store marks the order refunded
raw_type str the store's own type or status text

Licence

MIT. See LICENSE.

Metadata

Release files for purchase-history-parsers 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for purchase-history-parsers 0.1.1
File Size Uploaded Provenance
purchase_history_parsers-0.1.1.tar.gz 8.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for purchase-history-parsers 0.1.1
File Interpreter ABI Platform
purchase_history_parsers-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 20.2 kB

Release files / purchase_history_parsers-0.1.1.tar.gz

Download URL purchase_history_parsers-0.1.1.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
4e9653ea38da787f7daeaaffc6dca583220b7fa2cfaf251e2b636adaee40481e
BLAKE2b-256 checksum
How to use checksums
73e7a27c7c14c3ec2b90e41217c48b562d73392d6d676b509d638e67efbefeb8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Release files / purchase_history_parsers-0.1.1-py3-none-any.whl

Download URL purchase_history_parsers-0.1.1-py3-none-any.whl
Size 11.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
be5f21a3088f172e63d3ed9cc2383c70a2bdea1693d3c8a5438d35360139baac
BLAKE2b-256 checksum
How to use checksums
4037913a93b9c2523a8c3b3ecff36373d3d78bad40a6ae81a9f4214fa45ae086
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Security for purchase-history-parsers 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for purchase_history_parsers-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page