Legacy endpoint migration to v1.1

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

📘

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; certificate-based login is now mandatory; Encrypted API Keys required going forward

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) — replaced by new payment service endpoint
• 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
• Name Enquiry / Name Validation — moved to payment service; new endpoint URL
• Proof of Payment — 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. The payload structure remains unchanged; a small number of new keys will be introduced as non-breaking additions

Migration guides

• Atlas for Fintech — Collections migration guide
• Atlas for Fintech — Payout migration guide
• Atlas for Platforms — Migration guide
• FX Rates migration guide

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