Improved
May 2026: Legacy endpoint migration
4 days ago by Geoffrey Mulei
We’ve introduced new service-specific sandbox endpoints to replace the legacy shared api-v3-sandbox.vertofx.com routes for login, beneficiaries, purpose codes, currencies, payment requests, and wallets.
The new endpoints separate traffic by service, including:
- Company authentication: api-company-sandbox.vertofx.com
- Beneficiaries: api-beneficiary-sandbox.vertofx.com
- Payments and purpose codes: api-payment-preview.vertofx.dev
- Currencies: api-currency-sandbox.vertofx.com
- Wallets: api-wallet-sandbox.vertofx.com
Key benefits
- Clearer service ownership: Each API area now has its own service-specific host, making integrations easier to configure, monitor, and troubleshoot.
- Improved scalability: Services can evolve independently without requiring all integrations to depend on one shared legacy API host.
- Cleaner migration path: Legacy routes now map directly to newer routes for authorization, beneficiaries, listings, payments, and wallets.
- More consistent resource naming: Beneficiary routes now use the /recipients resource path, aligning the API with recipient-based payout workflows.
- Better company-scoped wallet access: Wallet routes now include {companyId}, making account context explicit when listing or retrieving wallets.
- Safer integration testingTeams can migrate one service at a time in sandbox before moving updated routing patterns into production.
Migration guide
See the new Legacy Endpoint Migration Guide for the full endpoint mapping and migration checklist.
Affected endpoint areas
- Authorization login
- Beneficiary create, list, update, get, and delete
- Purpose code listing
- Currency listing
- Payment request create, list, and lookup Wallet list and wallet detail