Get the Amount, Recipient, and Transaction Reference from an OPay or PalmPay Screenshot
Manually typing the four fields from an OPay or PalmPay confirmation into a spreadsheet takes 2 minutes per screenshot — this does it in 5 seconds, regardless of which app or transaction type.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Grab from an OPay or PalmPay Confirmation
OPay and PalmPay are Nigeria's two largest fintech apps. With Custom Column Extraction, you name the fields and the AI locates them by meaning.
Formatted as ₦1,500.00 — Naira symbol before the value, comma as thousand separator, period as decimal. The AI reads the ₦ prefix and the numeric value together.
Every Nigerian bank transfer shows the recipient's name, bank, and 10-digit NUBAN. The AI extracts all three as a single field — the bank name is critical because NUBAN alone is not unique across banks.
A long numeric or alphanumeric string (e.g., 231220013036927215 on OPay). This is the primary reconciliation key — it ties a payment to a specific transaction across systems.
Both apps display the transaction timestamp. OPay shows Dec 20, 2023 09:46; PalmPay uses a similar format. The AI normalises it into a consistent date column.
Nigeria's Fintech Giants Don't Use the Same Layout — and Neither Do Their Transactions
OPay started as a super-app (ride-hailing, food delivery, payments) before focusing on fintech. PalmPay built for mobile-first Nigeria from day one. Their screenshots share the same four fields but render them differently — traditional extraction tools built for Western payment apps can't handle the Nigerian ecosystem.
Why OPay & PalmPay Break Traditional Extraction
Two apps, two visual languages. OPay uses a green-themed receipt with a centred layout. PalmPay uses a blue-themed screen with left-aligned fields. Template-based tools that expect a fixed pixel position for "Amount" fail when the app changes.
Super-app blur — not every screen is a payment. OPay's history as a super-app (ORide, OFood, OExpress) means its confirmation screens include ride receipts, food delivery invoices, and loan notices. A regex tool expecting only "Amount + Recipient + Bank" breaks on a ride-hailing receipt.
NUBAN + Bank is the real identifier, not just a name. Nigerian bank transfers display the recipient's 10-digit NUBAN account number and bank name alongside the person's name. Two recipients with the same name but different banks are different people. Traditional extraction that grabs only "Recipient Name" misses the bank + NUBAN context that makes the data useful for reconciliation.
How Semantic Extraction Handles the Nigerian Ecosystem
App-independent field identification. The AI reads the meaning of each visible element, not its pixel position. Whether the Amount label is centred on OPay or left-aligned on PalmPay, the AI identifies it by the ₦ prefix. The same column definition works for both apps.
Transaction-type-aware extraction. The AI reads the screen title to determine the transaction type. A bank transfer shows "Transfer Successful" and includes a NUBAN. An airtime top-up shows a phone number. A bill payment shows the biller name. The same four columns are populated correctly for each type.
NUBAN + Bank extracted as a structured composite. The AI locates the 10-digit NUBAN by its digit pattern, reads the bank name from the adjacent label, and captures the recipient's name. All three are combined into a single Recipient field that uniquely identifies the payee.
"Nigeria's fintech industry processes millions of transactions daily. Many still reconcile them on spreadsheets."
— techsomaafrica on Instagram
From Mixed OPay and PalmPay Screenshots to One Clean Spreadsheet
Upload OPay and PalmPay Screenshots Together
You have a folder of screenshots from the past week: an OPay bank transfer receipt to a supplier, a PalmPay bill payment for electricity, and an OPay airtime top-up confirmation. Three different apps, three different transaction types, three different screen layouts. Upload them all into one batch — JPG, PNG, or WebP screenshots of the confirmation screens.
Define Columns Once — Amount, Recipient, Reference, Date
Type the four columns you need. The AI reads each screenshot independently: it finds the amount by the Naira symbol, extracts the recipient's name + bank + 10-digit NUBAN from the transfer confirmation, locates the long transaction reference string (the reconciliation key), and records the date and time. The same column definition works for OPay, PalmPay, or any Nigerian fintech confirmation.
Get One Unified Table — No Sorting by App
Processing takes 5-10 seconds per screenshot. The output is one XLSX or CSV: three rows, four columns (Amount, Recipient, Transaction Reference, Date), one row per screenshot. The OPay transfer, PalmPay bill payment, and OPay airtime top-up each produced the same clean structure. Roughly 18x faster than opening each screenshot and typing the values by hand (~2 min manual per screenshot vs ~5s here).
What you get — across OPay and PalmPay, all transaction types:
| Amount | Recipient | Transaction Reference | Date |
|---|---|---|---|
| ₦1,500.00 | Chinedu Okonkwo / GTBank / 0123456789 | 231220013036927215 | 20 Dec 2023 |
| ₦5,200.00 | IKEDC / 9876543210 | 000013240712133841000203629444 | 12 Jul 2024 |
| ₦500.00 | MTN Nigeria / 08031234567 | OP240715001234567 | 15 Jul 2024 |
When Screenshot Extraction Works Best — and Its Limits
Understanding the boundaries helps you get consistent results.
When It Works Best
Direct device screenshots of OPay or PalmPay confirmation screens. Full-resolution screenshots achieve up to 99% accuracy. Machine-rendered app text is high-contrast.
Mixed transaction types in a single batch. Bank transfers, airtime top-ups, bill payments, and QR payments can be uploaded together — no need to sort by type or app before processing.
Business reconciliation across multiple channels. If you accept payments via both OPay and PalmPay, batch processing gives you a single spreadsheet with every transaction's reference number for accounting.
When to Be Cautious
Forwarded screenshots through WhatsApp or Messenger. Messaging platforms compress images. Forwarded screenshots may have reduced resolution that affects accuracy for the long transaction reference string.
Architecture boundary: screenshot of the app screen, not direct API access. This tool extracts data from what is visible on the confirmation screen. It cannot pull transaction history directly from OPay's or PalmPay's servers.
USSD-style confirmation screens. Some Nigerian users still receive confirmations via USSD banking codes. These screens have a different visual format (monochrome, simpler layout) and may produce partial results.
Frequently Asked Questions
Can the AI tell the difference between a bank transfer, an airtime top-up, and a loan disbursement in an OPay screenshot?
Yes. The AI reads the screen title and the context of each field. A bank transfer receipt shows a recipient name with a 10-digit NUBAN and bank name. An airtime top-up shows a phone number and network provider (MTN, Glo, Airtel, 9mobile). A loan disbursement shows loan terms, interest rate, and repayment date. The same four columns are populated correctly for each type — the Recipient field will contain the bank details for a transfer, the phone number for an airtime top-up, and the loan reference for a disbursement.
Does the NUBAN account number always have 10 digits for Nigerian bank transfers?
Yes. The Nigeria Uniform Bank Account Number (NUBAN) standard, mandated by the Central Bank of Nigeria, specifies a 10-digit account number for all Nigerian banks. Both OPay and PalmPay display the recipient's 10-digit NUBAN alongside the bank name on every transfer confirmation screen. The Recipient field extracts this number along with the bank name, giving you a complete identifier for each payee.
Can I batch OPay and PalmPay screenshots together in a single upload?
Yes. Define your four columns once — Amount, Recipient, Transaction Reference, Date — and upload OPay and PalmPay screenshots into the same batch. The AI processes each screenshot independently, identifies which app generated it, and extracts the fields. The output is a single spreadsheet with one row per screenshot, regardless of which app or transaction type produced it.
What does the Transaction Reference field look like, and how do I use it for reconciliation?
The Transaction Reference is a long identifier that changes format between apps. On OPay, it is typically a 15-digit numeric string (e.g., 231220013036927215) where the first digits encode the date. On PalmPay, it is a longer alphanumeric string (e.g., 000013240712133841000203629444). This reference is the primary reconciliation key — it is the identifier you use to match a payment against your records, dispute a failed transaction with support, or cross-reference with your bank statement.
Can I extract data from a USSD banking confirmation screenshot too?
USSD banking screens (monochrome confirmations from codes like *737#) have a different format from OPay and PalmPay app screens. The AI can still read the text, but the layout is simpler and some fields (like the recipient's bank name) may not be displayed. The Recipient field may contain less complete data for USSD entries.
See all payment screenshot types supported by this tool, from Venmo and PayPal to M-Pesa and PIX: payment screenshots overview
Another Nigerian payment channel with its own format challenges: Nigerian bank transfer screenshot extraction
Compare with Kenya's mobile-money-first payment system: M-Pesa SMS screenshot extraction