Kem Business ఎలా పనిచేస్తుంది

ప్లాట్‌ఫారమ్ లిఖిత పటం — ఖాతాలు & పాత్రలు, ప్రతి వాలెట్ ఎక్కడ ఉంటుంది, కార్డులు, పేమెంట్ గేట్‌వే, ఉపసంహరణలు & బిల్లింగ్, ఇవన్నీ ఎలా అనుసంధానమవుతాయి.

How it fits together

Kem Business is one account with three moving parts: a payment gateway that turns links, products or API calls into settled USDT; a set of wallets where that money lives and moves; and a team of people whose roles decide exactly which of those surfaces they see. Everything below describes how the parts connect — which wallet funds what, who may touch which button, and what each action costs.

One idea repeats throughout: businesses are verified once (KYB), and people are verified individually (KYC). The business verification unlocks real money; a person's verification unlocks the actions that money leaves through — withdrawals and cards.

Accounts & roles

Every teammate signs in with their own email and holds one role. Roles map to permission bundles — the sidebar only shows what the role can actually use. Two identities deserve special mention: the owner is the human the business belongs to, and an invited member can additionally link their personal Kem app account, which is what gives “their money” a destination outside the business.

ownerEverything. The only role that moves money out of the company wallet, issues the company card, and links the business to their personal Kem account.

adminFull dashboard control except owner-only money movement: team, products, payments, settings.

financePayments, wallet, withdrawals, analytics, exports — the money pages, without team or developer control.

developerAPI keys and webhooks, payments visibility — everything an integration needs, nothing else.

managerDay-to-day operations: payments, products, recipients.

employeeTheir own corner: their salary wallet, their card, their payslips.

viewerRead-only across the pages their team shares.

customA hand-picked permission list when none of the presets fit.

Wallets

Money in Kem Business always sits in exactly one of three places, and every screen in the dashboard is scoped to one of them:

business walletThe company's money. Created automatically when KYB is approved. Settled customer payments, deposits and refunds land here; withdrawals, payroll and the company card draw from it.

salary walletEvery member's personal sub-wallet inside the business — including the owner's. Payroll and one-off transfers arrive here; the member's own card spends from here.

personal Kem walletThe member's own wallet in the Kem consumer app, connected by QR pairing. Members move salary-wallet money to it, then spend or withdraw in the app on their own terms.

The flow between them is one-directional by design: customer payments settle into the business wallet → the business pays people into their salary wallets → each person moves their salary to their personal Kem wallet when they want it off the company's books. The Wallet page shows each of these as a separate view with its own ledger; every payment, transfer, card spend and fee is one row there.

Payment gateway

Three doors into the same pipeline: payment links shared from Products, hosted checkouts created over the REST API, or ad-hoc payments from the dashboard. A customer pays USDT on a Kem-hosted page; Kem watches the chain, confirms, and settles the amount minus the processing fee into the business wallet. The fee follows a volume ladder — your live rate and the full ladder are on Settings → Pricing.

Before KYB approval all payments are test mode: same flow, same webhooks, no money. After approval, live keys and live links move real funds. Refunds are issued from the payment's own page and travel back on-chain. The full API contract — endpoints, webhooks, signatures — lives in the Developer documentation.

Cards

Kem cards are virtual Visa cards funded directly by a wallet — no top-ups, no separate card balance. The company card belongs to the owner and spends the business wallet. Every member (the owner included) can also self-issue a personal card on their salary wallet, so team spending never touches company funds unless you route salary there first.

Issuing requires the cardholder's personal KYC (done in the Kem app) and costs a flat fee debited from the funding wallet. A purchase places a hold on the wallet, and the cleared amount — including the provider's FX conversion and per-transaction fee, both shown on the ledger row — is written off when it settles. Cards can be added to Apple Pay and Google Pay from the card's reveal screen.

Withdrawals

Three ways out of the business wallet, all owner-gated and all quoted before you confirm: off-ramp converts USDT to fiat on a local payout rail (bank transfer, mobile wallets, region by region) with a live quote and the provider's rate shown up front; on-chain sends USDT to any external address; SWIFT wires USD to a bank account with its own beneficiary record and flat wire fee.

Off-ramp additionally needs the person withdrawing to be KYC-verified — the payout partner names them as the sender. Recipients you pay repeatedly can be saved once under Recipients.

Team & payroll

Invites go out by email with a role attached. Accepting creates the member's login, their salary wallet, and — once they link the Kem app — the bridge to their personal money. Pay them one-off from the Wallet page or set a recurring payroll schedule per member under Team; each run is a normal ledger transfer they can see land in real time.

Verification & sandbox

A new business starts in sandbox: the whole dashboard is open — test payments, team invites, products, API keys — but no wallet exists and nothing real can move. Submitting KYB (company documents, ownership, expected volume) keeps sandbox on while we review. Approval creates the business wallet and flips payments live.

Separately, each person who moves money — withdrawing, or holding a card — completes their own identity verification in the Kem app; the dashboard syncs the result and tells you exactly when it's needed.

Plans & billing

Two independent meters. Processing fees follow actual volume down a tiered ladder, frozen per payment at settlement. The subscription plan (Starter, Growth, Scale, Enterprise) is chosen, not derived: it prices seats, monthly free off-ramps, API access and advanced analytics. Every fee of any kind — processing, off-ramp, card issuance, subscription — appears itemised on Settings → Billing, and nothing is ever charged while billing is disabled on your account.