FINANCE
Vyom - Union Bank of India
Banking app with account, payment, loan, and offer flows that need controlled rollout.
- Google Play installs
- 28.0M
- Store rating
- 3.7
For Fintech & Banking
Ship security fixes to your banking app without waiting on store review
When a fix only touches the web layer of your Capacitor app, ship it as an encrypted, signed live update. Stage it on a channel, roll it out by percentage, and keep a record of who shipped what.
human support from Martin
SOC 2 Type II and ISO 27001 (Enterprise plan)
EU data location option
Encrypted and signed bundles
Why finance teams add a live update lane
Web-layer fixes should not wait on a new binary
The store-only fix path
Your team finds a bug in a payment or login screen. The fix is a few lines of JavaScript.
With a store-only process, you build a new binary, submit it, and wait. Store review is often 24–48 hours, sometimes much longer.
Even after approval, users still have to install the new version before they get the fix.
Store review sits between you and the fix
A web-layer fix waits for a new binary, store review, and user updates before it reaches everyone.
Every release needs a record
Security and compliance teams want to know who changed production, when, and which build is live on each channel.
Risky changes need gradual exposure
A change to a transfer or card screen should reach a small group first, with a fast way back if something looks wrong.
Vendor reviews ask hard questions
Your vendor review will ask how bundles are protected, where update data is stored, and whether you can inspect the code.
What Capgo gives fintech teams
A controlled way to ship web-layer fixes
Controls that match how regulated teams ship: encrypted bundles, staged exposure, and a record of every change.
Patch the web layer directly
Upload the fixed JavaScript, HTML, and CSS with the Capgo CLI. Devices on the channel download it in the background and switch to it the next time the app comes back to the foreground. Native code changes still go through the stores.
Channels docsAudit logs and access control
Organization, app, and channel activity logs show who changed what. Channel history lists every bundle that was live, so you can answer auditors and roll back from the same screen.
Organization roles- Organization, app, and channel audit logs
- Roles per organization, app, and channel
- 2FA enforcement, plus SSO on Enterprise
End-to-end encryption and signing
Create a key pair with the CLI. Bundles are encrypted before they leave your machine or CI, and the app checks them before installing. Capgo never sees the plain bundle.
Encryption docsProgressive rollout and automatic rollback
Send a new bundle to 5% of devices, watch install and failure data, then increase or roll back. If a bundle never calls notifyAppReady(), the device returns to the last working version by itself.
notifyAppReady() and automatic rollbackHow it works
How a fintech team ships a fix with Capgo
A typical setup for a Capacitor banking or payments app. Every command below is from the Capgo CLI docs.
-
Create your encryption key once
Create a key pair, save the public key in your Capacitor config, and sync. Keep the private key in your CI secrets, never in the repo.
Encryption docsnpx @capgo/cli@latest key create npx @capgo/cli@latest key save --key ./.capgo_key_v2.pub npx cap sync -
Upload an encrypted bundle to staging
Your QA and compliance testers use a staging channel. The bundle is encrypted with your key during upload.
Channels docsnpx @capgo/cli@latest bundle upload --channel staging --key-v2 -
Roll out to a small share of production
Send the reviewed bundle to 5% of production devices. Everyone else stays on the stable bundle.
Progressive rollouts docsnpx @capgo/cli@latest bundle upload --channel production --key-v2 --rollout 5 -
Promote or roll back
When install and failure data look right, promote the bundle to everyone. If not, roll the cohort back to stable.
Rollbacks docsnpx @capgo/cli@latest channel set production --rollout-promote # or, if something looks wrong npx @capgo/cli@latest channel set production --rollout-rollback
Security and compliance details
What you can show your security and vendor review teams
SOC 2 Type II and ISO 27001 on Enterprise
The Enterprise plan comes with SOC 2 Type II and ISO 27001, a DPA, SSO, and a published sub-processor list for your vendor review.
GDPR support and EU data location
Point the updater plugin at the EU endpoints so update checks, statistics, and channel data stay in Europe. A DPA is available for review.
End-to-end encryption
Bundles are encrypted with your key before upload and verified on the device. Capgo, storage providers, and CDNs only see ciphertext.
Open source you can audit
The updater plugin and the Capgo backend are open source on GitHub. Your security team can read the code that downloads, checks, and installs bundles on your users' devices.
View on GitHubApps built with Capacitor
Banking apps need safe, staged interface fixes
Banking and money apps with accounts, payments, offers, investments, and support flows have to move quickly while preserving trust. Capgo fits fixes that can be shipped through the approved web layer and expanded gradually.
FINANCE
FINANCE
IndOASIS Indian Bank MobileApp
Mobile banking surface where reviewed interface changes should expand gradually.
- Google Play installs
- 15.4M
- Store rating
- 4.2
FINANCE
Orange Money Sénégal
Wallet app where support copy and transactional UI changes need caution.
- Google Play installs
- 2.6M
- Store rating
- 4.0
Customer proof
What teams shipping with Capgo say
Sergiu S
Lead Developer, drivolino GmbH
“The Capgo Capacitor Updater plugin completely transformed how we ship updates. What used to take days now takes just minutes.”
no-tone @ Webincode
Developer, Webincode
“Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.”
Kapil
Founder, NuTriQ
“Being able to push production OTA updates instantly without waiting for full App Store review cycles has been a massive operational advantage.”
FAQ
Questions fintech teams ask
Straight answers for engineering, security, and compliance reviewers.
Are live updates allowed in banking apps on the App Store and Google Play?
Capgo only updates the web layer of a Capacitor app: JavaScript, HTML, CSS, and assets. It does not change native code, permissions, or store metadata. Use live updates for web-layer changes that stay within the store rules and the scope of your reviewed app, and ship native changes through a normal store release.
Compliance and data handling
Can Capgo read our app bundles?
Not when encryption is on. Bundles are encrypted with your key before upload, so Capgo and its storage providers only hold ciphertext, and only someone with your private key can publish a valid update. Like any shipped app, the code on the device can still be reverse engineered, so keep secrets on your servers.
Encryption docs
Is Capgo SOC 2 and ISO 27001 certified?
Yes. Capgo holds SOC 2 Type II and ISO 27001, available on the Enterprise plan together with SSO, a DPA, and dedicated support. The sub-processor list and data handling details are public so your vendor review can start before you talk to us.
Compliance and data handling
Can we keep update data in the EU or run Capgo ourselves?
Yes. Set the updater plugin's update, stats, and channel endpoints to the EU host to keep live update data in Europe. The Enterprise plan also offers dedicated, hybrid, and licensed self-hosted setups.
EU data location
How do we limit who can push to production?
Use organization, app, and channel roles so only release managers can change the production channel. You can enforce 2FA and password policies for the whole organization, use SSO on Enterprise, and review changes in the audit logs.
Organization rolesGive your security fixes a faster path
Set up encrypted bundles, a staging channel, and a progressive rollout on your own app during the trial.
human support from Martin
14-day free trial, no credit card. SOC 2 Type II, ISO 27001, and SSO come with the Enterprise plan.