Identify Amount, UPI Transaction ID, and Note from Any Google Pay India Screenshot
Manually typing GPay confirmation data — amount, UPI Transaction ID, UPI ID, and the free-text note — takes roughly 90 seconds per screenshot. This extracts all four fields from any GPay screen in 5 seconds.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Extract from a Google Pay India Screenshot
GPay's dark purple theme with its white confirmation card stacks fields in a fixed visual hierarchy — but the real challenge is knowing which value means what. Name the columns you want, and the AI locates each field by understanding its semantic role, not its pixel position.
The large Rupee figure in the centre of the confirmation card. GPay uses Indian numbering — ₹1,50,000 (1.5 lakh) — which basic OCR tools often misread as separate values.
The 12-character alphanumeric code at the bottom of the screen. This is the primary reconciliation key — it ties a screenshot to a bank statement line. PhonePe uses 12 digits; GPay mixes letters and numbers.
The payment handle (e.g., name@okhdfcbank, name@oksbi). The suffix reveals the recipient's bank — useful for reconciling across multiple accounts or verifying that funds went to the right institution.
GPay's free-text description field carries the real transaction purpose — "rent", "lunch split", "EMI for bike", "college fee". For Indian users tracking expenses across categories, this is the most valuable field on the screen.
Why GPay's Confirmation Screen Is Trickier Than It Looks
The white card on dark purple background looks clean, but three things make it harder to extract than a standard receipt.
"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 GPay screenshots with bank statements
The cash jar is decorative — but basic OCR treats it as data
GPay's success screen shows a distinctive coin-jar animation that fills with coins on a successful transaction. It's purely visual, but position-based OCR tools try to read text from that region, generating garbage output that pollutes the extraction.
Indian numbering breaks comma-separated value parsers
"₹1,50,000" is 1.5 lakh — but a standard CSV parser or regex tool sees three separate number groups. The AI understands the Indian grouping convention and extracts the full value as a single field, not three fragments.
UPI terminology is invisible to generic OCR
A tool that doesn't know what "UPI Transaction ID" or "UPI ID" means can't distinguish between them. Both appear as alphanumeric strings on the same screen — one is a transaction-level key, the other is a bank-linked handle. The AI understands the semantic difference.
Semantic extraction ignores decoration, reads data
Custom Column Extraction identifies text by its meaning, not its location. The cash jar animation is invisible to the AI — it reads the Amount, UPI ID, Transaction ID, and Note fields from the text that actually carries information, skipping the decorative elements entirely.
Indian number formats are parsed as a single value
The AI recognises the Indian numbering convention natively. "₹1,50,000" is extracted as one amount field — not as "₹1", "50", "000". You can also define a Computed Column to normalise the output to a standard numeric format during extraction.
UPI ID and Transaction ID are identified by role
Define columns called "UPI ID" and "UPI Transaction ID" — the AI reads the confirmation screen, recognises which handle is the bank-linked UPI ID and which code is the unique transaction identifier, and places each in the correct column. No manual labelling required.
A Folder of GPay Confirmations vs One Batch
Open the screenshot. The amount is the large Rupee figure — but it says "₹1,50,000" and you have to decide whether to type it as "150000" or "1,50,000". The UPI Transaction ID at the bottom is a 12-character alphanumeric string — "T2206ABCXYZ" — easy to mistype. The UPI ID says "user@okhdfcbank" — which bank is that? And the Note field says "rent for July" — do you need that for your records? Each screenshot takes about 90 seconds of reading, deciding, and typing. A month of GPay payments adds up fast.
Upload all GPay screenshots into one batch. Type four column names: Amount, UPI Transaction ID, UPI ID, Note. The AI reads every screenshot at once — it identifies the large Rupee figure as the Amount, extracts the 12-character alphanumeric Transaction ID from the bottom of the card, captures the UPI handle with its bank suffix, and pulls the free-text note. Five seconds per screenshot. The output is a single XLSX — one row per payment, ready for bank reconciliation.
When It Works Best — and When to Be Cautious
Understanding these boundaries helps you get the best results from GPay India screenshots.
When It Works Best
Direct device screenshots from the GPay app. Machine-rendered white text on dark purple has excellent contrast — up to 99% accuracy on printed Rupee values and labels.
GPay's consistent white-card layout. The confirmation card always follows the same visual hierarchy: amount at top, UPI ID below, then Note, with Transaction ID at the bottom. The AI identifies fields by their semantic relationship, not pixel position.
Batch processing across UPI payment apps. One column set handles GPay alongside PhonePe, Paytm, and BHIM UPI in the same batch — everything merges into one spreadsheet.
When to Be Cautious
Compressed screenshots forwarded through messaging apps. GPay's card text is machine-rendered, but heavy compression can blur smaller elements like the UPI Transaction ID at the bottom of the card.
Low screen brightness capture. GPay's dark purple theme already reduces contrast — dim screenshots produce weaker results. Bump brightness before capturing.
Handwritten notes or edited captions. GPay's Note field is typed text — it's machine-rendered and readable. However, if the screenshot captures a hand-filled cheque or a handwritten caption added after the fact, the AI may not recognise it.
Frequently Asked Questions
Can I extract both the UPI ID and the UPI Transaction ID from one GPay screenshot?
Yes. Define columns for both "UPI ID" and "UPI Transaction ID" in the same column set. The UPI ID appears on the confirmation as the payment handle (e.g., name@okhdfcbank), and the UPI Transaction ID is the 12-character alphanumeric code at the bottom of the screen. The AI identifies each by its semantic role, not its position, so you get both fields in the same row without conflict.
How does the tool handle Indian numbering like ₹1,50,000 (1.5 lakh)?
The AI reads the Rupee value as displayed, including Indian-standard grouping with commas at the thousand/lakh/crore positions. A value displayed as ₹1,50,000 is extracted exactly as shown. You can then convert it to a standard numeric format in Excel, or use a Computed Column to normalise the output during extraction by defining a column like "Amount (Normalised)" with a rule to strip commas and convert to a plain number.
The cash jar animation on the GPay success screen — does it interfere with extraction?
No. The coin-jar animation is a purely visual element — it doesn't contain text. Position-based OCR tools sometimes try to read the area around it and generate garbage output, but Custom Column Extraction identifies fields by their semantic meaning. The AI reads the Amount, UPI ID, Transaction ID, and Note fields from the actual text on the white confirmation card, completely ignoring the decorative jar.
Can I process multiple GPay screenshots in one batch to get a consolidated UPI payments log?
Yes. Upload all GPay screenshots — or mix them with PhonePe, Paytm, and BHIM UPI screenshots — into a single batch. Define the same column set once, and the AI processes every screenshot in the queue. The output is one unified Excel file with each row representing one payment, regardless of which UPI app the screenshot came from.
What's the difference between the UPI Transaction ID and the UPI ID — which one do I use for bank reconciliation?
The UPI ID (e.g., user@oksbi) is the payment handle linked to the recipient's bank account. The "oksbi" suffix tells you the bank is State Bank of India. The UPI Transaction ID is a unique 12-character alphanumeric code assigned to each individual transaction. For bank reconciliation, the UPI Transaction ID is the primary key — it's unique per transaction and appears in your bank statement's UTR field. The UPI ID tells you who received the payment and at which bank.
From the parent Hub: Extract data from any payment screenshot — PhonePe, Paytm, GPay, and more
Also from this Hub: PhonePe screenshot field guide · Paytm screenshot field guide