What we are shipping next on Payvessel (and how we prioritise)
Users ask for more countries, lower fees, and instant everything. We want that too. Reality is each corridor requires bank partners, licences, fraud models, and support training before we turn it on for everyone. Shipping half-ready rails would create losses for users and for Payvessel.
How prioritisation works
Our roadmap weights markets by remittance volume, merchant demand, and regulatory clarity. Nigeria remains the core launch market for consumer features while we expand Africa rails in phases. Features that reduce support load, like clearer decline reasons, sometimes ship before shiny new flags because they help millions of existing users immediately.
How to follow releases
Follow this blog and release notes in the app; we publish when a corridor moves from beta to general availability. If you depend on a corridor for payroll, subscribe to email updates so you are not surprised by maintenance windows.
Quick answers
- Can I request a feature?
- Yes, through support or community channels. We log demand even when we cannot commit to a date.
- Why did my corridor disappear temporarily?
- Partners sometimes pause for upgrades or compliance changes. Check in-app banners for timelines.
- Do betas cost the same?
- Beta pricing, if any, is communicated in the app. Always read the beta notice before moving large sums.
This article describes Payvessel product areas in general terms. Fees, limits, corridors, and availability depend on your verification level and region; always confirm in the app before you move money.
