Migrate from direct account generation
Move an API integration from legacy generation endpoints to the setup-request lifecycle.
Migrate from direct account generation
New integrations should use the setup-request workflow instead of calling a legacy account-generation endpoint directly.
Why migrate
The setup-request API:
- Returns actionable missing-data and missing-person blockers.
- Supports asynchronous verification and activation.
- Starts setup automatically when ready.
- Separates setup status from the available account.
Equivalent workflow
| Legacy action | New action |
|---|---|
| Generate a USD/EUR/GBP account directly | POST /v1/senders/{senderId}/virtual-bank-accounts/{currency}/setup-request |
| Retry generation after adding data | Follow blocker actions, then poll GET |
| Read generated account from sender details | GET /v1/senders/{senderId}/virtual-bank-accounts/{currency} |
Use USD, EUR, GBP, or MXN in the URL.
Existing generation endpoints remain available during the compatibility period. Mesta will communicate a deprecation timeline separately.
Updated about 10 hours ago
Did this page help you?