v1.0 to v1.1 - What's Changing

This page provides a high-level summary of what is changing between v1.0 and v1.1, and the timeline for migrating to the new endpoints.

We are upgrading our API infrastructure to give you a faster, more reliable, and more consistent integration experience. The new v1.1 endpoints are built on a modernised architecture that reduces complexity, improves response times, and makes it easier to build on top of Verto.

Most of your existing integration remains unchanged — only a small number of endpoints require updates, and we have provided step-by-step migration guides to make the transition as straightforward as possible.

Timeline

Date	Milestone
1 July 2026	Legacy APIs officially deprecated. Migration guides and new endpoints available. Begin your migration.
31 January 2027	Legacy API access revoked. All integrations must be on v1.1 by this date.

📘
Why January 2027?
Our standard deprecation window is 6 months, which would ordinarily place the deadline in December 2026.
We have extended this to 31 January 2027 to account for code freezes over the Christmas and New Year period. We encourage you to complete your migration before the holiday period where possible.

APIs being deprecated

The following legacy endpoints are deprecated as of 1 July 2026 and will stop working after 31 January 2027. Detailed migration guidance for each is available in the migration guides below.

Authorization

Login — URL change; new base URL required

FX Service

Get FX Rate — GET method deprecated; replaced by new POST endpoint with restructured payload; amount and amountCurrency now mandatory
Create FX Trade — new endpoint URL; payload restructured; side (BUY/SELL) removed.paymentType and targetWalletId now required
Get an FX Trade — URL change; client-side integration changes required

Beneficiary

Create Beneficiary — new beneficiary service endpoint
Get all Beneficiaries — new beneficiary service endpoint; pagination parameters renamed
Get a Beneficiary — new beneficiary service endpoint
Update a Beneficiary — new beneficiary service endpoint
Delete a Beneficiary — new beneficiary service endpoint

Payment Service

Create Payment Request (v2.1) & Create Payment Request (v2.2) — replaced by new payment service endpoint
Get all Payment Requests — new endpoint URL
Get a Payment Request — new endpoint URL
Get all Purpose Codes — moved to payment service; new endpoint URL

Wallet Service

Get a Wallet (v2.2) — deprecated; migrate to Get all Wallets

No action required

The following are unchanged in v1.1 and require no migration:

Sub-account creation & onboarding
Add onboarding data
Create wallet
Get account details for the wallet
Receive funding webhook
Sub-account wallet-to-wallet sweep
Webhooks — existing webhook consumers will be automatically migrated by Verto with zero interruption to your service, and no change to payload.

Migration guides

Questions? Contact your account manager or reach out to [email protected]