DEV Community

Cover image for Binance P2P Order History Fetcher with Full Name — Why I Built It (and Why Binance Export Is Useless for Accounting)
PyDev
PyDev

Posted on

Binance P2P Order History Fetcher with Full Name — Why I Built It (and Why Binance Export Is Useless for Accounting)

How it started

A while ago I ran into a very practical problem.

I was working with P2P transactions on Binance and needed to prepare reports — not for myself, but for accounting.

At first I thought:

“Okay, Binance already has export. This should be easy.”

So I downloaded the P2P order history.

And… that’s where the problem started.

The moment I realized something is wrong

The export looked fine at first glance.

But then I noticed something critical:

👉 All names and surnames were hidden ().*

And that completely breaks everything.

Because for accounting, compliance, or any kind of reporting —

you NEED full names of counterparties.

Without that:

  • you can’t validate transactions
  • you can’t build proper reports
  • you can’t submit documents

Basically, the export becomes useless.

If you’ve ever tried to use Binance export for accounting — you already know the pain.

I ended up building a tool that actually solves this problem:

👉 https://py-dev.top/application-software/binance-p2p-order-history-fetcher-with-full-name

“But Binance gives it for free…”

Yes, Binance does provide a free export.

But let’s be honest:

👉 It’s not usable for any serious purpose.

The data is:

  • incomplete
  • anonymized
  • not suitable for accounting
  • impossible to properly process

It’s more like a viewer, not a real export.

And this is not a bug — it’s intentional.

Binance simply does not expose full names in their export.

The idea: what if I just automate it?

At that point I thought:

“Okay, I’ll just write a small script to fix this.”

Spoiler:

👉 It was NOT a small script.

The reality of building this tool

What seems simple at first actually involves:

  • working around Binance API limitations
  • handling authentication and requests properly
  • collecting full order data (not partial)
  • extracting real *full names instead of **
  • structuring everything correctly
  • exporting clean Excel reports

And most importantly — making it stable, not something that breaks after 2 runs.

That’s how Binance P2P Order History Fetcher with Full Name was created.

What the tool actually does

This is a Python-based tool that:

✔ fetches complete P2P order history

✔ retrieves full names and surnames (no masking)

✔ exports everything into a clean Excel file

✔ works for:

  • full year
  • specific months

What data you get

The generated Excel file includes:

  • orderNumber — order ID
  • advNo — advertisement ID
  • tradeType — buy/sell
  • asset — crypto (USDT, BTC, etc.)
  • fiat — fiat currency (USD, EUR…)
  • amount — crypto amount
  • totalPrice — total fiat value
  • unitPrice — price per unit
  • orderStatus — status
  • commission — fees
  • takerAmount — final crypto amount
  • payMethodName — payment method
  • Match time (UTC) — timestamp

And the most important part:

👉 Full Name (e.g., John Smith)

Why this actually matters

Let’s be clear.

Without full names:

  • reports are incomplete
  • accounting becomes manual hell
  • audits become risky

With full names:

  • you can generate real reports
  • you can use the data in accounting systems
  • you can actually TRUST your export

“It’s just a script, why is it paid?”

I literally got this comment yesterday:

“Binance gives it for free, this isn’t worth the money.”

Here’s the honest answer:

👉 If you think it’s “just a script” — try to build it.

Deal with:

  • API quirks
  • missing fields
  • hidden data
  • pagination
  • data consistency
  • Excel formatting

Then come back and say it’s “free”.

Because the real value here is not the code itself —

👉 it’s solving a problem Binance doesn’t solve.

Installation (quick overview)

  1. Install Python

    👉 https://py-dev.top/installing-python

  2. Extract the archive to C:\

  3. Open config.ini and configure parameters

  4. Run start-the-program.bat

Final thoughts

Binance export is “free”.

But in reality:

👉 it’s incomplete and unusable for real workflows.

If you only need to “look at history” — it’s fine.

If you need:

  • accounting
  • reporting
  • real data

Then you need something more.

That’s exactly why I built this tool.

Top comments (1)

Collapse
 
pydevtop profile image
PyDev •

One thing that surprised me while building this:

Most people don’t realize how limited Binance export actually is until they try to use it for real accounting.

It looks fine… until you actually need full data.

That’s where everything breaks.