<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vinska Andrias on Medium]]></title>
        <description><![CDATA[Stories by Vinska Andrias on Medium]]></description>
        <link>https://medium.com/@vinskataniaandrias?source=rss-c8599f79068c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*S4qtvVdZMwZAd_kld3rQOA.jpeg</url>
            <title>Stories by Vinska Andrias on Medium</title>
            <link>https://medium.com/@vinskataniaandrias?source=rss-c8599f79068c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:43:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinskataniaandrias/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How precise UX copy in fintech can prevent fraud]]></title>
            <link>https://medium.com/@vinskataniaandrias/how-precise-ux-copy-in-fintech-can-prevent-fraud-15bfd2764647?source=rss-c8599f79068c------2</link>
            <guid isPermaLink="false">https://medium.com/p/15bfd2764647</guid>
            <category><![CDATA[banking-products]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[product-copywriting]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Vinska Andrias]]></dc:creator>
            <pubDate>Sun, 04 Oct 2026 10:04:24 GMT</pubDate>
            <atom:updated>2026-10-04T12:45:10.868Z</atom:updated>
            <content:encoded><![CDATA[<h4>Lessons from naming QRIS features in Indonesia, where an unclear word once caused real scams.</h4><p>In Indonesia, QRIS (Quick Response Code Indonesian Standard) is now everywhere for cashless payments. People usually think QRIS is just for scanning to pay, but it actually covers more flows.</p><p>That’s where one small detail in the copy ended up causing scams.</p><p>Some leading apps label the feature where <em>users show their QR code to pay at merchants</em> as “Payment”. That creates a dangerous grey area: <em>who is actually paying whom?</em></p><p>Fraudsters exploit the confusion by asking victims to show their QR code as if it will be scanned and they’ll receive money, when in fact it triggers a payment out of the victim’s account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*O2seObtV4A3nhD0RK4Z47w.png" /></figure><h3>Our understanding of QRIS</h3><p>When I first worked on QRIS copy in SimobiPlus (Bank Sinarmas digital banking app) back in 2022, I didn’t realize how tricky it could get.</p><p>Before we get into naming, we need to understand what QRIS actually covers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bGoM1g99NFoCaex_.jpg" /><figcaption><a href="https://www.jaringanprima.co.id/id/qris-dari-masa-ke-masa-evolusi-pembayaran-dari-satu-kode-qr">[Photo Source]</a></figcaption></figure><p><strong>Most people think QRIS means scanning to pay, </strong>but Bank Indonesia defines two models (keep these in mind; I’ll frequently mention them later):</p><ul><li><strong>Merchant Presented Mode (MPM):</strong> the merchant shows a QR code, the customer scans it. This can be static (a sticker, amount filled by customer) or dynamic (merchant’s device shows the exact amount).</li><li><strong>Consumer Presented Mode (CPM):</strong> the customer shows their code, the merchant scans it. Usually for speed, like transport or retail.</li></ul><p>On top of these, in 2023 Bank Indonesia introduced <strong>QRIS TUNTAS </strong>(cash withdrawal, transfer, and deposit), which extended QRIS beyond retail payments.</p><p>Not all banks support every QRIS flow. Some only offer MPM scan-to-pay, while others include CPM or TUNTAS. That difference matters because all these flows technically end in “payment”, but the directions are completely different.</p><p>That’s exactly where copy gets tricky.</p><h3>Early approach: designing the QRIS experience (2022–2023)</h3><p><strong>When we revamped the QRIS page in SimobiPlus, we also had to include QRIS TUNTAS.</strong> It was still super new, and no other bank had rolled it out yet, so there was literally no design best practice (let alone feature naming) to benchmark from.</p><p>As for QRIS MPM and CPM, we could peek at how others named them. Some banks even went with BI’s official terms as-is (never in our wildest thought to adapt that approach, for obvious reasons: it felt odd, not user-friendly, and nothing like how people actually talk).</p><p><strong>This was also the part when content design mattered, because it wasn’t just about picking words. </strong>We had to make all the QRIS features live together on one page in a way that made sense. Otherwise, labels would look like random features dumped into the UI.</p><p>Our first approach was straightforward: <strong>we</strong> <strong>clustered QRIS features by their inherent function, </strong>either <em>scanning</em> or <em>generating</em>. It kept things simple for users and clean in the UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*9hWNlvVMhLQNr1RLVPtU6w.png" /><figcaption>The storyline goes like this when we decided to cluster QRIS features by their inherent function, either <em>scanning</em> or <em>generating QR code</em>.</figcaption></figure><p>Shoutout to OCTO by CIMB Niaga. We liked how <strong>OCTO</strong> approached grouping: they told a mini “storyline” on the page. That way, it created a logical flow users could follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*ZGb4rg8R2YhUBpBM-7Ss_g.png" /><figcaption>Loved how OCTO by CIMB Niaga (left) emphasized storyline. Meanwhile, myBCA (right) took a grouping approach too, with “Tampilkan QRIS” as separator copy.</figcaption></figure><h3>The QRIS Tap disruption (mid-2024)</h3><p>Then came <strong>QRIS Tap</strong>. A branded feature, NFC-based, and pushed heavily by Bank Indonesia. Unlike the earlier code-based QRIS, QRIS Tap lets users simply move their phone closer to a reader to make payments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/0*lKz8OhuTeL3Yi0dO" /><figcaption><a href="https://www.youtube.com/watch?v=S1ocU-NPwNs">[Source]</a></figcaption></figure><p>As a branded feature, it needed to be highlighted, which instantly challenged the naming system we had in place.</p><p>With a launch deadline, we made a quick fix:</p><ul><li>Dropped QRIS Tap into the page <strong>as-is</strong> (because branding speaks for itself)</li><li>Adjusted the body copy from <strong>“Or generate your QR code”</strong> → <strong>“Or select other QRIS transaction” </strong>(because Tap isn’t generating anything, it’s simply NFC-based)</li></ul><p>We realized it was a patchwork solution. We knew we’d revisit it later for a proper naming iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*NHZRJ8XkosKBmscL9jfifQ.png" /><figcaption>Adjusted the body copy from <strong>“Or generate your QR code”</strong> → <strong>“Or select other QRIS transaction” </strong>(because Tap isn’t generating anything, it’s simply NFC-based)</figcaption></figure><h3>Why naming became critical again</h3><p>The real push came when SimobiPlus planned to <strong>roll out “Transactions without PIN” settings for small-amount MPM, QRIS Tap, and CPM transactions</strong>. This meant, just like “QRIS Tap”, both MPM and CPM now needed to be <strong>called out by name.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*90duWIFYJPmkdztfNjiFiA.png" /><figcaption>The issue surfaced when we created other feature: they needed accurate names.</figcaption></figure><p>MPM as “QRIS Scan” was straightforward. But what about CPM, the flow where users show their QR code?</p><p>At first, we called the CPM flow “QRIS Pay at Merchant”. It made sense in the old UI (before QRIS Tap happened), because it sat under the “Generate your QR code” cluster. In that context, the label felt logical.</p><p>That’s also why “Payment” got so popular. I found at least 6 digital banks using it. In clustered layouts it didn’t feel too problematic, since the main action was scanning and “Payment” just sat under the “generate” section. The split wasn’t always clear, but it worked well enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKIrUQI_1AnHeuKIDnXuEg.png" /><figcaption>“Payment” name for QRIS CPM is popular. I found at least 6 digital banks adopting this misleading approach.</figcaption></figure><p>But once it stood alone as a feature name in the “Transactions without PIN” settings page<strong>,</strong> the context was gone.</p><p>Side by side with QRIS Scan<strong>,</strong> both labels pointed to “payment,” just through different mechanisms. That redundancy was the exact ambiguity that opened the chance to fraud.</p><p>So we knew we couldn’t stick with <em>Pay at Merchant,</em> <em>Payment, </em>nor<em> Make Payment.</em> We needed something sharper that made the difference obvious.</p><h3>More explorations &amp; testings</h3><p>We explored industry patterns, ran quick copy testing, and debated. The keyword that stuck was <strong>Show, </strong>and the team leaned toward <strong>“Show QR”</strong>: it felt like the clearest way to separate <em>scanning a merchant’s QR</em> from <em>getting scanned</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*Mq1iThPHCwWoqBPXP77O0A.png" /><figcaption>Some banks use “Tampilkan”/“Show,” but only as a bridging body copy (like Livin’ and BCA on iOS). Others settle for a one-word approach, “Show” or “Show QR.” That makes sense since they don’t run the full set of QRIS features. Still, it’s confusing because the label doesn’t specify what happens after showing the QR code.</figcaption></figure><p><strong>“Show QR” was close, but not fully accurate.</strong> It was still generic. Even worse, it’s honestly as bland as “Payment”. Users might not immediately connect it with the specific act of <em>paying at cashier.</em></p><p>That’s when we knew we needed a stronger anchor.</p><h3>Validation and final call</h3><p>One solid advice I got on my Day 1 was: <em>when in doubt writing UX copy, think about the offline behavior.</em></p><p>So I circled back to the QRIS scenarios I had imagined.</p><p>At cashier, the CPM flow is simple. They’d say something like: <em>“Where’s the code to scan?” </em>or “<em>Let us scan the QR code”</em><br>What the user does next: they <strong>show their QR code</strong> and by doing that they <strong>make a payment.</strong></p><p>From that short interaction, there are two important cues: <strong>show</strong> and <strong>payment.</strong></p><p>We had already seen that just using <strong>“Payment”</strong> didn’t work. It was too outcome-focused and overlapped with <em>Scan QRIS</em>.</p><p>So the next step was to connect the dots. If <em>Payment</em> alone wasn’t enough, we needed a phrase that tied the <strong>action</strong> (showing the code) to the <strong>intent</strong> (paying). That’s where <em>to pay</em> came in. It bridged the gap and turned the label into something users could instantly relate to.</p><p>We validated this with a quick copy test on 8 participants who are regular users of SimobiPlus and MyBCA.</p><p>A few interesting highlights:</p><ul><li><strong>“Payment”</strong>: 5/8 found it confusing. “I’m not sure if this means I’m paying or receiving.”</li><li><strong>“Pay at Merchant”</strong> (our old label): some said it sounded clearer than “Payment,” but also clunky. Some other even thought it was a separate feature, not QRIS. One participant related it to what they do at Indomaret/Alfamart, but still questioned why BCA separates <em>Transfer</em> and <em>Payment</em> if both feel like sending money.</li><li><strong>“Show QRIS to Pay”</strong>: 7/8 connected it right away with the cashier flow. “Oh yeah, this is literally what I do, I show my QR code so the cashier can scan it.”</li></ul><p>That gave us the validation to move forward with “<strong>Show QRIS to Pay”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*2ra096LoYyQoWSAoOhQuyw.png" /><figcaption>Wrapped! Explicitly calling out QRIS flows: MPM = Scan QRIS to Pay, CPM = Show QRIS to Pay. Clear enough: one scans, the other shows.</figcaption></figure><p><strong>What I learned:</strong></p><ul><li><strong>Benchmarking against big players ≠ best practice.</strong> It shows what users may be used to, but not what works best. The final call still needs to be made carefully, otherwise your app ends up with blind spots.</li><li><strong>Offline cues are underrated. </strong>We paid attention to what the cashier says and what the user does in that moment. The offline behavior of showing a code and making a payment became the keywords we pulled into the microcopy.</li><li><strong>Tiny copy ≠ tiny impact.</strong> One unclear word can mislead, one clear word can protect.</li></ul><p>Read more about QRIS. <strong>Source:</strong></p><p><a href="https://qris.interactive.co.id/homepage/blog-detail.php?lang=id&amp;page=MTYz-jangan-keliru-ini-perbedaan-qris-tap-dan-qris-berbasis-kode-qr">https://qris.interactive.co.id/homepage/blog-detail.php?lang=id&amp;page=MTYz-jangan-keliru-ini-perbedaan-qris-tap-dan-qris-berbasis-kode-qr</a></p><p><a href="https://www.bi.go.id/en/fungsi-utama/sistem-pembayaran/ritel/kanal-layanan/qris/default.aspx">https://www.bi.go.id/en/fungsi-utama/sistem-pembayaran/ritel/kanal-layanan/qris/default.aspx</a></p><p>This work wasn’t done in a vacuum. <strong>Collaborators:</strong></p><p>Product Managers: <a href="https://www.linkedin.com/in/nicolatif/">Nico Latif</a>, <a href="https://www.linkedin.com/in/nicholas-liundi-575ba6192/">Nicholas Liundi</a>, <a href="https://www.linkedin.com/in/marcellius-xavier/">Marcellius Xavier</a><br>Product Designers: <a href="https://www.linkedin.com/in/ginanjarpr/">Ginanjar Prabowo</a>, <a href="https://www.linkedin.com/in/ardideswan/">M. Ardi Deswanto</a><br>Thought Partners: <a href="https://www.linkedin.com/in/listya-nareswari131/">Listya Nareswari</a>, <a href="https://www.linkedin.com/in/adinda-wardhani-01108250/">Adinda C. Wardhani</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15bfd2764647" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>