APIs engineers actually enjoy working with.
RESTful APIs with consistent design patterns, SDKs in 6 languages, a fully featured sandbox, and documentation written by engineers who have been on your side of the integration.
Sandbox ready in five minutes.
Get your API key
Sign up for a sandbox account and retrieve your test API key from the dashboard. No credit card, no contracts.
Instant provisioning with test credentials
Install the SDK
Install one of our six official SDKs, or call the REST API directly. All SDKs are open source and MIT licensed.
Available for Node.js, Python, Go, Ruby, Java & PHP
Make your first payment
Create an account, fund it with test money, and send your first test payment - all via API, all in sandbox.
Full payment lifecycle in a single API call
6 languages. All open source.
Every SDK is actively maintained by Techvica engineers, fully typed, and published under the MIT licence. Contributions welcome.
Install via npm. Fully typed, MIT licensed.
Install via pip. Fully typed, MIT licensed.
Install via go modules. Fully typed, MIT licensed.
Install via gem. Fully typed, MIT licensed.
Install via Gradle / Maven. Fully typed, MIT licensed.
Install via Composer. Fully typed, MIT licensed.
REST. Consistent. Predictable.
Every endpoint follows the same conventions. Resource-based URLs, JSON request and response bodies, standard HTTP status codes, and idempotency keys on all mutating operations.
Auth: Bearer token
Rate limit: 1,000 req/min (Growth)
Format: JSON request & response
Versioning: Stable, backwards-compatible
Core API areas
A full production mirror. No real money.
The sandbox is not a mock. It runs on the same codebase as production, with the same validation logic, the same webhook events, and the same ledger behaviour. Test edge cases you cannot safely test in production.
- Simulate payment success, failure, and timeout
- Trigger KYC pass, refer, and rejection scenarios
- Test webhook retry and signature verification
- Simulate FX rate movements
- Full ledger reconciliation in sandbox
Sandbox simulation
Payment success
Simulate a payment completing on any rail
Payment failure
Test specific failure codes like insufficient funds or timeout
KYC outcomes
Trigger pass, refer, or rejection scenarios
Delayed settlement
Add configurable latency to simulate real-world timing
Webhook retry
Test retry behaviour and signature verification
Everything you need to build.
Documentation
Comprehensive guides for every feature
Sample projects
Reference implementations in every SDK language
Migration guide
Moving from another provider? We have a path.
Community
Slack community of 3,000+ Techvica developers
What's changed.
API v2 is the current stable version. We maintain backwards compatibility across all minor versions. Breaking changes are only introduced in major versions with 6+ months notice.
April 2, 2026
Added SPEI (Mexico) rail support. FX endpoint now accepts forward quotes up to 30 days.
March 18, 2026
Resolved an edge case where SWIFT intermediary bank fees were not reflected in the payment object amount_net field.
March 5, 2026
Ledger v3 API now available in stable. Introduces cursor-based pagination, richer event metadata, and point-in-time balance queries.
February 20, 2026
Webhook HMAC signature now uses SHA-256 by default. SHA-1 deprecated - migrate by May 1, 2026.
February 6, 2026
Analytics API endpoints released. Query transaction volumes, success rates, and FX exposure programmatically.
Last 30 days uptime.
Common questions about our APIs
What programming languages do the SDKs support?
We maintain official SDKs for Node.js, Python, Go, Ruby, Java, and PHP. All SDKs are fully typed, open source under MIT, and actively maintained by Techvica engineers.
How do I get started with the Techvica API?
Sign up for a free sandbox account. You will get API keys within minutes. Our quick start guide walks you through your first payment in under 5 minutes with working code samples.
Is there a sandbox environment for testing?
Yes. The sandbox runs on the same codebase as production with identical validation, webhooks, and ledger behaviour. You can simulate successes, failures, timeouts, and edge cases.
What authentication does the API use?
The API uses Bearer token authentication. You generate API keys per environment (sandbox and production) from the dashboard. OAuth 2.0 is also supported for partner integrations.
How does API versioning work?
API v2 is the current stable version. We maintain backwards compatibility across all minor versions. Breaking changes are introduced only in major versions with 6+ months advance notice.
What are the API rate limits?
Starter plans get 100 requests per minute. Growth plans get 1,000 per minute. Enterprise customers get custom rate limits. All plans support burst capacity for bulk operations.
Developer support
Stuck on an integration? Growth and Enterprise customers get a dedicated support Slack channel with a response time of under 1 hour during business hours.
Contact supportDeveloper community
Join 3,000+ engineers building on Techvica. Share patterns, ask questions, and get notified about API changes in our Slack community.
Join the community