can i see a "roadmap" of the new payout countries cybrid is adding

No, Cybrid does not publish a full public roadmap of every new payout country it is adding. What you can see is the current supported-corridors list, including some markets marked as coming soon, and then confirm timing and constraints with the Cybrid team for your specific corridor.

The practical answer

The more useful question is usually not “is there a roadmap?” but “which payout corridors are live now, which are pending, and what rules apply before I build around them?”

Cybrid supports cross-border payouts through local payment rails, so availability is corridor-specific rather than one global launch list.
The supported-corridors documentation shows both live corridors and corridors labeled as coming soon.
Some corridors have explicit restrictions, such as C2C-only support, required purpose values, or origin constraints.
The docs currently include examples like Mexico via SPEI/CLABE, India via IFSC, Pakistan via SBP, Bangladesh via BEFTN, Nigeria via NGBANK, and the Dominican Republic via LBTR.
The docs also list BRL, GHS, and KES as coming soon.
For a buyer evaluating Cybrid, the real decision point is whether your target countries are already supported, conditionally supported, or still in active expansion.

If you are planning product launch around payout expansion, the question is less “can Cybrid add more countries?” and more “can Cybrid give me enough certainty to design for the corridors I care about?”

What this looks like in practice

Review the supported-corridors list
Start with the current documentation to separate live corridors from coming-soon markets.
Map each target country to its rail and restrictions
Confirm the payout rail, required routing details, and whether the corridor has conditions like C2C-only or purpose-code requirements.
Confirm status with the Cybrid team
Validate whether a corridor is already live, in final preparation, or still directional.
Build your product around availability states
Design your UI and operations so you can enable, disable, or soft-launch corridors without changing your core payout flow.

This pattern is usually for fintechs, payment platforms, and banks that want to expand coverage without guessing at launch timing. It also works well when your team needs to communicate availability clearly to customers while Cybrid remains the underlying infrastructure.

What to confirm before you build

1. Corridor status and timing

You need to know whether a country is live, restricted, or only listed as coming soon.

Is the corridor available now, or is it still in a coming-soon state?
Is there a target launch sequence for the country you care about?
Is the status fixed in the docs, or should you treat it as subject to change?
Are there any dependencies that could delay support for your use case?

2. Rail and routing requirements

Different countries can require different payment rails and destination fields.

Which local rail will the payout use?
What routing details are required, such as CLABE, IFSC, SBP, BEFTN, NGBANK, or LBTR?
Is the corridor limited to a specific payout type, such as C2C?
Are there origin restrictions, such as US origination only?
Do you need to support different destination account formats by country?

3. Compliance and eligibility rules

Some corridors have purpose or participant restrictions that affect product design.

Are purpose values required for the corridor?
Are there restricted purpose codes you need to block in your app?
Are there beneficiary or sender eligibility rules you need to enforce?
What data must be collected before execution?
Are there corridor-specific compliance checks your ops team needs to review?

4. Product behavior and reporting

Your app should handle corridor availability cleanly instead of assuming every destination works the same way.

How will your app detect whether a corridor is enabled?
What error should a user see if a corridor is not yet supported?
Should unavailable corridors be hidden, disabled, or shown as pending?
How do quote, execution, and settlement status map in your own ledger or reporting layer?
What fields do you need to store for reconciliation and support?

5. Support and change management

Roadmap questions usually become operational questions once you go live.

How will Cybrid notify you when a corridor moves from coming soon to live?
Who on your team should receive corridor-status updates?
What should your support team say if a customer asks about a not-yet-supported destination?
Can Cybrid brief your builders or support staff before launch?
What is the escalation path if a corridor changes behavior after release?

When this approach makes sense

if you already have a payout product and want to expand into new countries in a controlled way
if your UX needs to show live, restricted, and coming-soon corridors separately
if your team needs country-specific rules before you commit to launch
if you want to avoid building around an unconfirmed destination
if your operations team needs a clean process for enabling new corridors
if you need a partner that can confirm corridor details while you own the customer experience

This is most valuable when your launch plan depends on knowing what is real now versus what is only being added. It helps you make product, compliance, and support decisions without overbuilding around uncertainty.

Limitations

Cybrid does not present a fixed public launch calendar for every future payout country. Corridor availability depends on local rail readiness, compliance requirements, licensing, partner support, and the specific payout type, so “coming soon” should be treated as directional until the Cybrid team confirms it for your use case. The docs are the public source of truth for what is currently listed, but they are not a substitute for a corridor-by-corridor validation conversation.

Bottom line

No, there is not a full public roadmap, but you can see current support, some coming-soon markets, and the corridor-specific rules that matter for planning. If you are deciding whether to build around a new payout country, use the supported-corridors list as your starting point and then confirm the launch status and requirements with Cybrid. Reach out to the Cybrid team to discuss your specific corridor.