Identify Transfer Amount (송금액), Korean Addresses & Chat Metadata from a KakaoTalk Screenshot
Identify 8 fields from a single KakaoTalk screenshot — transfer amount (송금액), bank account (계좌번호), Korean address in either address system, plus sender and chat metadata — in 5-10 seconds per image.
5-10s per screenshot · Up to 99% accuracy on printed text
Two Layers of Data in Every KakaoTalk Chat
Custom Column Extraction reads both message content and chat-native metadata from each screenshot by meaning, not position.
Content (메시지 내용)
₩ amounts like "50,000원" on a KakaoPay card or chat message — the AI reads the ₩/원 marker.
Order reference numbers shared in chat — identified by "주문번호" labels or sequential patterns.
Both 도로명주소 (road name: 테헤란로 123) and 지번주소 (land lot: 역삼동 123-45) by structural markers.
"국민은행 123456-78-901234" — bank name (은행명) plus hyphenated account number (계좌번호).
The memo below a KakaoPay transfer — an order reference, product name, or "입금 확인".
Native Metadata (App UI 속성)
The contact name from KakaoTalk's chat sender label.
Date and time from the message header, captured as displayed.
Labels each element as 송금카드, 텍스트, or 주소 for spreadsheet filtering.
Why a KakaoTalk Screenshot Requires More Than OCR
South Korea's dual address system means a customer's address in KakaoTalk might be written as road name (도로명주소) or land lot (지번주소) — and a KakaoPay payment card alongside it uses a completely different visual format. Traditional OCR flattens them all into one text stream.
"I really want to move over my KakaoTalk chatrooms/messages onto my new phone, but the app only has an option to export them into a text file."
— r/AndroidQuestions
Two Address Systems, No Warning
도로명주소 (road name: "테헤란로 123") and 지번주소 (land lot: "역삼동 123-45") are structurally different — one uses street-plus-building-number, the other uses dong-plus-parcel-number. Both formats appear in KakaoTalk daily. A template configured for one will miss the other.
KakaoPay Cards Mix With Chat Bubbles
A KakaoPay confirmation is a styled in-chat card with a green accent — the amount in bold, the merchant name, and "결제완료" status. It sits between regular chat bubbles. Traditional OCR outputs the card's ₩50,000 and the neighbor sticker caption in the same text dump.
Korean Banking Patterns Are Not Generic Digits
"국민은행 123456-78-901234" follows a Korean banking convention — bank name in Hangul, then a hyphenated account number with a bank-specific segment count. Traditional OCR treats the entire string as undifferentiated Korean text, missing the structured relationship between 은행명 and 계좌번호.
Recognizes Both Address Systems by Structure
The AI anchors on Korean administrative markers — the 시/군/구 suffix frames the city and district, 로/gil signals the road name system, 동/dong marks the land lot system. Whether the customer writes 테헤란로 123 or 역삼동 123-45, the address routes to your 주소 column without you choosing a format.
Classifies Each Visual Component by Role
The green-accented rectangle is recognized as a KakaoPay payment confirmation — the ₩50,000 goes into 송금액, the merchant name stays separate. Chat bubbles above and below are read for 주소, 주문번호, and 은행계좌. The sticker or KakaoMap card is excluded as non-data.
One Column Set for All KakaoTalk Messages
Define your eight columns once — 송금액, 주문번호, 주소, 은행계좌, 메모, 보낸사람, 시간, 메시지유형 — and process KakaoPay cards, address messages, and bank account texts in the same batch. The AI reads field meaning independently of format.
From a KakaoTalk Screenshot to One Structured Row
Whether you are logging KakaoPay transfers from freelancers, compiling Korean delivery addresses from order chats, or recording bank accounts sent by customers — the process is three steps with one set of column names.
Upload the KakaoTalk Screenshots
A KakaoPay transfer card, a customer's address message, a bank account text — all in one batch. PNG or JPG, whatever your phone saved them as. No need to sort by message type before uploading. The AI reads the visual structure of each element independently, whether it's a styled card or plain chat text.
Name Your Columns Once
Type 송금액, 주문번호, 주소, 은행계좌, 메모, 보낸사람, 시간, 메시지유형. The AI reads each screenshot individually — the KakaoPay card fills 송금액 and 메모, an address message fills 주소 in whichever format it was written, and 보낸사람 and 시간 populate from KakaoTalk's UI chrome across all message types. Inferred columns can automatically categorize 주소 as 도로명 or 지번 type.
Export a Unified Spreadsheet
Every screenshot becomes one row. Payment screenshots have 송금액, 은행계좌, 보낸사람, and 시간; address screenshots have the full 주소 in the customer's format plus sender metadata. All in one .xlsx file, ready to sort by sender or timestamp without reopening a single screenshot.
KakaoTalk Data Extraction — What Works and What Doesn't
KakaoPay styled cards and Korean addresses extract reliably. Two scenarios benefit from extra attention before uploading.
- ✓ KakaoPay opened payment cards — the green-accented card with amount, merchant, and "결제완료" status — extract reliably because the visual structure is consistent regardless of chat context.
- ✓ Korean addresses with either address system — the AI detects 도로명 markers (로/gil) and 지번 markers (동/dong) and routes both to the 주소 column.
- ✓ Batches mixing KakaoPay cards, address messages, and bank account texts — one column set works across all formats.
- ⚠ A KakaoPay card that was not fully opened (showing only the sender notification) will not display the amount or merchant. Open the payment card fully before screenshotting.
- ⚠ Heavily compressed screenshots — common when KakaoTalk images are forwarded or saved from chat backups — can reduce Hangul recognition accuracy. Screenshot the original conversation for best results.
Frequently Asked Questions About KakaoTalk Data Extraction
Can the AI read a Korean bank account number (계좌번호) from a KakaoTalk chat message even if the sender typed it without hyphens?
Yes. Korean bank account numbers typically follow patterns like "123456-78-901234" with hyphens, but even without explicit separators, the AI recognizes the 은행명-bank name prefix (e.g. 국민은행, 신한은행, 우리은행) and the expected digit sequence length for Korean 계좌번호. If the account number was typed without delimiters, it still gets identified as a banking pattern and routed to your 은행계좌 column.
A customer sent their address in KakaoTalk using only the land lot system (지번주소) — "서울시 강남구 역삼동 123-45". Can the AI still extract it alongside a message that uses road name format (도로명주소) from another customer in the same batch?
Yes. The AI recognizes both formats by their structural signatures. A 도로명주소 like 테헤란로 123 is anchored by the 로/gil road suffix. A 지번주소 like 역삼동 123-45 is identified by the 동 (dong) neighborhood unit and the hyphenated lot number pattern. Both are extracted into the same 주소 column — you don't need to specify which system a customer will use.
I have a single KakaoTalk screenshot with both a KakaoPay card (showing 송금액) and a text message containing the customer's address — can I extract both in one pass?
Yes. Define both content columns (송금액, 주소) in the same column set. The AI reads the KakaoPay card as a styled payment component, extracting the transfer amount, while separately reading the chat bubble for the address. The sender name (보낸사람) and timestamp (시간) populate from chat-native metadata in the same row — so one screenshot yields one complete record with payment, address, and sender information.
A KakaoTalk screenshot shows a KakaoMap shared location card — does the AI extract the address from the map preview card itself?
The KakaoMap location card displays a map thumbnail with the address and place name below it. The AI reads the text overlay on the card — the address label and the place name — and can extract them if you define a 주소 column. However, the accuracy depends on how much of the address text is rendered clearly in the preview card. For complete address data, a text message with the full address yields better results than a map thumbnail.
I get multiple KakaoTalk payment screenshots from different senders — can I batch-extract every 송금액 and sender name into one table sorted by date?
Upload all screenshots at once — the AI processes them in a single batch and outputs one row per screenshot. Define 송금액, 보낸사람, and 시간 as columns and every KakaoPay card or transfer message in the batch populates the corresponding fields. The exported Excel file can then be sorted by the 시간 timestamp column to organize payments chronologically across all senders.