/

v2.6.0

Virtual Accounts & Inbound Payment Routing

Summarize with AI

Share update

Solvent API v2 is now generally available.

When we started designing v2, the question we kept coming back to was: what would this API look like if we built it knowing everything we know now about how our customers actually use it? The answer required more changes than a minor version bump could accommodate. So we built v2 from the ground up, carrying forward the parts that worked and rethinking the parts that did not.

What Changed

The most significant change is the unified API surface. In v1, payments, accounts, and FX were separate API products with separate authentication flows and separate base URLs. In v2, everything is accessible through a single endpoint with a single API key.

Javascript

1
2
3
4
5
6
7
8
9
# v1 — three separate base URLs
curl https://payments.Solvent.com/v1/payments
curl https://accounts.Solvent.com/v1/accounts
curl https://fx.Solvent.com/v1/rates
 
# v2 — one unified base URL
curl https://api.Solvent.com/v2/payments
curl https://api.Solvent.com/v2/accounts
curl https://api.Solvent.com/v2/fx/rates

Idempotency keys are now supported on all write endpoints. This was one of the most requested features from customers building payment workflows where duplicate requests needed to be handled gracefully.

Javascript

1
2
3
4
5
curl -X POST https://api.Solvent.com/v2/payments \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Idempotency-Key: pay_request_01jk9m" \
-H "Content-Type: application/json" \
-d '{"amount": 10000, "currency": "GBP", "destination": "acc_01jk4p"}'

SDK Availability

Official SDKs for Node.js, Python, and Go are available today.

Javascript

1
2
3
4
5
6
7
8
# Node.js
npm install @Solvent/sdk
 
# Python
pip install Solvent-sdk
 
# Go
go get github.com/Solvent-finance/Solvent-go

Full SDK documentation is at docs.Solvent.com/sdks.

v1 Deprecation Timeline

The v1 API will continue to receive security patches until March 31, 2026, at which point it will be retired. No new features will be added to v1. The migration guide covers every breaking change and provides side-by-side examples for each endpoint.

New Features

  • Multi-currency accounts — Hold, send, and receive in 34 currencies from a single Solvent account. Each balance is isolated, auditable, and visible in real time.

  • Entity-level account scoping — Accounts can now be scoped to a specific legal entity. Balances and statements are isolated per entity by default.

  • Programmatic account creation — Create currency accounts via the API in seconds. No manual provisioning or support ticket required.

  • Local account details per currency — Each account is assigned a local IBAN, account number, or mobile money identifier depending on the currency and jurisdiction.

  • Cross-entity transfers — Move funds between entities within the same Solvent organisation via the Transfers API, with a full audit trail on every transaction.

Improvements

  • Dashboard currency switcher — The treasury overview now lets you toggle between your reporting currency and any individual currency balance with a single click.

  • Faster account statement exports — Statement generation for accounts with more than 10,000 transactions has been optimised. Export times are now consistently under 3 seconds regardless of transaction volume.

  • Improved FX rate display — Live mid-market rates now update every 30 seconds in the dashboard, down from every 2 minutes. The timestamp of the last rate update is now shown next to each balance.

  • API pagination for account listings — The GET /v1/accounts endpoint now supports cursor-based pagination for organisations with more than 100 accounts.

Fixes

  • Fixed: Duplicate webhook events on payment settlement — In some cases, the payment.settled webhook was firing twice for payments processed via SEPA Instant. This has been resolved. Affected customers have been notified directly.

  • Fixed: Incorrect balance display after failed FX conversion — When an FX conversion failed mid-process, the source currency balance was temporarily showing as zero in the dashboard. The underlying balance was not affected, but the display was incorrect. This is now resolved.

  • Fixed: Statement export timeout for large accounts — Accounts with transaction histories exceeding 50,000 records were occasionally timing out during CSV export. The export pipeline has been rewritten to handle large volumes without timeout errors.

Create a free website with Framer, the website builder loved by startups, designers and agencies.