Welcome to TAPP Cash

TAPP Cash is a financial platform API that lets organizations embed banking capabilities into their products. With TAPP Cash, you can build and manage the full client lifecycle — from inviting users and verifying their identity through daily banking operations including transfers, account management, and reporting.

These docs are for engineering teams integrating the TAPP Cash API on behalf of your organization.

What can you build?

Quickstart

Recipes

End-to-end integration patterns with every API call in sequence.

Base URL

Your base URL follows the pattern https://api-{tenant}.stage2.tappbank.com where {tenant} is your organization's subdomain.

Contact [email protected] to get your tenant name.

Selecting Your Tenant in the API Reference

Every endpoint in the API Reference has a Try It panel that lets you make live requests directly from the docs. For it to work, you must set your tenant name first.

How to set your tenant:

1. Open any endpoint page in the API Reference (e.g. Sign in)
2. In the Try It panel on the right, click the server URL dropdown at the top — it shows the current environment
3. Look for the tenant variable field and replace test with your actual tenant name (e.g. wire-network)
4. Your requests will now go to https://api-{your-tenant}.stage2.tappbank.com

If you skip this step and leave the tenant as test, requests will fail or return a CORS error because api-test is a placeholder and may not resolve to your organization's environment.

The tenant setting persists for your browser session across all endpoints in the same spec section.

Authentication

All requests use session-based authentication. Include these two headers on every API call:

X-Session-Id: <sessionId>
X-Client-Id:  <clientId>

Sessions are obtained from POST /entrypoint/org/v1/sessions using your clientId and clientSecret. Sessions are valid for 24 hours.

To obtain credentials, contact [email protected].

Rate Limits

The API gateway enforces rate limits per client IP. Limits are configured per endpoint — every response includes headers
so you can track your current usage.

When the limit is exceeded the API returns 429 Too Many Requests. Back off and retry after the time indicated by
X-RateLimit-Reset. See Error Handling for the full retry strategy.

Standard Response Format

Every response — success or error — follows the same envelope.

Success

{
  "data": {},
  "meta": {}
}

Error

{
  "errors": [
    {
      "code": "ERROR_CODE",
      "title": "Human-readable summary",
      "details": "Additional context",
      "target": "field | common",
      "source": "fieldName"
    }
  ]
}

Role-Based Access

Your token is scoped to a role. Calling an endpoint outside your role returns 403 Forbidden.

Support