open --case "Payments app — Armenian bank integration via webview + native shells"
Moons: bank webview & native bridge
problem
The bank’s template used relative asset paths, so the payment UI could not be fully validated locally until it ran inside the bank’s environment—yet production could not afford trial-and-error.
constraints
- Strict banking and compliance expectations.
- Required invisible web chrome with native iOS/Android inputs driving hidden web fields.
- Four-way sync: mobile app ↔ webview ↔ bank API ↔ backend.
solution
Implemented the integration once against the spec, hid webview chrome, mirrored native field state into hidden inputs the bank script expected, and wired bidirectional messaging for validation and submission.
outcome
First deployment in the bank environment worked; users completed KYC and payments without rework cycles.
status --result SUCCESS