Handle payment-processor prefixes with * separators to extract the true merchant name
F
Francisco Noriega
In Mexico (and likely other markets), most non-bank card terminals — MercadoPago, Clip, NetPay, BBVA/BPK, Z-Tech, etc. — post transactions as a processor prefix + * + the actual merchant name.
Lunch Money currently takes the first segment (the processor code) as the merchant, which is wrong. This also poisons auto-categorization: e.g. in one occation BPK* was parsed as "BP" and the transaction got categorized as a gas station, when the real merchant is 33CLUB REF (an bike-parts shop).
Real examples
Real world examples:
CLIP*MXLONCHES LEO -> Lonches Leo
NETPAY*BERNYS -> Berny's
BPK*33CLUBREF -> Club 33 Refacciones
ZTL*NAUNRODRIGOJUAREZG -> Naun Rodrigo Juarez
MERPAGO*TUKTUKTHAI -> Tuk Tuk Thai
Built-in recognition of common processors (CLIP, MERPAGO, NETPAY, BPK, ZTL, etc.), taking the text after the asterisk as the payee.
A generic "use the text after the asterisk" fallback for unknown prefixes.
At minimum, expose this in rules (for example a regex or "extract text after *" action) so users can build it themselves per prefix.
This matters because it produces correct, readable merchant names and, more importantly, lets the category engine see the real merchant instead of a misleading processor code. It affects the majority of small-business card payments in Mexico, so the impact is broad.
Log In