Extract Amount, Transaction ID, and Payment Source from a Paytm Screenshot
Manually typing the amount, 12-14 digit Transaction ID, and payment source from a Paytm confirmation screen into a spreadsheet takes about 90 seconds per screenshot — this picks all four fields in under 10 seconds.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Extract from a Paytm Payment Screen
Paytm's confirmation screen is deceptively simple — three payment sources, a persistent Cashback banner, and two different transaction identifiers depending on whether you sent money to a person or paid a merchant. With Custom Column Extraction, the AI reads the label beside each value so the right data lands in the right column every time.
The Rs figure uses Indian lakh/crore notation (Rs1,00,000 = 1 lakh). The Cashback banner also shows a Rs amount — the AI reads the label context to distinguish the transaction amount from the promotional offer.
A 12-14 digit numeric code for P2P transfers — the key for bank reconciliation. For merchant payments, Paytm also shows an Order ID (a different alphanumeric identifier). The AI identifies each by its label context.
Paytm's "Paid via" field shows whether the transaction was funded by Paytm Wallet (prepaid), UPI (bank-linked), or Paytm Card (postpaid). Each source has a slightly different confirmation layout — the AI reads the source label regardless of which one was used.
Transaction result — "Success", "Pending", or "Failed". Useful for separating confirmed payments from failed attempts before importing into your ledger.
Three Payment Sources, Two Identifiers, and a Cashback Banner That Tricks Dump OCR
Paytm is the only major Indian UPI app that lets you pay from three different sources — and each one draws a slightly different confirmation screen. Meanwhile, a persistent Cashback element sits on the same screen advertising a separate Rs amount that dump-style OCR tools cannot distinguish from the actual transaction.
"I have to extract data from the payment screenshots like GPay, PhonePay, Paytm, etc., and after extracting, I have to make an Excel to store all the details like sender name, date, time, amount, etc. After doing this, I have to match the payment transactions with the bank statement. Is it possible through UiPath Studio? I have tried a lot ... but it is not 100% accurate."
— Keshav, on the UiPath Community Forum, describing the challenge of reconciling Paytm, PhonePe, and GPay screenshots with bank statements
"Paid via" — Three Sources, Three Layouts
Paytm Wallet, UPI, and Paytm Card each show a different confirmation screen. The Wallet screen shows the prepaid balance deduction, the UPI screen shows the bank-linked payment, and the Card screen shows the postpaid credit line. Dump-style OCR treats each as a unique document type — but they are all from the same app.
The Cashback Banner Is Not Part of Your Transaction
Paytm's confirmation screen almost always includes a "Cashback" or "Rewards" section showing a promotional Rs amount — "You earned Rs12 cashback!" or "Get 5% off on your next order." A position-based OCR tool reads every Rs figure on the screen and cannot tell which one is the actual transfer amount.
Transaction ID vs Order ID — Two Different Things
For P2P transfers, Paytm shows a 12-14 digit numeric Transaction ID. For merchant payments, bill payments, and recharges, it shows a separate Order ID (alphanumeric). They serve different purposes — the Transaction ID is the bank-level reference, while the Order ID is Paytm's internal merchant tracking number.
One Column Set, Three Source Types
Define Amount, Transaction ID, Paid Via, and Status — the same four columns work for Wallet, UPI, and Card screenshots. The AI reads the "Paid via" label context to determine which source was used, regardless of layout differences.
Semantic Zones Keep Promotional Content Separate
The AI understands that the "Cashback" section is a separate visual zone with its own heading. Name your column Amount and the AI returns only the value beside the transaction amount label — the Rs12 cashback offer under the rewards heading stays out of the Amount column entirely.
Numeric Transaction ID, Identified by Label Context
Define Transaction ID and Order ID as separate columns. The AI reads the label text — "Transaction ID" for the 12-14 digit numeric P2P code, "Order ID" for the merchant alphanumeric reference. Each value lands in the correct column, and the Indian numbering system (Rs1,00,000) is parsed as a clean numeric value.
From a Paytm Confirmation Screen to a Clean Spreadsheet Row
If you are logging Paytm payments for expense tracking, reconciliation, or shared accounting — here is what happens when you drop a screenshot into the tool.
Upload the Screenshot
Upload a Paytm confirmation screen — a native screenshot from the app, or a photo of the screen if you are working from a second device. Paytm's in-app screenshots are not blocked, so you can capture the full transaction detail card. Whether it is a P2P transfer paid via Wallet, a merchant QR paid via UPI, or a bill payment charged to Paytm Card — all three source types go through the same upload queue.
Name the Columns
Define your column headers: Amount, Transaction ID, Paid Via, Status. The AI reads the label beside each value — the amount sits next to the Rs symbol, Transaction ID sits next to the "Transaction ID" label, and the payment source appears under "Paid via". If you want to track the Order ID for merchant payments separately, add a fifth column — the AI distinguishes it from the Transaction ID by label context. Add a Computed Column — Cashback Earned (Read Promotional Section) — to optionally capture the rewards amount.
Export the Row
The output lands as a single spreadsheet row — amount, Transaction ID, payment source, and status. Export to Excel, CSV, or push directly into Google Sheets via the add-on. One screenshot becomes one row, each field in its correct column, with the Indian numbering parsed correctly for Excel calculations. Process multiple Paytm screenshots — or mix them with PhonePe and GPay — in a single batch.
When Paytm Screenshot Extraction Works Best — and When It Does Not
When It Works Best
Clear transaction confirmation screens. The payment success page shows all four fields in high-contrast machine-rendered text — the amount, 12-14 digit Transaction ID, the "Paid via" source indicator, and the Success status.
Batch cross-platform processing. One column set extracts from Paytm alongside PhonePe and Google Pay India — all rows merge into one spreadsheet with consistent headers. The "Paid via" column captures the app-specific source automatically.
Reconciliation and expense tracking. The 12-14 digit Transaction ID is the key across the NPCI network — matching Paytm screenshots against bank statements becomes a straightforward VLOOKUP on the Transaction ID column. The "Paid via" field tells you which source funded each transaction.
When to Be Cautious
Screenshots from older Paytm app versions. Paytm has redesigned its confirmation screen layout multiple times — the "Paid via" label moved from the top to the bottom in a 2024 update. Semantic extraction handles layout changes, but very old screenshots may reduce accuracy.
Screenshots forwarded through messaging apps. WhatsApp and Telegram compress images, which can blur the smaller 12-14 digit Transaction ID at the bottom of the screen. Use the original screenshot from the Paytm app when possible.
Pending or failed transactions. A pending payment may show a "Processing..." status with provisional amounts. Confirm the Status shows "Success" before relying on the data for reconciliation.
Frequently Asked Questions
How do I extract the amount from a Paytm screenshot without also capturing the Cashback offer?
Define a column called Amount and the AI reads only the value beside the "Amount" or "Rs" label. Paytm's Cashback banner appears in a separate visual section with its own heading — the AI treats it as a different zone and ignores it for the Amount column. If you want to capture the cashback separately, define a second column called Cashback — the AI reads the rewards section as a separate field without mixing it with the transaction amount.
What is the difference between the Transaction ID and the Order ID on a Paytm screenshot — which one do I use for reconciliation?
Paytm shows two different identifiers depending on the transaction type. The Transaction ID is a 12-14 digit numeric code used for person-to-person (P2P) transfers — this is the correct reference for bank reconciliation. The Order ID is a separate alphanumeric identifier shown for merchant payments, bill payments, and recharges — it is Paytm's internal tracking number, not a bank-level reference. Define both columns (Transaction ID and Order ID) and the AI places each value in its correct column based on the label context. For disputes, use the Transaction ID or the UPI Reference Number visible in the transaction details.
Can I extract data from Paytm Wallet, UPI, and Card payment screenshots using the same column set?
Yes. Paytm shows a "Paid via" field on the confirmation screen that indicates whether the transaction was funded by Paytm Wallet (prepaid balance), UPI (linked bank account), or Paytm Card (postpaid credit). Each payment source has a slightly different layout — the Wallet screen shows the balance deduction, the UPI screen shows the bank-linked transaction, and the Card screen shows the credit line. The core fields — Amount, Transaction ID, Status, and Paid via — are present on all three. Define one column set and the AI extracts from all three source types in a single batch.
The amount on my Paytm screenshot shows Rs 1,00,000 — will the AI read it correctly as 1 lakh rupees?
Yes. The AI understands Indian numbering notation — Rs 1,00,000 is interpreted as 100,000 (one lakh), not 10,000. The Indian comma system places the first comma after the hundreds (1,00,000) rather than after the thousands (100,000). The AI reads the numeric value of the amount, not the comma positions, so the output preserves the correct number for Excel calculations. No manual correction needed.
Can I batch Paytm screenshots with PhonePe and Google Pay India screenshots in the same export?
Yes. Define one set of column names — Amount, Transaction ID, Paid Via, Status — and the AI processes Paytm, PhonePe, and Google Pay India screenshots in a single batch using the same definitions. Each app's confirmation screen looks different, but the underlying UPI fields are the same. See the payment screenshots overview for the full cross-app capability.
Compare with another Indian UPI leader: PhonePe screenshot extraction — the 12-digit UPI Ref No handled the same way
Also from this Hub: Google Pay India screenshot extraction — GPay's alphanumeric UPI Transaction ID vs Paytm's numeric one
Back to payment screenshots overview — see all supported payment apps