Yativo Crypto SDKs

Yativo provides official SDKs for the most popular languages and frameworks, plus an MCP server for AI agents. Every SDK wraps the same underlying Yativo Crypto API and provides a consistent, idiomatic interface for your platform.

TypeScript / Node.js

Full-featured SDK for Node.js and browser environments, including a card embed widget.

Python

Pythonic SDK with snake_case methods and structured exception hierarchy.

PHP

Composer package with static webhook verification helpers.

Java / Spring Boot

Spring Boot starter with auto-configuration, DI-ready services, and event-driven webhooks.

React

Hooks and pre-built components built on top of the TypeScript SDK.

MCP Server

Model Context Protocol server for AI agents — manage agentic wallets via Claude, GPT, or any MCP-compatible agent.

Quick Comparison

Feature	TypeScript	Python	PHP	Java	React	MCP
Package manager	npm	pip	Composer	Maven / Gradle	npm	npm
Package name	`@yativo/crypto-sdk`	`yativo-crypto-sdk`	`yativo/crypto-sdk`	`com.yativo:yativo-crypto-sdk-spring-boot-starter`	`@yativo/crypto-sdk-react`	`@yativo/mcp-server`
Latest version	`1.0.3`	`1.0.1`	`1.0.0`	`1.0.1`	`1.0.2`	`1.0.1`
Min runtime	Node 16 / modern browser	Python 3.8	PHP 7.4	Java 11 / Spring Boot 2.7+	React 17+	Node 18+
Auto token refresh	Yes	Yes	Yes	Yes	Yes	N/A (API key auth)
Webhook verification	Yes	Yes	Yes (static)	Yes (@EventListener)	Via TypeScript SDK	—
Card widget / embed	YativoCardEmbed	—	—	—	YativoCardWidget	—
UI components	—	—	—	—	Yes	—
Agentic wallets	Via API	Via API	Via API	Via API	Via API	Built-in MCP tools

Choosing the Right SDK

TypeScript / Node.js
Python
PHP
Java / Spring Boot
React

Use the TypeScript SDK when:

Building a Node.js backend (Express, Fastify, NestJS, etc.)
Writing a serverless function (Vercel, AWS Lambda, Cloudflare Workers)
Embedding the Yativo Card widget directly in a non-React frontend
You want full TypeScript type safety across all API resources

npm install @yativo/crypto-sdk

Use the Python SDK when:

Building a Django, Flask, or FastAPI backend
Running data pipelines or automation scripts
Integrating Yativo into a Jupyter notebook or analytics workflow

pip install yativo-crypto-sdk

Use the PHP SDK when:

Building a Laravel, Symfony, or plain PHP application
Your existing stack is PHP and you need a drop-in Composer package

composer require yativo/crypto-sdk

Use the Java SDK when:

Your application is built on Spring Boot
You want auto-configuration via application.yml with zero boilerplate
You prefer dependency injection and @Autowired service beans
You want to handle webhook events via Spring’s @EventListener

<!-- Maven -->
<dependency>
  <groupId>com.yativo</groupId>
  <artifactId>yativo-crypto-sdk-spring-boot-starter</artifactId>
  <version>1.0.1</version>
</dependency>

Use the React SDK when:

Building a React single-page application or Next.js app
You want ready-made hooks (useWallets, useBalance, useSwap, etc.)
You need pre-built UI components (DepositWidget, YativoCardWidget, etc.)
You want authentication state managed for you via YativoProvider

npm install @yativo/crypto-sdk-react

Common Concepts Across All SDKs

All SDKs expose the same logical resources:

Resource	Description
`auth`	Register, login, OTP verification
`accounts`	Manage business accounts
`assets`	Wallets and supported assets
`transactions`	Send / receive funds
`webhooks`	Create and verify webhooks
`apiKeys`	Programmatic API key management
`customers`	End-customer management
`analytics`	Volume, fees, and reporting
`cards`	Virtual card issuance and management
`swap`	Quote and execute asset swaps
`iban`	Dedicated IBAN accounts

Authentication Modes

Every SDK supports two authentication flows:

Email / password — call auth.login() then auth.verifyOtp() to obtain a session token; the SDK stores it and auto-refreshes on 401 responses.
API key + secret — pass apiKey and apiSecret to the constructor. The SDK exchanges them for a Bearer token automatically; no manual token management required.

Rate Limiting

The Yativo Crypto API enforces 60 requests per minute per endpoint. All SDKs surface rate-limit errors as dedicated exception types so you can implement back-off logic.

Base URL

All SDKs default to the production base URL:

https://crypto-api.yativo.com/api/

You can override this in the constructor for staging or local development environments.

Next Steps

TypeScript SDK

Complete guide with code examples for every resource.

Python SDK

Python-idiomatic examples and exception handling.

PHP SDK

Composer setup, try/catch patterns, and webhook verification.

Java SDK

Spring Boot auto-configuration and service injection.

React SDK

Hooks, components, widgets, and theme customization.

Browser Extensions

Chrome and Firefox extensions for wallet monitoring and notifications.

Overview

Wallets & Assets

Transactions

Yativo Card

Payment Gateway

Agentic Wallets

IBAN

Automation

Compliance

B2B

Developer Tools

Tutorials

SDKs

Browser Extensions (Coming Soon)

Sandbox

SDK Overview

Yativo Crypto SDKs

TypeScript / Node.js

Python

PHP

Java / Spring Boot

React

MCP Server

Quick Comparison

Choosing the Right SDK

Common Concepts Across All SDKs

Authentication Modes

Rate Limiting

Base URL

Next Steps

TypeScript SDK

Python SDK

PHP SDK

Java SDK

React SDK

Browser Extensions

​Yativo Crypto SDKs

TypeScript / Node.js

Python

PHP

Java / Spring Boot

React

MCP Server

​Quick Comparison

​Choosing the Right SDK

​Common Concepts Across All SDKs

​Authentication Modes

​Rate Limiting

​Base URL

​Next Steps

TypeScript SDK

Python SDK

PHP SDK

Java SDK

React SDK

Browser Extensions

Yativo Crypto SDKs

Quick Comparison

Choosing the Right SDK

Common Concepts Across All SDKs

Authentication Modes

Rate Limiting

Base URL

Next Steps