Industry

Websites and mobile apps for finance and fintech companies

We build websites and mobile apps for startups building products in payments, wallets, personal finance, investment or insurance, and for companies offering financial services. In this field, before trusting you with their money or personal data, users want to see who provides the service, what they will pay and where their data is kept. We build the site and the app to answer those three questions plainly.

01Needs

What a finance or fintech product needs from its site and app

With a financial product, the decision rests on trust, and trust is built in the details. Once visitors understand what the product does, they look at the following: which company provides the service, what its registered name and address are, how much is charged for which transaction, what limits apply, where money and data are kept, and who to contact if something goes wrong. This information should not sit behind a small link at the bottom of the site, but on its own pages in plain language.

On the app side, the first impression is the sign-up flow. If identity verification, phone confirmation and password steps do not tell users why they are being asked for, the flow is abandoned halfway. If identity verification is required, that step connects to the verification provider you have chosen and contracted with; the choice and the responsibility are yours.

Behind the scenes, an admin panel is almost always needed: a screen where the support team can find a user, see transactions, and where a record is kept of who accessed what. The roles and permissions of this panel should be designed from the start, together with the app’s screens.

Common mistakes on finance and fintech websites

01Fees and limits in a PDF or a footnote
When fees appear only in a downloadable document or an asterisked note, users get a surprise and the support team answers the same question over and over. The fee and limit table should be part of the product page and updated from a single place.
02Tracking and ad code loaded on sensitive pages
Analytics and ad pixels placed on logged-in screens or application forms can carry the personal and financial details in form fields to third parties. Which code runs on which page should be listed, and sensitive screens should carry no unnecessary code.
03Marketing copy that promises more than the product allows
Phrases such as “risk-free”, “guaranteed returns” or “instant approval” can mislead users and cause problems with ad platforms and regulators. The copy should say what the product actually does.
04Site and app built by separate teams, unaware of each other
When the fee table on the site does not match the one in the app, or the privacy policy does not match the store data declaration, both users and store review notice. The two should be fed from the same content source.

02What we build

What we build for finance and fintech companies

A startup’s first release and an established company’s new channel are made of different parts. We pick the scope from this list together with you.

01Marketing site

  • A separate page per product: what it does, who it suits, how it works
  • Fee and limit table, updated from a single place
  • Security page: where data is kept, how the account is protected
  • Company information page: registered name, address, the licence and registration details you provide
  • Help centre and frequently asked questions
  • KVKK privacy notice, privacy policy and cookie preferences

02Mobile app

  • iOS and Android app
  • Sign-up, phone confirmation and password flows
  • Face ID and fingerprint login
  • Verification step connected to the identity verification provider you use
  • Transaction history, notifications and in-app support
  • In-app account deletion request

03Backend and admin panel

  • User and transaction search screens
  • Role and permission definitions: support, operations, admin
  • Log of actions taken in the panel
  • Integration with the API of the bank, payment institution or infrastructure provider you work with

04Acquisition and tracking

  • Waiting list or application form
  • Store links and links that open the app from the site
  • A tracking plan that leaves sensitive screens out

03Services

Which services matter for finance and fintech, and how they are adapted

05Things to check

Things to check for finance and fintech products

This field is tightly regulated. The points below are only well-known topics; how they apply to your product is something to settle with your own legal and compliance advisers. Responsibility for compliance stays with you.
01Licensing and supervision
In Turkey, payment services and electronic money issuance are licensed and supervised activities; investment, lending and insurance are also bound by the rules of their own regulators. Determine with your adviser which permission your product requires and what information must appear on the site.
02Content that could be read as investment advice
In Turkey, investment advice is an activity that requires authorisation. If blog posts, newsletters or in-app suggestions could be read as personal investment recommendations, check their wording with your adviser before publishing.
03Advertising and store rules
Google and Meta apply additional rules to financial services ads, and in some countries require advertiser verification. Apple and Google may also ask apps offering financial services for additional declarations and documents. Check the current rules before submitting.
04Personal and financial data
Users’ identity, account and transaction details are data that must be protected under KVKK, Turkey’s data protection law. Decide with your adviser which data is collected, where it is stored and which third parties it is shared with, together with the privacy notice.

06Example

The personal budgeting app we built

07FAQ

Questions finance and fintech companies ask

01

Our licence application is still in progress. Can we start building the app now?

Development can technically start, but which features can be offered under which permission directly affects the product’s scope. So we suggest writing the scope together with your compliance adviser’s view and keeping the release date tied to the licensing process.

02

Do you provide identity verification and payment infrastructure?

No. Identity verification, payment or banking infrastructure comes from providers you have contracted with. We connect the app and the panel to those providers’ APIs; choosing and contracting the provider is up to you.

03

Where will user data be stored?

That is a decision to make before the server and database are set up, and it should be weighed together with your legal obligations. We write the options and the consequences of each into the scope document; you make the decision together with your adviser.

04

Web app or mobile app first?

It depends on where and how often users will use the product. For products used daily that need notifications and biometric login, a mobile app comes first; for products serving business users at a desktop, a web app. We separate together in the scope which one is essential in the first release.

05

Is account deletion mandatory? We have record-keeping obligations.

Apple and Google require apps that let users create an account to offer an account deletion request inside the app. If you have records you are legally required to keep, decide with your adviser which data is deleted and which is retained; we build the flow and the text shown to users accordingly.

Rufy Studio

Tell us about your product and where you are with it

Tell us what you are building, who your target users are, where your licensing process stands and which providers you work with; we will suggest a scope based on that.