RF
Riza Fauzi
HomeExperienceProjectsEducation
LinkedInContactDownload CV
01/Overview01 — 06
Overview01Description02Details03Tech stack04Screens05Contact06
← All projects01/Simas Merchant
bsim-logo
WORK · 01Bank Sinarmas

Simas Merchant.

Bank Sinarmas' QRIS merchant app, rebuilt in React Native: accept payments, track sales, and manage every outlet from one phone.

Mobile app · Merchant Payment App · 2025 — Now · Lead Frontend EngineerVisit website ↗
02/Description

About the project.

Simas Merchant lets Bank Sinarmas merchants accept QRIS payments and run their business from a smartphone. I led a three-person team rewriting it in React Native: QRIS payment flows (CPM and MPM, including QRIS Tap), daily sales reports, a searchable transaction history, multi-merchant switching, and role-based access for cashiers, managers, and owners.

03/Details

Challenges & decisions.

What it does

Simas Merchant is Bank Sinarmas' app for merchants. Shops accept payments by QR code and follow their sales in real time, without an EDC machine. Because the codes follow the national QRIS standard, customers can pay from any bank or e-wallet app on the QRIS network. The app has 10K+ downloads on Google Play.


Rewritten from the ground up

The app was rewritten from the ground up in React Native and TypeScript. It talks to the bank's payment and merchant services and must keep every payment status accurate, because merchants rely on it to know whether a customer has actually paid.


What's inside

  • Merchant picker for owners who run several outlets under one account.

  • Daily report of money in and out, with one-tap Show QRIS, QRIS Tap, and Scan QRIS.

  • Transaction history with period, amount, status, and type filters, plus net revenue totals.

  • Detailed QRIS receipts with merchant, acquirer, and customer data.

  • QRIS Tap: NFC phone-to-phone payments with a timed session.

  • Refund requests, password and EasyPIN management, and Indonesian/English language switching.


The hard parts

  • Keeping payment states (processing, successful, failed) accurate and easy to read at the till.

  • Role-based access, so cashiers see only what they need while owners see every outlet.

  • Showing payments, cash deposits, QRIS Tap, and refunds in one consistent history.


My part

I led the three-person frontend team on the rewrite: I set the architecture and module structure, built the core payment and transaction history flows, and reviewed every change before release.

04/Tech stack

Built with.

01React Native
05/Screens

A look inside.

AppiOS · Android
List of the owner's merchants to choose which store to manage.
01 · Select merchant
Cashier home with daily money in and out, QRIS actions, and recent transactions.
02 · Home
Transaction history with period filter, totals, net revenue, and a searchable list.
03 · Transaction history
Successful QRIS payment receipt with merchant and customer details.
04 · Payment success
QRIS Tap screen showing the amount and asking the merchant to tap the customer's phone.
05 · QRIS Tap
Settings for password, EasyPIN, refund requests, language, and logout.
06 · Settings
←
PREVIOUS PROJECTARMS.
NEXT PROJECTSimas Merchant Landing Page.
→
Open to roles

Let's work together.

Frontend & Mobile Engineer (React, React Native)

Contact meDownload CV ↓
RF
Frontend & Mobile Engineer (React, React Native)mrizafauzi.r@gmail.com
SECTIONSExperienceProjectsEducation
ELSEWHERELinkedIn ↗GitHub ↗Instagram ↗
© 2026 Riza Fauzi