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

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

Getting started

Kem Business connects a payment gateway, a company treasury, individual salary wallets and a permission-based team. An owner registers by pairing their Kem app account, then sets a dashboard email and password. Invited teammates join through their invitation link and use their own dashboard credentials.

Choose Payment gateway, Payroll or Both during setup, enter the legal entity's details, and complete Business Verification. The mode changes the dashboard presentation and navigation. An authorized owner can change it later in Settings → Use case; existing records remain attached to the same business.

Organizations & switching

One login can belong to several organizations, with a different role in each. Use the organization chooser at sign-in or the profile menu to switch. Payments, products, API keys, team memberships and company/salary balances belong to the selected organization.

An eligible owner can choose Create new organization in the profile menu. Creation uses the current business's allowance, which KEM support can adjust. Signup businesses normally start with one additional-organization allowance; an organization created this way starts with zero of its own, until KEM explicitly grants an allowance.

Each legal entity completes its own KYB and gets its own company wallet after approval. Verification and balances do not carry over. If setup was interrupted, select the organization marked as incomplete to resume its business-details setup, then complete Business Verification. Additional-organization creation currently requires an original QR-registered owner, a dashboard password and available allowance.

Accounts & roles

These are the built-in role presets. The sidebar also depends on the selected dashboard mode and feature availability. Team roster visibility is open to active members; inviting, changing roles, suspending and removing teammates are separate permissions. Linking a personal Kem account does not promote a teammate or change their business role.

ownerFull business permissions: profile and dashboard-mode changes, ownership management, treasury actions, and company-card issuance. Identity and verification requirements still apply.

adminTeam administration, payments, products, API keys, webhooks and internal transfers; can view the company wallet and all organization transactions. The preset excludes business-profile editing and external withdrawals.

financePayment visibility, company-wallet visibility, all organization transactions, analytics and internal/payroll transfers. The preset excludes Withdraw, API-key/webhook management and team administration.

developerAPI keys and webhooks, payment/product visibility, analytics, internal transfers and their own wallet/card. No organization-wide Transactions access.

managerPayment and product operations, team invitations and internal/payroll transfers, plus their own wallet/card. No organization-wide Transactions access or Withdraw.

employeeTheir own wallet/card, payment creation and visibility, product visibility, the team roster and analytics. No company-funded payroll or organization-wide Transactions access.

viewerRead access to the views in their permission set. No payment/product management, team administration, card issuance or organization-wide Transactions access.

customAn explicit permission set granted by an authorized teammate. The available actions depend on those permissions and any additional owner/verification requirements.

Some actions additionally require the owner role, approved KYB, personal KYC, a linked Kem account or an enabled feature. Ask your business owner about permissions and KEM support about account-level feature access.

Wallets

The Wallet page separates the company's treasury from each person's money:

business walletThe company treasury, created when KYB is approved. Customer payments and company deposits arrive here; payroll, company-card spending, fees and company withdrawals 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 person's wallet in the Kem consumer app. Invited members connect their own Kem account by QR pairing; original QR-registered owners already use a real Kem identity.

A typical flow is business → salary → personal, but transfers can also go back the other way. The wallet transfer flow lets you choose between wallets you can use, including funding the business or salary wallet from your linked personal wallet. Owner-only rules apply when that self-transfer starts from the company treasury.

Paying another teammate is a separate internal-transfer permission, held by the owner, admin, finance, developer and manager presets. Check the selected source wallet before confirming: a company-card purchase and a salary-card purchase reduce different balances.

Transactions & card activity

Transactions is the organization-wide activity view for owners, admins and finance, plus custom roles granted access. It combines company and member-wallet movements with payment records, including pending, failed and expired payments. Wallet labels identify the business or teammate involved; internal transfers appear once.

Filter by type, direction, status, member, currency, network, amount, date range or search. The activity can include payments, card purchases and refunds, payroll, other transfers, withdrawals, SWIFT and collected KEM fees. A pending payment record is not a settled balance movement, and a test payment is not real revenue.

The Cards page uses organization-wide card activity for these same audit roles, including both an owner's company card and salary card. Other card-enabled roles see activity from their own wallet. Their personal Kem app wallet is a separate view, outside the organization-wide transaction feed.

Payment gateway

Create an ad-hoc payment in Payments, a reusable product/price link in Products, or a payment from your server through the merchant REST API. Payments are quoted in USDT. Send the customer to the returned hosted checkout, which offers the supported payment networks and wallet flow.

Pending is awaiting payment; detected is being confirmed; succeeded means the payment completed. A submitted but unconfirmed hash can remain pending beyond the initial checkout window. Check status before treating an order as paid. Collected processing fees are recorded separately, and payment details show the fee and net amount when available. Your rate is shown in Settings → Pricing.

Dashboard checkouts and product links use live mode after KYB approval. API keys select test or live mode independently. Current payment detail pages show status, amounts, fees and the checkout link; merchant-initiated refunds are not currently available, although historical records can have refunded status and card refunds can appear in wallet history.

API-key and webhook management live in their dashboard pages. Keys are business-specific, and an authorized user can reveal or revoke them. See the developer documentation for the supported payment endpoints, testing and signed webhook handling.

Cards

Cards require KEM to enable the feature for your business; platform availability also applies. The company card spends the company wallet. An owner can issue it when that wallet has no live card. Members with card-issuance permission, including owners, can self-issue a salary card on their own business sub-wallet. There is one live card per funding wallet, so an owner can use both wallet types.

The business must have approved KYB and the cardholder must satisfy personal KYC and provider readiness checks. Invited teammates connect their own Kem identity. An invited owner can also use the company-card flow once their real account is linked. Issuance can wait for provider approval; the screen reports when it is ready or still being reviewed.

Cards draw directly from their funding wallets. Review the displayed issuance fee and balance before confirming; KEM billing settings determine whether that fee is charged. Activity shows merchant descriptions, statuses and available currency/fee details. You can reveal your own wallet's card; owners can also reveal the company card. A verification code may be required. The reveal screen includes Apple Pay/Google Pay instructions for manually adding the card.

Withdrawals

The Withdraw section is available to the owner preset and custom roles granted the withdrawal permission; finance and admin presets do not have it. Source-wallet, identity and provider checks still apply. Choose a route: 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.

For off-ramp, select the funding wallet, supported destination/currency and payout details, then review a fresh quote. Personal KYC is required. On-chain withdrawals also require a supported real Kem identity; an invited dashboard identity alone is insufficient. Manage payout details in the withdrawal flow and SWIFT beneficiaries in the SWIFT flow. Recipients is the payroll roster, not a bank-beneficiary address book.

A submitted SWIFT wire remains pending until processing advances; check its status and download the confirmation when available. A failed or uncertain transfer needs its activity checked before you submit another instruction.

Team & payroll

Authorized inviters choose an email and role. Accepting an invitation creates the membership and salary wallet. If the email already has a Kem Business login, acceptance requires its existing password. Owner invitations and promotions are ownership actions; role grants are bounded by the inviter's permissions.

Pay teammates through the available transfer controls in Wallet, Team or Recipients. Recurring transfers support weekly, biweekly, monthly and every-N-days schedules, with a first run, optional end time and note. Review run results and maintain enough company balance. Suspended members cannot act in the dashboard, and their past transactions remain part of the organization's history.

Verification & sandbox

Business Verification (KYB) covers the legal entity: company details, ownership information and supporting documents/agreements. Approval provisions its company wallet and enables live-payment setup. Personal KYC is a separate check for the human using identity-dependent services; completing one does not replace the other.

Current testing limit: products, team setup and test API keys can be prepared before KYB approval, but creating a payment currently requires approved KYB even with a test key. Once approved, use test keys and the documented simulation calls to test payment events without sending money. Test payment records are not evidence of a real transfer.

Open Identity Verification to see whether to connect a Kem account, complete verification in the app, or launch the supported Persona flow in the browser. Invited members verify their linked real identity in the Kem app; eligible real-identity owners can verify from the dashboard. The page syncs the resulting verification status.

Security & sign-in

Use your own login and invite colleagues rather than sharing credentials. The profile menu contains password change and, when enabled, Security. Password changes and resets apply across memberships sharing the same dashboard email.

Where two-factor authentication is enabled, enroll an authenticator and save its recovery codes. Login checks and sensitive-action checks are separate: revealing credentials or card details, sending transfers and granting ownership can require a fresh code. Follow the methods offered for the action; email fallback is not available for every action. Availability and enforcement depend on the deployed security configuration.

Plans & billing

Processing fees follow the current volume tier or a per-business override, and are frozen on successful payments. Subscription plans are Starter, Growth, Scale and Enterprise; the agreed plan controls its included seats, allowances and entitlements. Plan changes are handled by KEM, not automatically applied from volume.

Settings → Pricing shows your effective processing rate, fee totals and other KEM charges. Settings → Billing shows subscription details and billing history, with a fee CSV export for itemized KEM charges. Collected fees also appear in the transaction history. Monthly/annual billing, extra seats and mid-period upgrades can affect a subscription charge.

When KEM billing is disabled for the business, KEM's fee engine does not charge its fees. Individual fee kinds can also be waived. Card-provider FX/spend charges and blockchain/network costs are separate; review the actual quote or card transaction.

Escrow availability

Escrow is a limited-availability feature requiring KEM to enable it for the business and configure a supported network. When available, an authorized merchant creates an order and shares its buyer link. The buyer connects an external wallet, approves the token and funds the on-chain contract. Delivery, buyer confirmation and dispute resolution determine release or refund under the contract's terms.

The current dashboard does not provide a buyer reclaim button or automatically submit timed release transactions. Escrow availability therefore includes operational setup beyond enabling a menu item. It is separate from the public API-key payment endpoints; confirm supported workflows with KEM before using it for an order.

Notifications & help

Check the notification bell and Notifications for account activity. Use the export controls on supported pages where your permissions allow them. Open Help & support from the profile menu when a transfer, verification or feature requires assistance; include the business and payment/transfer reference, never a password, OTP or secret key.