SoulBit Personal and SoulBit Business on Mobile: What the Apps Bring

When a platform announces that it "will have an app", a CFO asks what the team will be able to do from a phone, what risk it adds and what to prepare. The answer depends on the app and its verified availability.

At Soulbit Academy we write for CFOs, finance managers and founders of Latin American SMBs who want to decide on facts. This article explains what is planned for SoulBit Personal and SoulBit Business, what stays on the web and what to settle before the apps arrive. It is an informational guide, not a launch notice.

Soulbit app: two apps with two different jobs

Soulbit is preparing two hybrid mobile apps for iOS and Android: one for individuals in the SoulBit Personal offering and one for companies in SoulBit Business. As of October 30, 2026, we could not verify official store listings. Check the stores and Soulbit's official channels for current availability; we have no launch date to confirm.

SoulBit Personal and SoulBit Business are names of commercial offerings, not names assigned to the apps. The planned individual and company apps have no separate product names in the documentation. Anyone searching for the "Soulbit app" should verify the publisher in the official stores.

The difference matters because each app serves a different user. The Personal app is planned for a person managing their own balance. The Business app is planned for a company that needs to see its position from a phone without executing sensitive operations. The existing company web platform supports KYB, employee management and internal payroll; external disbursement and expanded limits are planned.

Why two apps instead of one?

Because a company and an individual carry different risks. An individual decides about their own money. A company has several users, roles and approvals, and internal control requires that the person who views a balance is not necessarily the one who orders a payment. Separate apps reflect that difference in the product design.

If you do not yet know the platform, what Soulbit is and how it works for an SMB describes its three main functions before we turn to mobile.

What SoulBit Personal and SoulBit Business will do

The planned Personal app will let an individual register, verify their identity and view balances from a phone. The planned Business app will let a company view its balance, portfolio and history, and receive alerts. These are selected examples of the agreed scope, not a complete feature list.

Nine examples of planned Personal app functions are registration and login; phone verification; 2FA and biometrics; identity verification (KYC) with facial verification; a portfolio with balances; sending and receiving funds; history and statements; push notifications; and integrated support staffed by a human team. The product requirements cover additional functions.

SoulBit Business will have four view-only functions: login with 2FA; company balance and portfolio; transaction history; and push notifications.

Planned function	Personal app	Business app	Company web platform
Login with 2FA	Yes, with biometrics	Yes	Access with own user
Identity verification (KYC) with facial check	Yes	Not applicable	Not applicable
Balance and portfolio view	Yes	Yes, company level	Yes
Transaction history	Yes, with statements	Yes	Yes
Push notifications	Yes	Yes	Not applicable
Sending and receiving funds	Yes	No	Yes
Integrated support with a human team	Yes	No	Yes
External disbursement and expanded limits	No	No	Planned integration
Company payroll	No	No	Internal payroll exists; external Soulbit Salaries planned

The table leads to a practical conclusion. Anything that moves company money in volume stays on the web. The phone is for viewing and for receiving alerts.

Why SoulBit Business is view-only

The planned Business app is view-only because the product design sets a principle: sensitive company operations are performed on the web, not in the company app. Internal payroll stays on the web; external Soulbit Salaries disbursement and expanded limits are planned there as integrations. It is a control decision, not a shortcoming.

From a CFO's viewpoint this has clear advantages. A phone gets lost, shared or left unlocked. A view-only company app does not provide a way to order a bulk payment from the device. Unauthorized access to company information remains a risk.

There is a second, accounting advantage. Approvals that stay on the web leave a single trail, not split across two channels. To see how that evidence is organized, read payment traceability and accounting records.

What does a company lose by not operating from a phone?

It loses speed in out-of-office emergencies. A manager who is traveling cannot approve a payment from the app. That friction is deliberate. The alternative, approving payments from any phone, widens the fraud surface and weakens segregation of duties.

Companies that already have a payment approval policy often find this split consistent with the principle of segregation of duties. The guide to internal controls for payment approval in an SMB covers how to structure it.

Security: 2FA, biometrics and institutional custody

App security rests on three layers: two-factor authentication, biometrics in SoulBit Personal and institutional custody of the funds. No layer replaces the others. Authentication protects access, and custody protects the asset.

The first layer is 2FA, which requires a second factor beyond the password. NIST, the US standards institute, sets out in SP 800-63B-4 on authentication and authenticator management assurance levels that rely on multiple factors. It is a widely used technical reference for judging the strength of a login.

The second layer is biometrics in SoulBit Personal. Biometrics confirm that the person using the phone is who they claim to be, without remembering a password. OWASP, the reference body for application security, warns in MASWE-0021 on biometrics and device-passcode fallback that sensitive operations should require strong biometric authentication and not a weaker fallback. That is one more reason to keep those operations on the web.

The third layer is custody. The funds you see in the app are held under institutional custody with MPC technology, the same model as the web platform. Soulbit is custodial: keys are not on the device. A lost phone is not a lost key. You can read more in institutional MPC custody of a company balance.

2FA and biometrics lower the risk of improper access but do not remove it. Tricking a user, such as a message asking them to share a code, remains a training risk and not only a technology risk.

What to do in your company before the apps arrive

Preparing for the arrival takes four management decisions: who gets access, how to separate viewing from authorization, which device policy to apply, and keeping KYB verification and user records current. None depends on the publication date. You can settle them today and avoid improvising the day the app appears.

A hypothetical case helps. Imagine a Colombian SMB with 40 employees, a CFO, an accountant, a treasurer and a general manager. No figure in this example is real.

The first step is to list who needs to see the balance from a phone. Probably the CFO and the general manager. The treasurer already works on the web and may not need the app. The accountant reads history but does it better with the web reports.

The second step is to separate viewing from approval. On the web, the person who orders a payment and the person who approves it should be different people. The app only adds a way to view, so it should not change that rule. Writing it into the treasury policy keeps mobile access from being read as permission to operate.

The third step is a device policy. Decide whether personal phones are allowed, whether a screen lock is required and what happens when someone leaves the company or loses a phone. Removing a user should happen the same day.

The fourth step is to confirm that KYB verification is complete and user data is current. Access to the platform depends on it. If your company has not finished the process, what KYB is and why it matters explains what is checked and why.

Should a company wait for the apps before it starts operating?

No. The company web platform already supports KYB, employee management and internal payroll. The planned company app adds a way to view information; external Soulbit Salaries disbursement and expanded limits need separate availability checks. A company can prepare users and controls on the web without waiting for mobile access.

What V1 delivers and what it does not

The existing web platform supports individual and company workflows. We could not verify official app-store listings as of October 30, 2026; check the stores for current availability. The examples above do not exhaust the planned mobile scope. Confirm any other function and its availability with Soulbit.

The documented web workflow includes KYB verification, employee management and internal payroll, alongside balances, payment links, collection QR, OTC by quote, institutional custody and AML/KYT controls. External Soulbit Salaries disbursement and expanded limits are planned integrations; confirm when they become available. For context, read batch payroll from a file to disbursement.

Aspect	What exists today	What to expect with the apps	What is not claimed
Company operations	Web KYB, employees and internal payroll	Viewing in the planned Business app	External disbursement or expanded limits already live
Access for individuals	Store listing unverified as of October 30, 2026	Registration, KYC and portfolio in the planned Personal app	A publication date
Security	Institutional MPC custody	2FA and biometrics on mobile	Zero fraud risk
Other functions	Those listed in V1	Those in the agreed scope	Unconfirmed roadmap functions

Three limits are worth stating plainly. The first is that there is no launch date we can confirm. The second is that official store listings were unverified as of October 30, 2026, so current availability needs checking. The third is that planned integrations need confirmation before a company relies on them.

How to decide whether the apps matter to your company

The apps matter to a company when several people need to see the balance away from the office and want immediate alerts. If your operation is small and handled by one or two people, the benefit is modest. The web may be enough.

First ask who needs visibility and how often. A CFO who checks the balance daily values a quick view. An accountant who reconciles at month end values complete reports more. Each profile has different needs, and the company app only covers the first.

Then ask how it fits your close. The app does not replace reports or reconciliation. The mobile history is a viewing tool, and your accounting evidence still comes from the web platform.

How will Soulbit announce that the apps are published?

Check Soulbit's official channels and the iOS and Android stores for publication updates. Verify the publisher before installing any application using the Soulbit name, and be wary of links received by message or requests for login details. A fake app is a known fraud vector.

For a CFO the conclusion is simple. The planned apps complement web access with company viewing and personal functions, while control of company money stays on the web. Confirm the availability of external disbursement and expanded limits separately. Users, roles and a device policy can be prepared in advance.