IMBA Partner API

IMBA Partner API is a server-to-server HTTP API for B2B integrators. Your backend manages a USDT settlement balance and issues products (virtual cards, eSIM, gift cards) to your end customers. End users do not log into IMBA Wallet and do not receive a client JWT. All calls use your partner access token. Prepaid autonomous agents (register a key, USDT TRC-20, catalog) are a different product: switch to Agent API in the header, or open Agent API.


API	`https://api.imbawallet.com` (production)
Docs	`https://api-docs.imbawallet.com`
Sandbox	None — Partner API has no sandbox
Support	support@imbawallet.com (usually under 1 hour)

Capabilities

Area	What you can do
Money	Read balance, sticky USDT TRC-20 deposit address, withdraw USDT, pull reconciliation
Cards	Tenant catalog, issue, get (JWE), balance, top up, freeze
eSIM	Offers, purchase, top up, get activation (LPA)
Gift cards	Offers, purchase, get receipt (code / epin)
Ops	Poll by `ext_id`, HMAC webhooks for terminal statuses

How integration works

Your server
  │  1. Sign short-lived assertion JWT (Ed25519)
  ▼
POST /auth/v1/partner/token
  │  2. Receive access_token (900s)
  ▼
GET|POST https://api.imbawallet.com/partner/...
  │  3. Authorization: Bearer <access_token>
  ▼
IMBA processes async work → webhooks + GET documents / products

Start here

Onboarding

Email support — manual review, then keys

Quickstart

Token → balance → deposit address

Authentication

Ed25519 assertion, scopes, isolation

API reference

Full OpenAPI endpoint list

FAQ

Catalogs, lookup, refunds, card lifecycle, what v1 does not expose

Onboarding

Access is manual only after business review — no self-serve or automatic signup.

Email support@imbawallet.com with subject Partner API onboarding — <Your Company>
After IMBA contacts you — generate Ed25519 (+ X25519 for cards) and send public keys only
IMBA registers credentials, webhook, and products by hand

Full steps: Onboarding. Commercial minimum first deposit is 1,000 USDT. There is no monthly volume minimum and no partner sandbox.

Credential delivery

After a successful purchase IMBA does not email PAN, gift codes, or eSIM LPA to your end user. Your server pulls them and shows them in your UI:

Product	Pull
Card (PAN / expiry / CVV)	`GET /partner/cards/{card_id}` (JWE by default)
Gift (`epin`)	`GET /partner/gift-cards/{purchase_id}`
eSIM (LPA / QR)	`GET /partner/esims/{esim_id}`

Webhooks carry status and ids only (plus card.otp for 3-D Secure). See FAQ.

Get started

Money

Products

Operations

Capabilities

How integration works

Start here

Onboarding

Quickstart

Authentication

API reference

FAQ

Onboarding

Credential delivery

​Capabilities

​How integration works

​Start here

Onboarding

Quickstart

Authentication

API reference

FAQ

​Onboarding

​Credential delivery

Capabilities

How integration works

Start here

Onboarding

Credential delivery