Delivery.
Commercial frontend work spanning the 2018 Vue 2 rebuild, ongoing insurer and bank integrations, rendering optimization and payment safeguards. This written case uses a workflow illustration; it does not reproduce the product interface.
CASE STUDY 07 / Fintech · Collections & payouts
Ronghe Pay — Insurance Payments Platform
Built the Vue 2 frontend during the 2018 upgrade of a PHP-based insurance payments product, then supported new insurer and bank integrations. My work included institution-specific configuration, response-field adaptation, large-data rendering and payment safeguards.
Commercial project · Written case studyCONTEXT
Fingard · Ronghe Pay
The name combines “Ronghe” (integration in Chinese) with “Pay”: integrated payments.
MY ROLE
Frontend development · Rebuild & ongoing integrations
TOOLS & FOCUS
Vue 2 · Multi-bank integration · Payment safety · Rendering performance · Reconciliation
01 / THE PROBLEM
What needed to work.
Insurers needed premium collections and claim payouts across banks through one platform. As more clients joined, each insurer and bank required its own configuration. Bank interfaces and response fields differed, while growing data volumes and real-time payment safety added frontend challenges. The platform supported batch and single payments, real-time settlement where available, and reconciliation statements.
CONCEPT / 07
01Insurer + bank configuration
02Payment workflows + safeguards
03Reconciliation statements
A summary of my responsibilities and technical approach. This workflow illustration does not reproduce the product UI.
02 / MY CONTRIBUTION
Where I took ownership.
- Built the Vue 2 frontend from zero to one during the 2018 upgrade of an existing PHP-based product.
- Supported new insurance-company and bank integrations through institution-specific configuration and frontend adaptation of differing response fields.
- Optimized frontend rendering as payment-related data volumes grew.
- Worked on real-time payment safeguards, including prevention of duplicate submissions, across collection and payout workflows.
03 / TECHNICAL APPROACH
Decisions in context.
A rebuild followed by new integrations
My zero-to-one contribution refers to the Vue 2 frontend rebuild of an existing PHP-based product in 2018. The work continued as we onboarded more insurance companies and banks, each with corresponding configuration and integration needs.
04 / DELIVERY & REFLECTION
What I can share.
What I learned.
This was where I began learning the payment domain. Accuracy and timeliness matter throughout the workflow: institution-specific data needs careful interpretation, growing datasets need usable interfaces, and payment actions need safeguards against repetition.
Have a similar challenge?
Let’s talk ↗