Privacy-preserving Telemedicine Sample App

The Revolut Flutter SDK is the open-source one-package solution for accepting Revolut payments (card, Revolut Pay, Apple Pay) inside a Flutter mobile app. It wraps Revolut's native Android and iOS SDKs into a single Dart API so you ship payment integration in a day, not a sprint. Built and maintained by Life Value. MIT licensed.

What it is

Revolut Business gives merchants a payment gateway with native SDKs for iOS and Android. Flutter teams used to write platform channels by hand for both. Pain on every release, friction every time Revolut shipped an SDK update. The Revolut Flutter SDK packages both native sides into one Dart API. You write the payment flow once.

• Card payments. Mastercard, Visa. Hosted card-entry flow; PCI-DSS scope reduced.
• Revolut Pay. Revolut's wallet-style one-tap pay.
• Apple Pay. Fully wired in.
• Google Pay. Supported once Revolut ships it in their native SDK. We track upstream; package updates automatic via pub.dev.

Why this matters for healthcare apps

Healthcare apps need payments in three places: HSA / FSA reimbursement, patient-paid co-pays inside member portals, and employer-paid benefit top-ups. Each one wants a payments flow that does not introduce PCI-DSS scope into the rest of the app. Revolut's hosted card-entry flow handles that. The SDK never sees the raw PAN. You stay outside PCI scope while the SDK handles the transaction. Same architectural argument as Stripe Elements, but with European payment-method coverage that matters for cross-border healthcare programmes.

Compliance posture: the SDK does not touch PHI. The payment flow is patient-context-aware (you pass the patient ID, amount, currency, and reference) but the merchant API never sees clinical data. Use it for benefits, co-pays, paid telemedicine, paid genetic-test orders, paid second opinions, paid lab kits.

Stack and requirements

How it installs

Add the package to your pubspec.yaml. Initialise with a Revolut Business Merchant ID (you get this from your Revolut Business account). The first integration takes a developer about an hour, including testing in Revolut sandbox mode.

Full installation walkthrough, including the Merchant ID setup, sandbox-to-production switch, and a sample app with all four payment methods wired, sits inside the example folder of the GitHub repo. Direct link in the email after you request access below.

Frequently asked questions

Do I need a Revolut Business account to use this?

Yes. The Merchant ID that initialises the SDK comes from a Revolut Business account. Revolut Business is free to open in most EU/EEA countries plus the UK; merchant onboarding takes a few business days. The SDK itself does not require any Revolut relationship at build time.

Is this PCI-DSS compliant?

The SDK uses Revolut's hosted card-entry flow, which means the SDK and your app never see the raw card number. This reduces your PCI-DSS scope to SAQ A (the lightest tier). You still need to maintain SAQ A compliance for the rest of your stack: TLS, secure storage of merchant credentials, and so on.

Does this handle PHI?

No. The SDK transmits payment data only. The patient reference you pass through is your own opaque identifier; no clinical information leaves the SDK. Treat the SDK as a payments component; treat PHI handling separately under your HIPAA/GDPR programme.

How is this licensed?

MIT licence. Use it in commercial healthcare products without restriction. We do ask that you keep the attribution in the package.

What about Google Pay?

Revolut has not yet shipped Google Pay in their native Android SDK as of mid-2026. When they do, this package will be updated to expose it. Watch the GitHub releases.

Who maintains this?

Life Value (Tech Stack App SRL, Romania). Issues filed on the GitHub repo get triaged within one business day. Major releases follow Revolut's native SDK releases.

Why we built it

Life Value builds healthcare software for European founders, payers, and healthtech enterprises. Several of our client engagements ship with Revolut as the payment processor. We were writing the same Flutter platform-channel code on every project. We open-sourced it so nobody has to write it again. The package is now used in production by our clients and by independent Flutter teams across Europe.

Get the setup guide

Submit your name and email through the form at the bottom of this page. We send you a one-page setup guide (Merchant ID setup, sandbox-to-production switch, sample-app walkthrough), the GitHub repo and pub.dev links, and a short Loom video walking through the integration.

Last reviewed: 30 May 2026