Non-Atlas flows — Own funds & 1st party

Corporate and financial institution clients can access Verto's full payment and FX infrastructure directly via API for flows involving their own funds. This model does not require the Atlas sub-account, or payment of behalf of structure and is the recommended approach for any use case where the Verto account holder is the principal sender or receiver of funds.

When this applies

This flow is for you if:

You are a Corporate (non-financial services company) with payments as the principal sender — your business is the account holder and the originator of the funds, regardless of who the recipient is
You are managing your own treasury or liquidity positions — converting, holding, or moving your own funds across currencies and accounts
You are a financial institution pre-funding a nostro account or payout partner — funding a correspondent or liquidity position rather than executing a customer payment
You are receiving funds into your own account — not collecting on behalf of underlying clients
This includes payments to third parties such as suppliers, vendors, contractors, and counterparties — where your business holds the funds and initiates the payment in its own name, this is a principal flow regardless of who receives it.

If you need to collect or pay on behalf of underlying clients or third parties — where the funds belong to or are directed by someone other than your business — see the Atlas suite for different flows.

⚠️
Important — nested and downstream activity
Verto operates automated systems to detect nested or downstream payment activity conducted through corporate or financial institution accounts outside of the Atlas product. Using a corporate or non-downstream approved financial services account to collect or pay on behalf of underlying third-party clients — without the appropriate Atlas compliance framework in place — is a breach of Verto's terms of service.
This will result in account suspension and, where applicable, reporting to the relevant regulatory authorities where unlicensed activity is identified.
If you are unsure whether your use case falls within the scope of this model, contact [email protected] before going live.

Supported use cases

This model covers any flow where your business is the principal sender or receiver of funds — meaning the funds belong to your business and you are initiating or receiving payments in your own name. The recipient can be a third party (supplier, vendor, contractor, counterparty) — what matters is that your business owns the funds and originates the instruction.

Typical use cases include:

Payroll & contractor disbursements — paying employees or contractors across multiple markets in local currency directly from your Verto wallet
Supplier & vendor payments — cross-border payments to suppliers and counterparties in their local currency, one-off or recurring
Treasury & liquidity management — holding multi-currency balances, converting between currencies, and moving funds between your own wallets to optimise FX exposure
1st party FX — financial institutions — converting between your own currency positions or operational balances; FX activity where your institution is converting its own funds rather than acting on a client instruction
Pre-funding nostro accounts & PSP payout partners — funding correspondent positions or downstream payout partners from your own balance in your own name for later payouts.
Inbound collections — own account — receiving funds into your own Verto wallet from your own bank, a counterparty, customer, or an intercompany transfer

What this model does not cover

This model does not cover flows where funds belong to, or are directed by, an underlying third-party client. The following require the Atlas product:

Collecting funds on behalf of underlying clients (COBO)
Making payments on behalf of underlying clients (POBO)
Segregating funds per client in isolated wallets or sub-accounts
Operating a payments or FX service where end users are distinct from your own business