Platform Overview
TAPP Cash is a financial platform API that gives organizations programmatic control over the full banking lifecycle — covering role hierarchy, user types, environments, and key concepts from admin setup through client operations.
Role Hierarchy
TAPP Cash organizes users into two groups: admin roles that manage the organization and its clients, and client-facing roles that hold and operate financial accounts.
flowchart TD
Root["Root Advisor"]
HBM["Head Branch Manager"]
BM["Branch Manager"]
Advisor["Advisor"]
Ind["Individual"]
BO["Business Owner"]
Op["Operator"]
Root --> HBM
Root --> BM
HBM --> Advisor
BM --> Advisor
Advisor -->|invites| Ind
Advisor -->|invites| BO
BO -->|invites| Op
Admin Roles
Top-level admin. Manages all branches and admin tiers with full visibility across every client portfolio and report.
Manages Advisors across branches. Oversees all client transfers, auto-payments, and reports for managed branches.
Manages Advisors within a branch, reviews client transfer requests and portfolios, and configures approval settings.
Front-line role. Invites and manages Individual and Business Owner clients — transfers, auto-payments, and reports.
Client-Facing Roles
Holds personal checking and savings accounts. Completes KYC, initiates transfers and ACH, and views transaction history.
Holds business accounts. Completes KYB verification and invites Operators to manage accounts on their behalf.
Acts on behalf of a Business Owner with assigned permissions — transfer funds, run ACH, or schedule auto-payments.
User Lifecycle
flowchart TD
A["Advisor signs in"]
A --> B{"Invite client"}
B -->|Individual| C["Individual accepts invite"]
B -->|Business Owner| D["Business Owner accepts invite"]
C --> E["Individual completes KYC"]
D --> F["Business Owner completes KYB"]
E --> G(["Individual accounts active"])
F --> H(["Business accounts active"])
H --> I["Business Owner invites Operators"]
G --> J["Transfers, balances, notifications"]
H --> J
I --> J
Base URLs
| Environment | Base URL |
|---|---|
| Staging | https://api-{tenant}.stage2.tappbank.com |
| Production | https://api-{tenant}.tappcash.com |
Replace {tenant} with your organization's assigned tenant identifier. For example, if your tenant is acme:
POST https://api-acme.stage2.tappbank.com/users/public/v1/auth/signin
Contact [email protected] to obtain your tenant identifier and production credentials.
Staging shortcut: The shared test environment is available at
https://api-test.stage2.tappbank.com— useful for initial exploration before your tenant is provisioned.
Selecting Your Tenant in the API Reference
When using the Try It feature in the API Reference pages, a server selector appears at the top of each endpoint. You must choose the correct server and enter your tenant identifier before sending requests.
- Open any API Reference endpoint (e.g., Sign In).
- Click the Server dropdown — it defaults to the shared staging URL.
- Select Staging (custom tenant) or Production if your organization has a dedicated tenant.
- Replace the
{tenant}variable in the URL field with your tenant identifier (e.g.,acme). - Add your Bearer token in the Authorization section.
- Click Try It to send the request.
If you are just getting started and do not yet have a tenant, use the default staging server (https://api-test.stage2.tappbank.com) with the test credentials provided during onboarding.
API Versioning
Endpoints follow a versioned path pattern:
/{service}/{visibility}/v{version}/{resource}
| Segment | Example | Meaning |
|---|---|---|
service | users, branches, accounts | Microservice owning the resource |
visibility | public, private | Public = no auth; Private = Bearer token required |
version | v1 | API version |
resource | auth/signin, individual | Resource path |
Environments
Staging is for development and testing. Use test credentials and dummy data — no real money moves. Staging credentials will not work against the production base URL.
Production requires separate credentials issued by the TAPP Cash platform team. Contact [email protected] to request production access.
Updated about 2 months ago
